1. Gerhard Dueck -- CS3013Architecture 1 Architecture-Centric Process  There is more to software development then going blindly through the workflows driven only by uses cases  “more” is architecture  Analogous example: build a one car garage (see page 59) –(Blind man and elephant)  Architectural Styles –Pipes and filters –Layered systems –Client-server –Distributed systems

2. Gerhard Dueck -- CS3013Architecture 2 Software Architecture  Organization of the software system  Structural elements and their interfaces  Composition of the structural and behavioral elements into progressively larger subsystems  Architectural style  Concerns also: functionality, performance, resilience, reuse, comprehensibility,

3. Gerhard Dueck -- CS3013Architecture 3 4 + 1 View of Architecture Logical View Component View Process View Deployment View Use Case View

4. Gerhard Dueck -- CS3013Architecture 4 Logical View  Functionality  This view is addressed early  Referred to a tactical design  Key mechanisms involve the selection of: –Programming language –Persistent data storage –Look and feel of UI –Error handling –Object distribution and migration –Networking

5. Gerhard Dueck -- CS3013Architecture 5 Component View  Actual software module organization  Often layered  Often there is a one-to-one relationship between logical and component view packages User Interface Application Specific Packages Reusable Packages Key Mechanisms OS/ System Packages

6. Gerhard Dueck -- CS3013Architecture 6 Process View  Focuses on the run-time implementation  Takes into account: –Performance –Reliability –Scalability –Integrity –System management –Synchronization  Examples: –Java applets –ActiveX components –Dynamic libraries

7. Gerhard Dueck -- CS3013Architecture 7 Deployment View  Run-time processing elements and the software processes living in them  Takes into account: –System availability –Reliability –Scalability –Performance

8. Gerhard Dueck -- CS3013Architecture 8 Use Case View  This view of the architecture demonstrates and validates the logical, process, component, and deployment views. Sequence diagrams and collaboration diagrams are created to show how the various design elements interact to produce the desired behavior.