Representation Options | UML Representation:
The decision about whether or not a System Architecture Proof-of-Concept is required and what form it must
take depends on:
-
How well the domain is understood. If the domain is unfamiliar, the System Architecture
Proof-of-Concept might not only explore possible solutions, but can also help the customer and
development organizations understand and clarify important requirements.
-
The novelty of the system. If the development organization has constructed many such systems
previously, then it should not be necessary to build a proof-of-concept. It might be possible to base a
determination of feasibility on existing reference architectures and technologies.
-
Whether or not, even though the domain is familiar and the system is precedented, any of the
requirements are judged to be particularly onerous; for example, extreme reliability or survivability
are required, or the system must function in a particularly hostile physical environment (for example,
subjected to high temperature or extreme radiation levels).
The higher the risk, the more effort needs to be put into this system architectural synthesis activity in
Inception (with the expectation of more realistic results from the models or prototypes produced and
assessed), so that all stakeholders can be convinced that the basis for committing funds and continuing
into Elaboration is credible. However, it has to be recognized that all risks cannot be eliminated in this
phase. Do not distort the Inception phase into a de-facto Elaboration phase.
|