1、Chapter 10Architectural DesignSoftware Engineering: A Practitioners Approach, 6th editionby Roger S. Pressman1Software ArchitectureThe software architecture of a program or computing system is the structure or structures of the system, which comprise the software components, the externally visible p

2、roperties of those components, and the relationships among them. Bass. et al.2Why Architecture?Architecture is a representation of a system that enables the software engineer to:analyze the effectiveness of the design in meeting its stated requirements,consider architectural alternatives at a stage

3、when making design changes is still relatively easy, andreduce the risks associated with the construction of the software.3Data DesignArchitectural level Database designdata miningdata warehousingComponent level Data structure design4Architectural StylesEach style describes a system category that en

4、compasses:a set of components (e.g., a database, computational modules) that perform a function required by a system,a set of connectors that enable “communication, coordination, and cooperation” among components,constraints that define how components can be integrated to form the system, andsemanti

5、c models that enable a designer to understand the overall properties of a system.5Specific StylesData-centered architectureData flow architectureCall and return architectureObject-oriented architectureLayered architecture6Data-Centered Architecture7Data-Flow Architecture8Call and Return Architecture

6、9Object-Oriented Architecture10Layered Architecture11Architectural PatternsConcurrencyoperating system process managementtask schedulerPersistencedatabase management systemapplication level persistenceDistributionbroker12Architectural DesignArchitectural context diagrams model how software interacts with external entitiesArchetypes are classes or patterns that represent an abstraction critical to the systemArchitectural components are derived from the application domain, the infrastructure, and the interfac