• Developer

• Architect
• Developer

• Implement the Solution
• Refine the Architecture

• Design the Solution
• Implement Developer Tests

• Design the Solution
• Refine the Architecture

• Construction Phase Iteration  >  Develop Solution (for requirement) (within context)  >  Design
• Construction Phase Iteration  >  Develop Solution Increment  >  Design
• Develop Solution (for requirement) (within context)  >  Design
• Develop Solution Increment  >  Design
• Develop Solution Increment (no TDD)  >  Design
• Develop the Architecture  >  Design
• Develop the Architecture  >  Develop the Solution  >  Design
• Develop the Architecture  >  Design
• Develop the Architecture  >  Develop Solution Increment  >  Design
• Elaboration Phase Iteration  >  Develop the Architecture  >  Design
• Elaboration Phase Iteration  >  Develop Solution (for requirement) (within context)  >  Design
• Elaboration Phase Iteration  >  Develop the Architecture  >  Design
• Elaboration Phase Iteration  >  Develop Solution Increment  >  Design
• Inception Phase Iteration  >  Develop Architecture Spike  >  Design
• Transition Phase Iteration  >  Develop Solution (for requirement) (within context)  >  Design
• Transition Phase Iteration  >  Develop Solution Increment  >  Design

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

• Design

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 key decisions about the structure and behavior of the system and communicate them to other collaborators. It is also important that these decisions can be communicated at various levels of abstraction and granularity. Some aspects of the design can be represented by source code, possibly with some extra annotations. But more abstract representations of the design will be at a higher-level than source code.

The more abstract representation could use various representation options. UML could be used either strictly or informally; it is a preferred notation based on its rich semantics and broad usage in the industry. Other techniques could be used to communicate the design. Or the design could use a mix of techniques as applicable.

Whether you record these representations on a white board or use a formal tool is not governed by this process. But any representation, whether characterized as formal or informal, should unambiguously communicate the technical decisions embodied by the design.

• Design

• Design
• Visual Modeling