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.190 Consolidate logical data

RCAMT-383 - Populate Confluence page for process step ARCH.190 Consolidate logical data Finished

GoalAvoid duplications, ensure re-usability and consistency of modelled logical data.
Requirements met by this process stepNone defined
Inputs

AMOD-091 Logical data objects [L.CDB]

AMOD-092 Logical exchange items [L.CDB]

AMOD-025 Abstract concepts

AMOD-034 Abstract concept states

Outputs

AMOD-091 Logical data objects [L.CDB]

AMOD-092 Logical exchange items [L.CDB]

AMOD-025 Abstract concepts

AMOD-034 Abstract concept states

Methodology

This process step involves the review and, if required, the update of the existing viewpoints AMOD-091 and AMOD-092, with focus on the following aspects:

  • Re-usability and consistency: Are all common data objects 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:
    • Logical exchange items: Are all logical exchange items actually linked to a logical data item?
    • Functional exchange allocation: Are all logical exchange items allocated to functional exchanges?
    • Viewpoints: Is there at least one instance of AMOD-091 per instance of AMOD-025?
  • Readability:
    • Do the instances of AMOD-091 provide good readability to convey the full definition of the respective logical data?
    • Is there also an overview of all logical data available as working diagram? This helps to ensure re-usablity, consistency and completeness
Tools and non-human resources

Team for Capella

CardinalityAt least once per capability package prior to review ARCH.R.5.
Completion criteria

The output views conform to their modelling rules.

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

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

Design reviewARCH.R.5 Logical capability review
Step done by (Responsible)

Lead system architect

Provides input to/assists (Contributes)
  • System architect
  • Subsystem architect
  • Engineer
Uses outputs (Informed)

None directly.