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.129 Model data flowing between interface layer functions

RCAMT-343 - Populate Confluence page for activity definition: ARCH.129 Define data models for interface layers Finished

GoalDefine exchange items and data objects of an interface layer.
Requirements met by this process stepNone defined
Inputs

AMOD-100 Interface layer definition

AMOD-143 Inter-subsystem interface definition

Outputs

AMOD-094 Interface layer exchange items

AMOD-086 Interface layer data objects

Methodology

Scope

DuringĀ ARCH.128 Define functions of single interface layer new functional exchanges were created. In case additional data or information must be defined that flows along these, the following methodology shall be used.


Exchange items

Each functional exchange should have allocated at least one exchange item.

  1. Define for each exchange item the types of data via the exchange item elements. The information content of the exchange item should be defined as far as possible using an appropriate combination of data objects.
  2. Where the information content is unknown or unclear, write a text description on the exchange item, to act as a placeholder/stub until the information content is resolved (i.e. communication mechanism of exchange item is UNSET).

Data objects

When a new data object is created the rationale for their creation must be documented.

Viewpoints

Tools and non-human resources

Capella for Teams

Cardinality

Once per each interface layer.

Completion criteria

The exchange item definitions represent the best knowledge of the information content required at physical level.

Design review

ARCH.R.7 Physical review - system capability realisation

ARCH.R.8 Physical review - consolidated

Step done by (Responsible)
  • subsystem architect
Provides input to/assists (Contributes)
  • subsystem architect for comms/computation
  • System architect
  • Engineer
Uses outputs (Informed)

none