Artifact: Architecture |
The architecture describes the blueprint for software development, frequently represented using a number of architecture views. It also contains the rationale, assumptions, explanations and implications of the decisions that where made in forming the architecture as well as the global mapping between views.
Domain: Architecture Work Product Kinds: Specification
Purpose
This artifact focuses on specific aspects of the design, concentrating on structure, essential elements, and key scenarios and those aspects that have a lasting impact on performance, reliability, adaptability and cost. It defines the set of mechanism, patterns and styles that are going to guide the rest of the design, assuring its integrity. Teams are formed around architectural elements, which are the units of implementation, unit testing, integration, configuration management, documentation, and a host of other activities.
Relationships
Roles | Responsible: Architect | Modified By: Architect
Tasks | Input To: Implement the Solution Design the Solution Demonstrate the Architecture Refine the Architecture Plan Iteration Define the Architecture | Output From: Define the Architecture Refine the Architecture
Description
Main Description | This product is a communication vehicle that tells developers what pieces to build and how they behave and interact with each other. It determines the project structure so that managers can plan the project. It also gives the first glimpse of the system to who must maintain and change the architecture later on.
Illustrations
Templates | Architecture
Tailoring
Representation Options | The architecture can be represented in many forms and from many viewpoints, depending on the needs of the project and the preferences of the project team. It can be expressed as a simple metaphor; or as a reference to a pre-defined architectural style or set of styles. It may be a precise set of models or documents describing the various aspects of the system's key elements. It may also be expressed as a set of skeletal code. It is frequently a design artifact that must be represented in a readable and accessible way, employing Architecture Views for describing and communicating the architecture. A view is a representation of a set of significant system elements and the relations associated with them. To choose the appropriate set of views, you must identify the stakeholders that depend on software architecture documentation and their information needs.
More Information
Checklists | Architecture
Concepts | Patterns Visual Modeling Component Abstract Away Complexity Using Visualizations
Guidelines | Architecture View
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