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.156 Define single inter-subsystem interface

RCAMT-353 - Create Confluence page for activity definition ARCH.156: Define single inter-subsystem interface Finished

GoalDefine a single inter-subsystem interface between two subsystems.
Requirements met by this process stepNone defined
Inputs

AMOD-093 Subsystem architecture definition

AMOD-085 Subsystem architecture definition (single realised capability)

AMOD-100 Interface layer definition

OutputsAMOD-143 Inter-subsystem interface definition
Methodology

First step: identify the inter-subsystem interface

Consider a pair of two subsystems provided by AMOD-085 and AMOD-093. A candidate for an inter-subsystem interface is indicated from the situation that are existing inter-subsystem exchanges (logical component exchanges) between logical components deployed to each of the two subsystems crossing those boundary of those subsystems.

Decide then which kind of interface is intended and needed. This shall take into account design decisions made in ARCH.934 for the physical architecture.

possible categories of inter-subsystem interfaces
  • network communication interface
    • e.g. protocol stacks
  • human-machine interface
    • e.g. user interfaces
  • hardware interface
    • e.g. 4-wire point machine interface
    • e.g. power supply interface
  • software interface
    • e.g. application programming interface

Note: Where it is not possible or practical to model the interface with the aforementioned categories, another one shall be identified and selected.

Second step: define the inter-subsystem interface

This process step as well as the corresponding process step ARCH.114 Define single interface layer are performed in parallel. This is required to define the inter-subsystem interface in the whole showing the interconnections of all interface layers as well as to focus on each interface layer itself.

Process stepactions
this

create AMOD-143 Inter-subsystem interface definition for inter-subsystem interface as a whole

actions for the considered subsystems (inside each):

  • define real "vertical" component exchanges between the interface layer components of different interface layers
  • define internal logical component exchanges between the interface layer components and the existing logical components

actions between the subsystems:

  • define the inter-subsystem interface by creating the physical interface (i.e. physical link) between the two considered subsystems and allocate then all symbolic "horizontal" component exchanges to that link
ARCH.114 Define single interface layer

create AMOD-100 Interface layer definition for each interface layer

  • define interface layer components of the interface layer for each subsystem

Guidance

Tools and non-human resources

Team for Capella

CardinalityOnce per every identified pair of two subsystems.
Completion criteriaThe 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 architects of the interfacing subsystems
Provides input to/assists (Contributes)
  • subsystem architect for communication/computation
  • system architect
  • engineer
Uses outputs (Informed)

none