Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.R.4 System review - consolidated
AREV-4.1 Artefacts list
Scope of compliance | Artefact | S1 | S2 | S3 | S4 | Identities of views created | Modelling rules compliance ![]() ![]() | Notes |
---|---|---|---|---|---|---|---|---|
Full | AMOD-025 Abstract concepts | Updated | Updated | - | Updated | Only to be updated if new abstract concepts are revealed during system analysis. | ||
Full | AMOD-116 System implementation constraints | Initial | - | - | - | |||
Full | AMOD-045 System capabilities | Initial | Updated | Updated | Updated | |||
Full | AMOD-104 System level - operational level traceability report | Initial | Updated | Updated | Updated | |||
Full | AMOD-046 Selected system boundary tradeoff record | - | Initial | - | - | |||
Full | AMOD-049 Non-functional requirements implementation | - | Initial | Updated | Updated | |||
Full | AMOD-050 Stakeholder non-functional requirements | - | Initial | Updated | Updated | |||
Full | AMOD-119 System context definition | - | Initial | Updated | Updated | |||
Full | AMOD-055 System functions to state allocation map [Matrix] | - | Initial | Updated | Updated | This viewpoint may be updated after the system function consolidation step, which is why it needs to be checked in the consolidated review. | ||
Full | AMOD-056 System functions and exchanges (single system capability) | - | Initial | Updated | Updated | This viewpoint may be updated after the system function consolidation step, which is why it needs to be checked in the consolidated review. | ||
Full | AMOD-057 Measures of performance | - | Initial or updated | Updated | Updated | Only to be created initially if this is the first package of system capabilities. Created on a capability-wise basis, but needs to be reviewed in the consolidated review to ensure the measures of performance make sense for the entire package of capabilities. | ||
Full | AMOD-058 Initial system exchange scenario | - | Initial | - | - | |||
Full | AMOD-059 Initial system functional chain description | - | Initial | - | - | |||
Full | AMOD-060 System/actor states | - | Initial | Updated | Updated | |||
Full | AMOD-112 System data objects [S.CDB] | - | Initial | Updated | Updated | |||
Full | AMOD-113 System exchange items [S.CDB] | - | Initial | Updated | Updated | |||
Full | AMOD-114 System interface definition | - | Initial | Updated | Updated | |||
Full | AMOD-115 External interface behaviour | - | Initial | Updated | Updated | |||
Full | AMOD-004 Fault tree (per operational deviation) | - | - | Initial or updated | - | Only to be created initially if this is the first time a system-level deviation has been identified that can lead to this operational deviation; otherwise, update the existing fault tree. | ||
Full | AMOD-071 System failure modes and effects analysis | - | - | Initial or updated | - | Only to be created initially if this is the first package of system capabilities to be designed. | ||
Full | AMOD-117 System exchange scenarios with risk control measures [S.ES] | - | - | - | Initial | |||
Full | AMOD-118 System functional chain descriptions with risk control measures [SFCD] | - | - | - | Initial | |||
Full | AMOD-103 Consolidated system functions | - | - | - | Initial | |||
Full | AMOD-133 Consolidated system function allocation | - | Initial | Updated | Updated | |||
Full | AMOD-146 System needs and constraints tradeoff decision record | - | - | - | Initial | |||
Full | AMOD-079 Agreed system requirements baseline (functional + non functional) | - | - | - | Initial |
AREV-4.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-4.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 | S1 | S4 | The set of system capabilities is necessary and sufficient to fulfill all the operational needs of this package/version/variant/release. | AMOD-045 | Design authority | |||||
020 | S1 | S4 | The set of abstract objects is necessary and sufficient for the capabilities in this package/version/variant/release. | AMOD-025 | Design authority | |||||
030 | S2 | S4 | All the system actors have been identified who are relevant to the capabilities in this package/version/variant/release. | Design authority | ||||||
040 | S2 | S4 | State models for the system or actors are safe enough to try. | AMOD-060 | Design authority | |||||
050 | S2 | S4 | The set of system and actor functions is necessary and sufficient to realise all the capabilities in this package/version/variant/release. | AMOD-103 | Design authority | |||||
060 | S2 | S4 | The outcome of any system boundary tradeoffs is safe enough to try. | AMOD-046 | Design authority | |||||
070 | S2 | S4 | The constrained aspects of external interfaces are fully specified for the scope of this package/version/variant/release. Note: Where aspects of an external interface are not constrained e.g. by external standards, it is not necessary for them to be fully specified until the physical level review (ARCH.R.8). | Design authority | ||||||
080 | S3 | S3 | The system risk assessments/treatments have been completed without gaps or overlaps for the set of system capabilities in this package/version/variant/release. | Design authority | ||||||
090 | Expert reviewer (safety) | |||||||||
100 | Expert reviewer (RAM) | |||||||||
110 | Expert reviewer (security) | |||||||||
120 | S4 | S4 | Cross-references between functional chains (including robustness measures) are consistent and safe enough to try. | AMOD-118 | Design authority | |||||
130 | S4 | S4 | Cross-references between system exchange scenarios (including robustness measures) are consistent and safe enough to try. | AMOD-117 | Design authority | |||||
140 | S4 | S4 | The results of tradeoffs between system needs and constraints are safe enough to try. | AMOD-146 | Design authority | |||||
150 | S4 | S4 | The stakeholders have agreed the baseline of system requirements in the model. | AMOD-079 | Design authority |