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.112 Execute vertical transition from logical architecture of parent model to system analysis of child model

  Draft
GoalProvide the inputs needed to develop the system analysis of a child model in alignment with the logical architecture of a parent model
Requirements met by this process stepNot defined
Inputs

Logical component considered as a constituent system from the parent model

ARCH.M.060 Method for the execution of automatic transition in capella

01-Method page for System of Systems approach

Outputs

Model elements on the system level of a child model

Methodology

Context

This step is related to the system of systems approach whose overall methodology is described here: Method page for SoS Approach with more guidance and definition of terms. There are two distinct cases where a child model can be linked to a parent model. In this case, we need to create a new child model where the logical component selected as a constituent system will be the new system of interest.

Methodology

See "Vertical transition between LA layer of parent model and SA layer of new child models" ->ARCH.M.060 Method for the execution of automatic transition in capella

Tools and non-human resources

Team for Capella

System-to-SubSystems Capella plugin

Cardinality

At least once per logical component considered as a constituent system and not linked to an already existing child model.

Carried out as required to maintain synchronization between the logical level of the parent model and the system level of the child model under consideration.

Completion criteria

The logical component selected for the child model is well transitioned at the system analysis of the child model, with all the other external systems/logical components interacting with it.

The set of capabilities in the child model includes all capabilities to be delivered within the set under consideration.

Design reviewNo design review checks this since it is an intermediate step, but the work should be coordinated and checked by the cross-cutting engineer especially to check if the scope is well derived for each child model
Step done by (Responsible)

Cross-cutting engineer/Lead system architect

Provides input to/assists (Contributes)
  • Engineer
  • Cross-cutting engineer
  • Subsystem Architect
Uses outputs (Informed)

Engineers responsible for the child model design and management