Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
Definition of scope of compliance
The review structure is designed to be flexible and allow quick progress. Because of this, there are variations in the scope of the reviews, in order to prevent a review being held up because of deficiencies in an artefact that are not related to the scope of the review.
Broadly speaking, there are two types of artefact produced in the ARCH process:
- Artefacts that are focused on only one system capability - "capability-based" artefacts;
- Artefacts that are consolidated across multiple system capabilities - "consolidated" artefacts.
Consolidated artefacts may be created to cover a subset (package) of the whole set of system/operational capabilities as defined by capability phasing/roadmaps. This allows consolidated system designs to be released for implementation when they achieve the set of system capabilities needed to meet a particular set of stakeholder needs that may not be the full set.
Some consolidated artefacts need to be reviewed in both the capability-based review (reviews 1, 3, 5, and 7) AND the consolidated review (reviews 2, 4, 6, 8, 9, and 10).
Definition
"Capability-based" compliance means that a consolidated artefact's contents need only be complete and correct from the point of view of the capability of interest. Any content in the artefact that is not related to the capability of interest does not need to be reviewed to establish this level of compliance.
"Full" compliance means that a consolidated artefact's contents need to be complete and correct from the point of view of the set of capabilities of interest over which the design work is being consolidated. There should not be any content in the artefact that is not related to a capability included in the package. This means that everything that is visible/included in the artefact must be complete and correct.