Work Product: Architecture Notebook |  |
This artifact describes the rationale, assumptions, explanations and implications of the decisions that were made in forming the architecture.
Purpose
To capture and make architectural decisions, and explain those decisions to developers.
Relationships
Roles | Responsible: Architect | Modified By: Architect
Input To | Mandatory: Evolve the Architecture | Optional: None | External: None
Output From | Evolve the Architecture
Description
Brief Outline | At a minimum, this artifact should : Describe the goals and philosophy of the architecture Identify assumptions and dependencies Reference the architecturally significant requirements Describe the architectural mechanisms, and Describe decisions and constraints with their justifications. Consider adding more information when it's appropriate. A small project shouldn't spend lots of time documenting the architecture, but all critical elements of the system must be communicated to current and future team members. Consider including useful architectural views, references to architecturally significant areas of the design, key abstractions, critical system interface descriptions, and a description of the architectural framework or pattern.
Main Description | This artifact describes the Software Architecture. It provides a place for maintaining the list of architectural issues, along with the associated architectural decisions, designs, patterns, code documented (or pointed at),etc. all at appropriate level to make it easy to understand what architectural decisions have been made, and are still left to be made.
Properties
Optional |
Planned |
Illustrations
Templates | Architecture Notebook
Tailoring
Representation Options | A set of architecture models could be developed as part of the architectural documentation. For more information, see Guideline: Modeling the Architecture.
More Information
Checklists | Architecture Notebook
Concepts | Software Architecture
Guidelines | Modeling the Architecture