架構(gòu)設(shè)計(jì)Chapter10ArchitecturalDesign課件

1、Chapter 10Architectural DesignSoftware Engineering: A Practitioners Approach, 6th editionby Roger S. Pressman1第1頁(yè)，共18頁(yè)。Software ArchitectureThe software architecture of a program or computing system is the structure or structures of the system, which comprise the software components, the externally

2、visible properties of those components, and the relationships among them. Bass. et al.2第2頁(yè)，共18頁(yè)。Why 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 altern

3、atives at a stage when making design changes is still relatively easy, andreduce the risks associated with the construction of the software.3第3頁(yè)，共18頁(yè)。Data DesignArchitectural level Database designdata miningdata warehousingComponent level Data structure design4第4頁(yè)，共18頁(yè)。Architectural StylesEach style

4、 describes a system category that encompasses: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 integ

5、rated to form the system, andsemantic models that enable a designer to understand the overall properties of a system.5第5頁(yè)，共18頁(yè)。Specific StylesData-centered architectureData flow architectureCall and return architectureObject-oriented architectureLayered architecture6第6頁(yè)，共18頁(yè)。Data-Centered Architectu

6、re7第7頁(yè)，共18頁(yè)。Data-Flow Architecture8第8頁(yè)，共18頁(yè)。Call and Return Architecture9第9頁(yè)，共18頁(yè)。Object-Oriented Architecture10第10頁(yè)，共18頁(yè)。Layered Architecture11第11頁(yè)，共18頁(yè)。Architectural PatternsConcurrencyoperating system process managementtask schedulerPersistencedatabase management systemapplication level persisten

7、ceDistributionbroker12第12頁(yè)，共18頁(yè)。Architectural 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 interface.13第13頁(yè)，共18頁(yè)。Arch. Context Diagram14第14頁(yè)，共18頁(yè)。Safe