1 / 22

Architectural Documentation

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

codyj
Download Presentation

Architectural Documentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 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 ã 2007, Spencer Rugaber

  2. 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 ã 2007, Spencer Rugaber

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

  4. Class Diagram with Packages ã 2007, Spencer Rugaber

  5. Package Diagram ã 2007, Spencer Rugaber

  6. Component Diagram ã 2007, Spencer Rugaber

  7. Process View • Processes and threads into which execution is divided • Diagrams • UML Deployment diagram ã 2007, Spencer Rugaber

  8. ExampleDeploymentDiagram ã 2007, Spencer Rugaber

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

  10. Example SequenceDiagram ã 2007, Spencer Rugaber

  11. 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 ã 2007, Spencer Rugaber

  12. Example Use Case Diagram ã 2007, Spencer Rugaber

  13. EquivalentCollaboration Diagram ã 2007, Spencer Rugaber

  14. ExampleActivityDiagram ã 2007, Spencer Rugaber

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

  16. Car Car Body Transmission Engine Pulls Trailer Automatic Manual Electric Gasoline Example ã 2007, Spencer Rugaber

  17. Notation • Mandatory features: • Optional features: • Alternative features: • Choose exactly one • Or features: • Choose a subset ã 2007, Spencer Rugaber

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

  19. Bug Reporting • Units to which bugs are allocated • Consequences with respect to Developmental view • Consequences with respect to Feature view • Bugzilla components ã 2007, Spencer Rugaber

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

  21. 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 Moves Human Opponent Play Chess Machine Moves Board Drawings ã 2007, Spencer Rugaber

  22. Utility View • Supporting software • Installation scripts • Log file analysis • Statistical processing • Tabular text ã 2007, Spencer Rugaber

More Related