Legal information

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 complianceArtefactS1S2S3S4Identities of views createdModelling rules compliance (tick)/(error)Notes
FullAMOD-025 Abstract conceptsUpdatedUpdated-Updated

Only to be updated if new abstract concepts are revealed during system analysis.
FullAMOD-116 System implementation constraintsInitial---


FullAMOD-045 System capabilitiesInitialUpdatedUpdatedUpdated


FullAMOD-104 System level - operational level traceability reportInitialUpdatedUpdatedUpdated


FullAMOD-046 Selected system boundary tradeoff record-Initial--


FullAMOD-049 Non-functional requirements implementation-InitialUpdatedUpdated


FullAMOD-050 Stakeholder non-functional requirements-InitialUpdatedUpdated


FullAMOD-119 System context definition-InitialUpdatedUpdated


FullAMOD-055 System functions to state allocation map [Matrix]-InitialUpdatedUpdated

This viewpoint may be updated after the system function consolidation step, which is why it needs to be checked in the consolidated review.
FullAMOD-056 System functions and exchanges (single system capability)-InitialUpdatedUpdated

This viewpoint may be updated after the system function consolidation step, which is why it needs to be checked in the consolidated review.
FullAMOD-057 Measures of performance-Initial or updatedUpdatedUpdated

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.
FullAMOD-058 Initial system exchange scenario-Initial--


FullAMOD-059 Initial system functional chain description-Initial--


FullAMOD-060 System/actor states-InitialUpdatedUpdated


FullAMOD-112 System data objects [S.CDB]-InitialUpdatedUpdated


FullAMOD-113 System exchange items [S.CDB]-InitialUpdatedUpdated


FullAMOD-114 System interface definition-InitialUpdatedUpdated


FullAMOD-115 External interface behaviour-InitialUpdatedUpdated


FullAMOD-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.
FullAMOD-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.
FullAMOD-117 System exchange scenarios with risk control measures [S.ES]---Initial


FullAMOD-118 System functional chain descriptions with risk control measures [SFCD]---Initial


FullAMOD-103 Consolidated system functions---Initial


FullAMOD-133 Consolidated system function allocation-InitialUpdatedUpdated


FullAMOD-146 System needs and constraints tradeoff decision record---Initial


FullAMOD-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.

ID

Prefix AREV-4.2.1.x

EN 50126 phaseActivityTicketsViewpoint output

Scope of compliance

Notes

010

S1ARCH.035 Identify constraints on the system solution
AMOD-116Full
020S1ARCH.036 Identify all alternative system boundaries
AMOD-041No need to review output of this stepThis is an intermediate process step and is only needed to proceed to ARCH.042
030S1ARCH.042 Select system boundary (or set of variants)



040
AMOD-046Full
050S1ARCH.049 Define set of potential system capabilities/missions
AMOD-120No need to review output of this stepThis is an intermediate process step and is only needed to proceed to ARCH.041, ARCH.119 and ARCH.045.
060S1ARCH.039 Define set of potential system and actor functions
AMOD-121No need to review output of this stepThis is an intermediate process step and is only needed to proceed to ARCH.041, ARCH.119 and ARCH.045.
070S1ARCH.043 Define set of potential system actors
AMOD-122No need to review output of this stepThis is an intermediate process step and is only needed to proceed to ARCH.041, ARCH.119 and ARCH.045.
080S1ARCH.041 Transfer or trace upper level model elements to system level

AMOD-103

AMOD-104

FullFurther outputs will be generated by the process steps ARCH.119
and ARCH.045
090S2ARCH.119 Define consolidated set of system capabilities/missions

AMOD-045

AMOD-120

Full
100S2ARCH.058 Define measures of performance
AMOD-057Full
110S2ARCH.048 Identify system implementation constraints
AMOD-049Full
120S2ARCH.044 Define requirements from non-actor stakeholders
AMOD-050Full
130S2ARCH.045 Define complete set of system-level actors

AMOD-119

AMOD-122

Full
140S3All risk assessment process steps are carried out on a single capability (which might own multiple scenarios)


AMOD-004Full
150
AMOD-071Full
160S4ARCH.157 Consolidate system data


AMOD-112Full
170
AMOD-113Full
180

S4

ARCH.152 Consolidate system functionality

AMOD-103

AMOD-121

Full
190
AMOD-133Full
200S4ARCH.081 Update constraints on system solution
AMOD-116Full
210S4ARCH.082 Trade off system requirements and constraints
AMOD-146Full
220S4ARCH.083 Agree the system requirements with stakeholders
AMOD-079Full

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 (tick) );
  • 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 - initialEN 50126 phase - final updateContent criterionEvidence

Achieved 

(tick)/(error)

Required review roleReviewer identityReviewer commentaryBlocking corrective actionNon-blocking corrective action
010S1S4The set of system capabilities is necessary and sufficient to fulfill all the operational needs of this package/version/variant/release.AMOD-045
Design authority



020S1S4The set of abstract objects is necessary and sufficient for the capabilities in this package/version/variant/release.AMOD-025
Design authority



030S2S4All the system actors have been identified who are relevant to the capabilities in this package/version/variant/release.

AMOD-045

AMOD-119


Design authority



040S2S4State models for the system or actors are safe enough to try.AMOD-060
Design authority



050S2S4The 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



060S2S4The outcome of any system boundary tradeoffs is safe enough to try.AMOD-046
Design authority



070S2S4

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).

AMOD-114

AMOD-115


Design authority



080S3


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.


AMOD-071

AMOD-004




Design authority



090
Expert reviewer (safety)



100
Expert reviewer (RAM)



110
Expert reviewer (security)



120S4S4Cross-references between functional chains (including robustness measures) are consistent and safe enough to try.AMOD-118
Design authority



130S4S4Cross-references between system exchange scenarios (including robustness measures) are consistent and safe enough to try.AMOD-117
Design authority



140S4S4The results of tradeoffs between system needs and constraints are safe enough to try.AMOD-146
Design authority



150S4S4The stakeholders have agreed the baseline of system requirements in the model.AMOD-079
Design authority