| 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.
|
