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.098 Define selected subsystem option

GoalDefinition/Modelling of a set of subsystems and deploy logical components.
Requirements met by this process step

ISO 15288 6.4.4.3 c)

ISO 15288 6.4.4.3 d)

EN 50126-1 7.3.2.1 b)

Inputs

AMOD-080 Subsystem option sketch

AMOD-124 Subsystem architecture tradeoff record

Outputs

AMOD-093 Subsystem architecture definition

AMOD-085 Subsystem architecture definition (single realised capability)

Methodology

Main steps

  1. Implement the decisions done in ARCH.097
  2. Define and model each component, function and subsystem based on the inputs of this process step.
  3. Justify each subsystem with a rationale.

Create the viewpoint AMOD-085 Subsystem architecture definition (single realised capability) for the realised capability of interest. A selection of subsystems shall be modeled there including the deployed logical components, their logical exchanges to the involved actors and the allocated functions.

  1. Select a subset of the defined subsystems and actors which are involved in a single realised capability of interest.
  2. Arrange the subset of the subsystems and the involved actors on the diagram.
  3. Deploy the logical components to the subsystems based on AMOD-124.
    1. Note: where there exists the possibility for a logical component(+allocated functions) to be carried out by more than one subsystem depending on the diffrent subsysten boundaries, the logical component should be defined once as a replicable element catalogue (REC) without being deployed, then replicas (RPL) of the logical component should be created and deployed to the respective subsystem.
  4. Define a rationale to justify the deployment of a logical component to a subsystem (only if it is otherwise not clear how you came to that decision).
  5. Arrange the logical component exchanges of the logical components between two subsystems and between a subsystem and a actor.
  6. Show all functions which are allocated to a deployed logical component of a subsystem.
  7. Show all functions which are allocated to a actor and which have a functional exchange connected to a function allocated to at least one of the before deployed logical components.
  8. Arrange the functions and functional exchanges.

Note: it is possible to copy the layout (functionality which is provided by Capella) from the logical level AMOD-125 because this viewpoint only added the subsystem. The rest of the content should be the same which is shown on AMOD-125 for a single realised capability.

Create AMOD-093 Subsystem architecture definition. All subsystems shall be modelled there concretely in an overall picture including the deployed logical components and their logical exchanges to actors.

  1. Show all the deployed logical components to the subsystems.
  2. Show all actors which will linked to a subsystem.
  3. Show all logical component exchanges of logical components between two subsystems and between a subsystem and an actor.

Note: Functions are not shown in AMOD-093 Subsystem architecture definition.

Guidance: Physical links between two subsystems may not be modelled always. A physical link doesn't always exist between two subsystems directly but rather could go into for example a network port of the communications platform. This will be added in later steps of the process.

Tools and non-human resources

Team for Capella

Cardinality

Once per subsystem with selected subsystem boundaries.

Completion criteria

All intended subsystems are defined.

Design review

ARCH.R.8 Subsystem review - consolidated

Step done by (Responsible)

Lead systems architect

Provides input to/assists (Contributes)
  • System architect
  • Subsystem architect
  • Engineer
Uses outputs (Informed)

None.