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.157 Consolidate system data

Goal

Avoid duplications, ensure re-usability and consistency of modelled system data.

Requirements met by this process stepNone defined
Inputs

AMOD-112 System data objects [S.CDB]

AMOD-113 System exchange items [S.CDB]

AMOD-025 Abstract concepts

AMOD-034 Abstract concept states

ARCH.M.050 Method for definition of data model

Outputs

AMOD-112 System data objects [S.CDB]

AMOD-113 System exchange items [S.CDB]

AMOD-025 Abstract concepts

AMOD-034 Abstract concept states

Methodology

System data modelling has different drivers and is using various inputs (i.e. operational data, functional exchanges and the implementation of risk measures) as described in ARCH.151, ARCH.054 and ARCH.149.

Hence during this activity the existing viewpoints AMOD-112 and AMOD-113 shall be reviewed and updated, where required with focus on the following aspects:

  • Re-usability and consistency: Are all common data objects been re-used as appropriate or are there potentially two or more specific data objects defined, which are very similar in scope? In this case it should be considered to create a common data object.
  • Completeness:
    • System exchange items: Are all system exchange items actually linked to a system data items?
    • Functional exchange allocation: Are all system exchange items allocated to functional exchanges?
    • Viewpoints: Is there at least one instance of AMOD-112 per instance of AMOD-025?
  • Readability:
    • Do the instances of AMOD-112 provide good readability to convey the full definition of the respective system data.
    • Is there also an overview of all system data available as working diagram available. This helps to ensure re-usablity, consistency and completeness
Tools and non-human resourcesTeam for Capella
CardinalityAt least once per capability package prior to review ARCH.R.4.
Completion criteria

The output views conform to their modelling rules.

The exchange item definition and system data definition have been judged to be consistently defined (with respect to completeness, re-usability).

All functional exchanges on system level have at least one exchange item allocated.

Design review
Step done by (Responsible)Lead system architect
Provides input to/assists (Contributes)
  • Expert for GoA4 railway operation
  • System architect
  • Engineer
  • Cross-cutting engineer
Uses outputs (Informed)None directly.