Capability Pattern: Determine Architectural Feasibility |
Confirm that the project is feasible by constructing an architectural proof-of-concept.
| Description |  | Work Breakdown Structure |  | Team Allocation |  | Work Product Usage |  |
Relationships
Context | OpenUPBasic
Properties
Event-Driven |
Multiple Occurrences |
Ongoing |
Optional |
Planned |
Repeatable |
Staffing
As with Activity: Define the Architecture, this activity is best carried out by a small team staffed by cross-functional team members. Issues that are typically architecturally significant include 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. From these inputs, the team will need to be able to synthesize a model, or even a prototype, of a solution.
Usage
Usage Notes | The major effort occurs early in the Inception phase; thereafter, the system should be assessed at every iteration to ensure that the design is still on track with the architecture (see Capability Pattern: Plan and Manage Iteration).
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