Roles and Activities > Developer Role Set > Software Architect > Construct Architectural Proof-of-Concept

Purpose 
  • To synthesize at least one solution (which may simply be conceptual) that meets the critical architectural requirements.
Steps
Input Artifacts:  Resulting Artifacts:
Frequency:  Probably once only, during an inception iteration.
Role: Software Architect
Concepts: 

Workflow Details:

Decide on Construction Approach To top of page

Select the techniques to be used for construction of the Architectural Proof-of-Concept, for example:

  • Conceptual modeling
  • 'Rapid' Prototyping
  • Simulation
  • Automatic translation of specifications to code
  • 'Executable' specifications
  • Construction of  'spikes' as prototypes - vertical slices through layers

The software architect needs to be able to reason about these models, in the process discovering something about both problem and solution spaces.

Select Assets and Technologies for Architectural Proof-of-Concept To top of page

The software architect should select, from the assets and technologies identified in Activity: Architectural Analysis, those to be used in the construction of the Architectural Proof-of-Concept.

Construct Architectural Proof-of-Concept To top of page

Using the techniques selected for construction, the software architect builds the Architectural Proof-of-Concept, using the selected assets and technologies, to satisfy - to the extent required by the risk profile of the project - the architecturally significant requirements as captured in stereotypical use-case realizations, the overview design and deployment models, and the software architecture document.

Copyright  1987 - 2001 Rational Software Corporation


Display Rational Unified Process using frames

Rational Unified Process