Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.056 Map system functionality to states
SM-2798
-
Populate Confluence page for activity definition: ARCH.056 Map system functionality to states/modes
Finished
Goal | Gain understanding of state-based changes to the system's behaviour |
---|---|
Requirements met by this process step | None defined |
Inputs | System/actor states from collaborative projects (optional) |
Outputs | AMOD-055 System functions to state allocation map [Matrix] Output is a set of new relationships in the model according to the architectural tuple below: system function is available in system state |
Methodology | System functions may not be available all the time. Their availability may be dependent on a system state or mode. If relevant states are already defined within a collaborative project, these should be referred to and utilised for this activity, where appropriate. This activity should be carried out in parallel to the modelling of system functionality for a single system capability. The scope of the activity is all system functions involved in the capability. For each state dimension (that is, each individual state machine or state machine region on the system): If a system function is only available in certain system states Allocate the function to those states where it is available; Else if a system function is available independently of this state dimension: Allocate the function to all states in this dimension end for |
Tools and non-human resources | Team for Capella |
Cardinality | Once per system capability |
Completion criteria | All system functions involved in this capability are allocated to the correct states |
Design review | ARCH.R.3 System capability review |
Step done by (Responsible) | System architect |
Provides input to/assists (Contributes) | Cross-cutting engineer |
Uses outputs (Informed) | None directly |