39.2. Notation: The Structure of a SAD
The following SAD structure is essentially the format used in the UP:
Software Architecture DocumentArchitectural Representation (Summary of how the architecture will be described in this document, such as using by technical memos and the architectural views. This is useful for someone unfamiliar with the idea of technical memos or views. Note that not all views are necessary.) Architectural Factors (Reference to the Supplementary Specification to view the Factor Table.) Architectural Decisions (The set of technical memos that summarize the decisions.) Logical View (UML package diagrams, and class diagrams of major elements. Commentary on the large scale structure and functionality of major components.) Deployment View (UML deployment diagrams showing the nodes and allocation of processes and components. Commentary on the networking.) Process View (UML class and interaction diagrams illustrating the processes and threads of the system. Group this by threads and processes that interact. Comment on how the interprocess communication works (e.g., by Java RMI). Use-Case View (Brief summary of the most architecturally significant use cases. UML interaction diagrams for some architectural significant use-case realizations, or scenarios, with commentary on the diagrams explaining how they illustrate the major architectural elements.) Other Views… |