1 5/18/2007ã 2007, Spencer Rugaber Architectural Documentation Graphical (views) and textual Kruchten's 4+1 Views –Philippe B. Kruchten. "The 4+1 View Model of Architecture." IEEE Software, 12(6):42-50, November 1995 –Logical, developmental, process, physical, use case Other useful information –Features, non-functional requirements, bug reporting, context, utility

2 5/18/2007ã 2007, Spencer Rugaber Logical View Structural breakdown of computational, communicational and behavioral responsibilities Diagrams: –Box and arrow –Components and connectors (ADLs) –UML Class model diagram –UML Interaction Overview diagram –UML Collaboration diagram

3 5/18/2007ã 2007, Spencer Rugaber Developmental View Units of source code –Packages, classes, subsystems, libraries, files Diagrams –UML Package diagram –UML Component diagram –CVS modules

4 5/18/2007ã 2007, Spencer Rugaber Class Diagram with Packages

5 5/18/2007ã 2007, Spencer Rugaber Package Diagram

6 5/18/2007ã 2007, Spencer Rugaber Component Diagram

7 5/18/2007ã 2007, Spencer Rugaber Process View Processes and threads into which execution is divided Diagrams –UML Deployment diagram

8 5/18/2007ã 2007, Spencer Rugaber Example Deployment Diagram

9 5/18/2007ã 2007, Spencer Rugaber Physical View Machines used for system execution and how processes are allocated to them Diagrams –UML Deployment diagram –UML Sequence diagram

10 5/18/2007ã 2007, Spencer Rugaber Example Sequence Diagram

11 5/18/2007ã 2007, Spencer Rugaber Use Case View Important execution sequences from the external actors' points of view Diagrams –UML Use Case diagram –UML Communication (Collaboration) diagram –UML Sequence diagram –UML Activity diagram –Structured text

12 5/18/2007ã 2007, Spencer Rugaber Example Use Case Diagram

13 5/18/2007ã 2007, Spencer Rugaber Equivalent Collaboration Diagram

14 5/18/2007ã 2007, Spencer Rugaber Example Activity Diagram

15 5/18/2007ã 2007, Spencer Rugaber Feature View Conceptual units from the user's point of view Diagrams –Feature diagram –Inter-feature constraints

16 5/18/2007ã 2007, Spencer Rugaber Example CarCar BodyTransmissionEnginePulls TrailerAutomaticManualElectricGasoline

17 5/18/2007ã 2007, Spencer Rugaber Mandatory features: Optional features: Alternative features: –Choose exactly one Or features: –Choose a subset Notation

18 5/18/2007ã 2007, Spencer Rugaber Non-Functional View How non-functional requirements affect the software architecture –Explicit tradeoffs Tabular text

19 5/18/2007ã 2007, Spencer Rugaber Bug Reporting Units to which bugs are allocated –Consequences with respect to Developmental view –Consequences with respect to Feature view Bugzilla components

20 5/18/2007ã 2007, Spencer Rugaber Context View Relationship of a system to its environment –External actors, events and percepts (Data flow) Context diagram

21 5/18/2007ã 2007, Spencer Rugaber Context Diagrams The top level data flow diagram is called the context diagram It contains exactly one process node denoting the overall function of the system Human Opponent Play Chess Human Moves Machine Moves Board Drawings

22 5/18/2007ã 2007, Spencer Rugaber Utility View Supporting software –Installation scripts –Log file analysis –Statistical processing Tabular text