Task Descriptor: Assess Viability of System Architecture Proof-of-Concept
This task defines how to evaluate a System Architecture Proof-of-Concept against Architectural Requirements and Risks.
Based on Method Task:  Assess Viability of System Architecture Proof-of-Concept
Relationships
Performing RolesMain: Additional: Assisting:
InputsMandatory: Optional: External:
Outputs
Steps
Determine evaluation criteria

The criteria against which the System Architecture Proof-of-Concept is to be evaluated are drawn from the architecturally significant requirements, which were the drivers in its construction. This is analogous to the construction of system test cases that occurs in later phases. The evaluation criteria can be quite narrowly defined, depending on the risk to be elucidated. For example, if the system had a requirement for unprecedented thermal resistance, but was otherwise unexceptional, the System Architecture Proof-of-Concept and the evaluation criteria might focus exclusively on the shielding or refrigeration aspects of the solution.

Evaluate Architectural Proof-of-Concept

In this step, the System Architecture Proof-of-Concept is tested against the evaluation criteria: the way in which this is done depends on the form of the proof-of-concept. For example, in the case of a working physical model or prototype, this can be through demonstration and test; in the case of a conceptual model, through inspection and reasoning; or, for a simulation, requiring the set-up and running of the simulation model with input data derived from the evaluation criteria, then through the collection and analysis of output data from the model.

Assess results

Assessment of the results from the evaluation determine not only if the architecturally significant requirements can be satisfied, but also check the validity of those requirements. At this time in the development, requirements are still mutable, and not necessarily well-understood by the stakeholders; for example, perhaps the opportunity exists to relax requirements that were shown to be high-risk by the evaluation of the System Architecture Proof-of-Concept. All these avenues need be thoroughly explored in assessing the results. This approach contrasts with the situation later in elaboration and construction, when there is much greater reluctance to change or reinterpret requirements. After the assessment, with a better understanding of scope and feasibility by all stakeholders, change proposals to the Business Case, Vision, and Risk List are prepared, if necessary.

Properties
Multiple Occurrences
Event-Driven
Ongoing
Optional
Planned
Repeatable