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.087 Model data flowing between logical functions

GoalCapture the requirements for information/data flow between logical functions.
Requirements met by this process stepISO 15288 6.4.4.3 c) 4
Inputs

AMOD-081 Logical functional flow definition (single system capability realisation)

AMOD-025 Abstract concepts

AMOD-112 System data objects [S.CDB]

AMOD-113 System exchange items [S.CDB]

AMOD-034 Abstract concept states

ARCH.M.050 Method for definition of data model

Outputs

AMOD-025 Abstract concepts (Updated)

AMOD-091 Logical data objects [L.CDB]

AMOD-092 Logical exchange items [L.CDB]

AMOD-034 Abstract concept states

Methodology

During the ARCH.182 new functional exchanges will be created. In case additional data or information must be defined that flows along these the following methodology shall be used ARCH.M.050 Method for definition of data model.

Abstract concept viewpoint

Concepts are defined in AMOD-025 Abstract concepts. These conceptual data model may be updated, and/or new concepts might be identified during definition of the logical architecture.

If a new abstract concept is to be defined, follow the process step ARCH.008 Define abstract concepts relevant to the wider system of interest.

Data object viewpoint

Check all instances of AMOD-105 Operational data objects [O.CDB] and AMOD-112 System data objects [S.CDB] and AMOD-091 Logical data objects [L.CDB] for existing reusable data objects, before creating new ones. It is not allowed to have identical data model elements on multiple levels. If there is a need to refine or change a data object from system level, please create a new data object at the logical level and link it via a realisation to the corresponding data object at the higher level.

Exchange item viewpoint

Check all instances of AMOD-110 Operational exchange items [O.CDB] and AMOD-113 System exchange items [S.CDB] and AMOD-092 Logical exchange items [L.CDB] for existing reusable exchange items, before creating new ones. It is not allowed to have identical data model elements on multiple levels. If there is a need to refine or change an exchange item from system level, please create a new exchange item at the logical level and link it via a realisation to the corresponding data object at the higher level.

Tools and non-human resourcesTeam for Capella
CardinalityOnce per system capability
Completion criteria

The output views conform to their modelling rules.

The exchange item definitions represent the best current knowledge of the information content required for exchange at logical level

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