Work Product Descriptor: Design |
This artifact describes the realization of required system functionality in terms of components and serves as an abstraction of the source code.
Based on Method Work Product: Design
Purpose
Describe the elements of the system so they can be examined and understood in ways not possible by reading the source code.
Relationships
Roles | Responsible: Developer | Modified By:
Input To | Mandatory: Develop the Architecture | Optional: None | External: None
Output From | Analyze Architectural Requirements Develop the Architecture
Main Description
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.
Properties
Optional |
Planned |
Tailoring
Impact of not having | Implementation will proceed with fine-grained, inconsistent tactical decisions that lead to poor-quality software.
Reasons for not needing | Some representation of the design will always be necessary. In circumstances where a project involves applying well-understood, existing strategies for architecture and design, it is possible that you will not need a new design. In those cases, you can simply refer to some existing design.
Representation Options | 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.
More Information
Checklists | Design
Concepts | Visual Modeling
Guidelines | Design
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. View copyright information here: OpenUP Copyright