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.154 Consolidate logical functional flow

GoalEnsure consistency of logical functions and their exchanged functional exchanges for each logical component.
Requirements met by this process stepNone.
Inputs

AMOD-081 Logical functional flow definition (single system capability realisation)

AMOD-082 Logical functional chain definition

AMOD-084 Logical exchange scenario definition

AMOD-125 Logical architecture definition

Outputs

AMOD-088 Consolidated logical functional flow definition

AMOD-081 Logical functional flow definition (single system capability realisation) (updated)

AMOD-082 Logical functional chain definition (updated)

AMOD-084 Logical exchange scenario definition (updated)

AMOD-125 Logical architecture definition (updated)

Methodology

The logical functions, their functional exchanges and the allocated exchange items have been developed using the input transferred from system level (ARCH.084) or they have been derived per capability realisation (ARCH.182/ARCH.085/ARCH.086).

This activity shall ensure that the logical functions for each logical component as a whole do fit together. As exemplary guidance the following aspects should be considered:

  • Avoid capability silos: From the conglomerate of logical functions that have been derived from one capability realisation some exchanges should be there to logical functions derived somehow else (e.g. transferred from system level, derived from risk measures). E.g. to get input needed from a supplier function or to send a result to a consumer function. In other words, maximise the re-use of logical functions in more than one capability realisation, as opposed to having new and separate functions for each capability realisation.
  • 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.
  • Removal of duplicates: Where duplication or scope overlaps are identified, resolve these with common functions where possible, re-link/re-involve functions that have changed (including updating functional chains and scenarios) and delete the duplicates only once they have been fully disconnected from the rest of the model.
  • Removal of transferred system function which were split into logical functions in ARCH.182.
    Before deleting a function please check if other diagrams are affected, if this is the case correct the layout of this diagrams by removing the function out of this diagram. Also check if all realised links from the logical functions to the corresponding system function are set correctly.
  • Completeness: AMOD-088 should ideally contain all logical 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.
  • If there are changes to the set of logical functions and functional exchanges, which need to be propagated manually to any functional chains or scenario.

    For each logical functional chain/scenario
    If involved functions were deleted during this process step

    Remove the function involvements

    Complete the functional chain/scenario with the correct new/alternative functions

    end if

    If new functions were added during this process AND those new functions should be involved in the functional chain/scenario

    Add the new functions/functional exchanges in the appropriate place

    end if

    If involved functions were split during this process step

    Replace the function involvements on the functional chain/scenario such that only leaf-level functions are involved

    end if

    If the logic of the functional chain/scenario has changed because of alterations to functions and functional exchanges

    update the logic so that it is consistent with the rest of the model

    end if

    end for

Caution!

Where this process step results in changes to the existing 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

Once per capability package prior to review ARCH.R.6

Completion criteria

The output view conforms to its modelling rules.

The whole set of logical functions is completely consistent and safe enough to try.

Each logical functional chain and scenario is completely consistent with the consolidated logical functional flow definition.

Design reviewARCH.R.6 Logical review - consolidated
Step done by (Responsible)

Lead system architect

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

None directly.