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.130 Define interface layer exchange scenarios

RCAMT-538 - Populate Confluence page for activity definition: ARCH.130: Define interface layer scenarios Finished

Goal

Define the behaviour with scenarios between interface layer components of an interface layer.

Requirements met by this process stepNone defined
Inputs

Method for definition of scenarios


OutputsAMOD-099 Interface layer exchange scenario
Methodology

Define scenarios of interface layer

Create AMOD-099 for corresponding interface layer.

  1. Populate the interface layer components of the considered interfacer layer on the scenario.
  2. Populate the symbolic functional exchanges between interface layer components on the scenario.
  3. Populate the involved functions on the scenario for each interface layer component.
  4. Arrange them in the necessary order based on design decisions and prerequisites of the behaviour definition of each function.
  5. Define the pre-and postconditions of the scenario.
  6. If necessary, add time duration constraints and/or state invariants to the scenario.

See the chapter "Specific guidance for scenarios applicable at the subsystem architecture" in Method for definition of scenarios for more guidance.

Tools and non-human resources

Capella for Teams

Cardinality
  • Inside the scope of a realised system capability: zero to n times per considered capability (as many different sequences should be created as are judged necessary to gain confidence in the design)
  • Outside the scope of a realised system capability: zero to m times as required (as many different sequences should be created as are judged necessary to gain confidence in the design)

For lower layers (e.g. towards physical layer) there might be fewer scenarios (max. m) than for upper layers like the application layer (max. n).

Completion criteria

All necessary and intended scenarios are created.

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