Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.R.1 Operational capability review
Configuration status report
ARCH process configuration
The version of the ARCH process used to create the content being reviewed here is: uncontrolled edit in Confluence / unqualified release x.y / qualified release.
Content configuration
The version of the Capella model that is being reviewed here is: uncontrolled / unqualified baseline / qualified baseline.
Limitations on the use of this review
If (ARCH process version is a latest Confluence edit OR an unqualified release ) OR ( Capella model version is uncontrolled OR unqualified baseline )
Content that is reviewed here may only proceed further to next ARCH steps, Safe Enough To Try (ARCH.R.1-8) reviews, and simulation or prototyping work of TRL 1-6
Else (that is, ARCH process version is a qualified release AND Capella model version is a qualified baseline )
Content that is reviewed here may proceed further to the Safe Enough To Fly area ( ARCH.R.9/10 and GEN process )
AREV-1.1 Artefacts list
AREV-1.2 Review criteria
Activity & viewpoint completion
This section of the review is complete when
- all the tickets in the Tickets column are closed;
- modelling rule compliance has been confirmed by the review proposer.
If a line is not applicable, note the reason for this in the Notes column.
The tickets should only be closed when all produced views are fully compliant with the modelling rules.
Content criteria
This section of the review is only complete when:
- All required review roles have agreed that each review criterion has been achieved (the Achieved y/n column contains only
);
- All the tickets in the "Blocking corrective action" column have been closed;
- All non-blocking corrective actions have been ticketed and are shown in the "Non-blocking corrective action" column (note: they do not need to be closed in order for the review to complete);
- All reviewer identities and comments are recorded.
The criterion can first be evaluated in the phase indicated in column "EN 50126 phase - initial", which is the first point at which evidence becomes available. However, this evidence may be updated later. Hence, reviews at this phase are optional because they do not reflect the final picture.
The criterion must be evaluated for the final time at the phase indicated in column "EN 50126 phase - final update" because up to this point, the evidence (artefacts) may have changed during the design process.
ID Prefix AREV-1.2.2.x | EN 50126 phase - initial | EN 50126 phase - final update | Content criterion | Evidence | Achieved
| Required review role | Reviewer identity | Reviewer commentary | Blocking corrective action | Non-blocking corrective action |
---|---|---|---|---|---|---|---|---|---|---|
010 | O1 | O4 | The operational capability under review represents a genuine stakeholder need | Description of OC | Design authority | |||||
030 | O1 | O4 | Abstract concepts defined for the operational capability under review are safe enough to try | AMOD-025 | Design authority | |||||
040 | O1 | O4 | Operational states defined to support description of the operational capability under review are safe enough to try | AMOD-023 | Design authority | |||||
050 | O2 | O2 | The flow of the operational bare business process for the operational capability under review is safe enough to try. (the set of activities and the arrangement in the flow is judged to be sufficient to achieve the end conditions of the operational capability under review) | AMOD-029 | Design authority | |||||
060 | O2 | O4 | Operational interactions defined for the operational capability under review are safe enough to try | AMOD-027 | Design authority | |||||
070 | O2 | O4 | Operational activities defined for the operational capability under review are safe enough to try | AMOD-028 | Design authority | |||||
080 | O2 | O4 | Assignments of operational activities to operational states defined for the operational capability under review are safe enough to try | AMOD-028 | Design authority | |||||
090 | O2 | O4 | Exchange item definitions and supporting data types defined for the operational capability under review are safe enough to try | Design authority | ||||||
100 | O2 | O4 | Allocation of operational activities to operational actors/entities for the operational capability under review is safe enough to try | AMOD-027 | Design authority | |||||
110 | O3 | O4 | The operational safety risks associated with for the operational capability under review have been identified, assessed, and mitigated to a non-qualifiable level (safe enough to try only) | Design authority | ||||||
130 | O3 | O4 | The business risks associated with for the operational capability under review have been identified, assessed, and mitigated to a non-qualifiable level (safe enough to try only) | Design authority | ||||||
150 | O3 | O4 | The security risks associated with for the operational capability under review have been identified, assessed, and mitigated to a non-qualifiable level (safe enough to try only) | Design authority | ||||||
160 | - | O4 | The content in the scope of this review is safe enough to try starting system needs analysis on the corresponding single operational capability. | All submitted viewpoints | Lead system architect |