Capability Pattern: Define the Architecture |
This activity completes the architecture for an iteration.
| Description |  | Work Breakdown Structure |  | Team Allocation |  | Work Product Usage |  |
Relationships
Context | OpenUPBasic
Description
This activity is repeated in each iteration in the Elaboration phase. The main goal of this activity is to propose an architecture that addresses the requirements with high architectural risks, thus providing a solid, yet resilient, foundation on which to build the system functionality. The architect analyzes the architectural constraints, identifies available assets to build the system, defines how the system will be structured, and identifies the initial abstractions and mechanisms that must be provided by the architecture. Throughout all of the iterations, the architect: Identifies commonalities between different requirements to leverage reuse Defines strategies for achieving requirements related to quality Captures and communicates architectural decisions
Properties
Event-Driven |
Multiple Occurrences |
Ongoing |
Optional |
Planned |
Repeatable |
Staffing
These activities are best carried out by a small team staffed by cross-functional team members. Issues that are typically architecturally significant include usability, performance, scaling, process and thread synchronization, and distribution. The team should also include members with domain experience who can identify key abstractions. The team should also have experience with model organization and layering. The team will need to be able to pull all these disparate threads into a cohesive, coherent (albeit preliminary) architecture. Because the focus of the architecture effort is shifting toward implementation issues, greater attention needs to be paid to specific technology issues. This will force the architecture team to shift members or expand to include people with distribution and deployment expertise (if those issues are architecturally significant). In order to understand the potential impact of the structure on the implementation model on the ease of integration, expertise in the software build management process is useful to have. At the same time, it is essential that the architecture team not be composed of a large extended team. A strategy for countering this trend is to retain a relatively small core team with a satellite group of extended team members that are brought in as "consultants" on key issues. This structure also works well for smaller projects where specific expertise may be borrowed or contracted from other organizations; they can be brought in as specific issues need to be addressed.
Usage
Usage Notes | The work is best done in several sessions, perhaps performed over a few days (or weeks and months for very large systems). The initial focus will be on the identifying Concept: Design Mechanisms and specifiying the important design elements. Care should also be taken to incorporate existing design elements to ensure that new design do not duplicate existing functionality. As the design emerges, concurrency and distribution issues are introduced. As these issues are considered, changes to design elements may be required to split behavior across processes, threads or nodes. As the individual models are refined to incorporate the architectural decisions, the results are documented in the Architecture description. The resulting architecture is reviewed.
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