The purpose of this workflow detail is to construct and assess an Architectural Proof-of-Concept to demonstrate that the system, as envisioned, is feasible.

Topics

Software Architect Architectural Analysis Construct Architectural Proof-of-Concept Access Viability of Architectural Proof-of-Concept Project Specific Guidelines - initial Software Architecture Document - updated Deployment Model - overview Design Model - overview Review Record Business Case Architectureal Proof-of-Concept Reference Architecture Software Architecture Document - key use cases Glossary Supplementary Specifications - key non-functional requirements Use-Case Model - preliminary


Description To top of page

This workflow detail is about showing that there exists, or is likely to exist, a solution which will satisfy the architecturally significant requirements, thus showing that the system, as envisioned, is feasible.

Related Information To top of page

This section provides links to additional information related to this workflow detail.

Timing To top of page

Inception phase

Optionality To top of page

Optional

How to Staff To top of page

As with Workflow Detail: Define a Candidate Architecture, these activities are 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.

Work Guidelines To top of page

This work takes place during inception, and so should be limited to one or two iterations. The purpose is to determine feasibility, not to construct the system during this workflow detail.



© Copyright IBM Corp. 1987, 2004. All Rights Reserved.

Rational Unified Process   2003.06.13