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.152 Consolidate system functionality


GoalEnsure 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 stepNone.
Inputs

AMOD-103 Consolidated system functions

AMOD-133 Consolidated system function allocation

AMOD-121 Record of system and actor functions

AMOD-122 Record of system actors

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:

  • Avoid capability silos: From the conglomerate of system functions that have been derived from one system capability some exchanges should be there to system functions derived somehow else (e.g. transferred from operational level, derived from risk measures). E.g. to get input needed from a supplier function or to send a result to a consumer function.
  • Commonality: Functions of similar scope might have been developed when derived from capabilities. Where commonality has been identified, it should be decided to combine functions.
  • Completeness: AMOD-103 should ideally contain all system functions defined, i.e. this view should provide the required overview to ensure that all functions are connected and no un-used elements are left (e.g. functions or ports). Also all functional exchanges should have exchange items allocated to (in support of ARCH.157).
  • On system level at the system level there should only be leaf-level functions
  • Consolidate the allocation of system fonctions : Add the functions currently allocated to the system and the system actors.

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;

  • Verify that all functional exchanges that cross the system boundary are allocated to a component exchange.
  • Arrange the output views in good order. This will be a large view and may not be easily printable.


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 reviewARCH.R.4 System review - consolidated
Step done by (Responsible)

Lead system architect

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

None directly.