Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.152 Consolidate system functionality
Goal | Ensure consistency of system functions, their exchanged functional exchanges and that all system functions are allocated correctly to either the system or the system actors. |
---|---|
Requirements met by this process step | None. |
Inputs | AMOD-103 Consolidated system functions AMOD-133 Consolidated system function allocation |
Outputs | AMOD-103 Consolidated system functions AMOD-133 Consolidated system function allocation It may be necessary to propagate any modifications to AMOD-055 System functions to state allocation map [Matrix] AMOD-056 System functions and exchanges (single system capability) AMOD-058 Initial system exchange scenario AMOD-059 Initial system functional chain description AMOD-115 External interface behaviour AMOD-117 System exchange scenarios with risk control measures [S.ES] AMOD-118 System functional chain descriptions with risk control measures [SFCD] AMOD-121 Record of system and actor functions (automatically updated with a tool) AMOD-122 Record of system actors (automatically updated with a tool) |
Methodology | This activity shall ensure that the system functions for the system as a whole do fit together. As exemplary guidance the following aspects should be considered:
All function on system level should be allocated to an actor or to the system. For each function that is not yet allocated Determine if this function is ever used. If it is used determine (with the owner of the corresponding capability), if it can be allocated to a system or to which actor it should be allocated to; else if not make it a candidate for deletion;
Caution! Where this process step results in changes to the existing system functions and/or exchanges, they must be updated on all views where they are used (including the viewpoints for the single system capabilities). the single-capability views must not be allowed to lose consistency with the consolidated views. |
Tools and non-human resources | Team for Capella |
Cardinality | At least once per capability package prior to review ARCH.R.4. |
Completion criteria | The output view conforms to its modelling rules. The whole set of system functions is safe enough to try. The allocation of system functions is an accurate representation of the system scope. |
Design review | ARCH.R.4 System review - consolidated |
Step done by (Responsible) | Lead system architect |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | None directly. |