Describe the elements of the system so they can be examined and understood in ways not possible by reading the source code.

• Developer

• Develop the Architecture
• Implement the Solution

• None

• None

• Design the Solution
• Develop the Architecture

This product can describe multiple static and dynamic views of the system for examination. Although various views may focus on divergent, seemingly independent issues of how the system will be put together and work, they should fit together without contradiction.

It describes the elements that will make up the implemented system. It communicates abstractions of particular portions of the implementation and can describe an isolated subsystem, a high-level analysis of the system, a view of the system in only one context, or other perspectives that explain a solution to a specific problem that needs to be communicated.

Implementation will proceed with fine-grained, inconsistent tactical decisions that lead to poor-quality software.

It is important that the author of this work product be able to analyze and communicate to other collaborators key decisions about the structure and behavior of the system.  It is also important that these decisions can be communicated at various levels of abstraction and granularity. Whether you record these decisions on a white board or use a formal tool is not governed by this process.

Certain parts of this artifact will be important to the understanding of the overall architecture. Therefore, you must represent them in some way that will last.  For other parts that are not architecturally-significant, this work product may be considered more of an informal result of the task of designing than a true artifact.

• Design

• Visual Modeling

• Design