Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.054 Model data flowing between system functions
Goal | Capture the requirements for information/data flow between system functions |
---|---|
Requirements met by this process step | ISO 15288 6.4.2.3 b 1), c 2) EN 50126-1 7.2.2 a), 7.3.2.1 a) |
Inputs | There may be existing views to which the data for the current system capability can be added, but if not, then create new views. AMOD-056 System functions and exchanges (single system capability) AMOD-110 Operational exchange items [O.CDB] AMOD-105 Operational data objects [O.CDB] |
Outputs | AMOD-025 Abstract concepts (updated) AMOD-112 System data objects [S.CDB] (updated) AMOD-113 System exchange items [S.CDB] (updated) AMOD-034 Abstract concept states (updated) |
Methodology | During the (ARCH.052 and ARCH.053) 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] for existing reusable data objects and types, 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 operational level, please create a new data object 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] 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 higher level, please create a new exchange item and link it via a realisation to the corresponding data object at the higher level. |
Tools and non-human resources | Team for Capella |
Cardinality | Once 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 system level. |
Design review | ARCH.R.3 System capability review |
Step done by (Responsible) | Lead system architect |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | None directly |