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 step | None defined |
Inputs | AMOD-112 System data objects [S.CDB] AMOD-113 System exchange items [S.CDB] |
Outputs | AMOD-112 System data objects [S.CDB] |
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:
|
Tools and non-human resources | Team for Capella |
Cardinality | At 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) |
|
Uses outputs (Informed) | None directly. |