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.114 Define single interface layer

RCAMT-335 - Populate Confluence page for activity definition: ARCH.114 Define reusable interface layers Finished

GoalDefine interface layer and its relationships independent of a specific subsystem interface.

Requirements met by this process step

None defined
Inputs
Outputs

AMOD-100 Interface layer definition

AMOD-143 Inter-subsystem interface definition (modified)

Methodology

First step

Modify the considered AMOD-143 by adding new interface layer components to both subsystems.

  1. create a new interface layer component inside one subsystem
  2. create a new interface layer component inside the other subsystem
  3. create new component exchanges (symbolic "horizonal" component exchanges) between the two new interface layer components (from one subsystem to other subsystem)
  4. create new component exchanges (real "vertical" component exchanges) between interface layer components of this interface layer with those of the adjacent interface layers
  5. create new component exchanges (internal logical exchanges of the subsystem) between interface layer components and the existing logical components of the subsystem

Second step

Create AMOD-100 by populate and depict only the new created interface layer components and their exchanges independent from the corresponding instances of AMOD-143.


Guidance

Tools and non-human resources

Team for Capella

Cardinality

Once per every identified interface layer of a subsystem interface.

Completion criteria

The output views conform to their modelling rules.

Design review

ARCH.R.7 Subsystem capability review

ARCH.R.8 Subsystem review - consolidated

Step done by (Responsible)
  • Subsystem architect
Provides input to/assists (Contributes)
  • subsystem architect for communication/computation
  • system architect
  • engineer
Uses outputs (Informed)

None.