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.153 Model data flowing between operational activities

GoalDefine and capture the specific information content needed for exchange between operational entities/actors
Requirements met by this process step

RiL 114.0210 05 (6) (partial)

[ISO 27001]

Inputs

AMOD-027 Operational bare business scenario

AMOD-028 Operational activities and interaction definitions (single operational capability)

AMOD-029 Operational bare business process

AMOD-025 Abstract concepts (limited scope)

AMOD-034 Abstract concept states

ARCH.M.050 Method for definition of data model

Outputs

AMOD-025 Abstract concepts (limited scope updated)

AMOD-105 Operational data objects [O.CDB]

AMOD-110 Operational exchange items [O.CDB]

AMOD-034 Abstract concept states

Methodology

As an operational capability is built up as a process and as an exchange scenario, it is important to define the information content carried by interactions between operational entities. 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 operational needs.

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] for existing reusable data objects and types, before creating new ones. It is not allowed to have identical data model elements more then once.

Exchange item viewpoint

Check all instances of AMOD-110 Operational exchange items [O.CDB] for existing reusable exchange items, before creating new ones. It is not allowed to have identical data model elements more then once.

Tools and non-human resources

Team for Capella

Cardinality

Once per operational capability, revisions allowed.

Completion criteria

The output views conform to their modelling rules.

Design review

ARCH.R.1 Operational capability review

ARCH.R.2 Operational review - consolidated


Step done by (Responsible)

Operational concept architect


Provides input to/assists (Contributes)

System architect

Systems engineer

Cross-cutting engineer

Uses outputs (Informed)

None directly.