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.176 Create subsystem exchange scenarios

RCAMT-322 - Create Confluence page for process step ARCH.176 BACKLOG

WIP

RCAMT-801 - Gap closure (SR-020) Populate Confluence pages for scenarios at physical layer Finished

Goal

Visualise subsystem black-box behaviour or subsystem interaction behaviour with actors (or external systems) or other subsystems.

Requirements met by this process stepNone identified
Inputs

AMOD-148 Subsystem capability realisation

AMOD-085 Subsystem architecture definition (single realised capability)

Method for definition of scenarios

OutputsAMOD-140 Subsystem exchange scenario
Methodology

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

Where new functions or functional exchanges are identified, these should be first created on the corresponding XXX.

Tools and non-human resourcesTeam for Capella
Cardinality

Zero to n times per realised system capability (as many different sequences should be created as are judged necessary to gain confidence in the design)

Completion criteria

The output view conforms to its modelling rules.

The content of the output view represents the team's current understanding of the way this realised system capability is intended to be delivered.

All necessary and intended scenarios are created.

Design reviewARCH.R.8 Subsystem review - consolidated
Step done by (Responsible)
  • Subsystem architect
Provides input to/assists (Contributes)
  • Lead System architect
  • System architect
  • Engineer
Uses outputs (Informed)None identified