Task Descriptor: Demonstrate the Architecture
Present at least one solution that proves the planned architecture will meet the requirements.
Based on Method Task:  Demonstrate the Architecture
Relationships
RolesMain: Additional: Assisting:
InputsMandatory: Optional: External:
  • None
Outputs
Steps
Define objectives

Define the scope and objectives of the proof-of-concept.

List the questions and unknown quantities about the architecture that must be understood to be confident of the architectural approach. These issues guide the construction of the proof-of-concept. The success of the proof-of-concept is measured by its ability to illuminate these issues.

The objectives describe what parts of the archtecture are at risk and need to be understood before investing significant effort in the project. For example, if new COTS software will be part of the architecture it may be useful to understand how the system under development will integrate with the COTS software, and understand what issues other organizations have had with integrating the third-party software.


Decide on construction approach

Select a format for the proof-of-concept that addresses the objectives.

Select a format that:

  • Illustrates the architectural philosophy of the system.
  • Addresses the objectives defined earlier.
  • Identifies key architectural elements such as areas that may have performance or security issues.

The proof-of-concept can take many forms depending on the novelty of the architecture and the difficulty of the requirements. See Guideline: Create Architectural Proof of Concept for guidance on selecting an aproach and validating the proof-of-concept.

Construct the proof-of-concept

Construct the architectural proof-of-concept using the chosen construction approach.

This effort could take less than a day or up to a few days, depending on the construction approach selected. However, a rare worst-case scenario could require constructing and validating up to 80% of the actual architecture before achieving enough confidence that it will support the requirements.

Properties
Multiple Occurrences
Event-Driven
Ongoing
Optional
Planned
Repeatable