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.039 Define set of potential system and actor functions

RCAMT-464 - Update ARCH.911 and ARCH.912 after refinment proposal was approved Finished

Goal

Define initial set of potential system functions and actor functions, in order to refine understanding of the system border. 

Note: this step does not need to result in a complete set of functions for the entire system.

Requirements met by this process stepCSM-SMS Guidance 3.1.1.1 c), 3.1.5
Inputs

AMOD-101 Consolidated operational activities & interactions

AMOD-024 Operational activity definition and allocation

AMOD-012 System lifecycle model

AMOD-122 Record of system actors

System-level scenarios from collaborative models (optional)

OutputsAMOD-121 Record of system and actor functions
Methodology

If operational concept exists in the same modelling tool as the system model:

Each operational activity shall be analysed to determine whether it shall be transferred to system level as a system function, and actor function, or both a system and an actor function. In order to be selected for transfer, the operational activity must fulfill the following conditions:

Operational activity to system function transition:

  • It is expected that the activity will be entirely done by the system AND
  • Either the activity is not triggered by a system actor OR
  • The activity does not yield an observable valuable result to one or more system actors

Operational activity to actor function transition:

  • it is expected that the activity will be done entirely by one and only one actor

Operational activity to system function and actor function transition:

  • It is expected that part of the operational activity shall be done by the system, and another part by an actor

If both of the above-listed conditions are fulfilled, the system function or actor function identified from analysing the operational activity shall be included in AMOD-121 Record of system and actor functions, along with a rationale for its definition.

Note: the rationale should explain why the system function or actor function is traced to one or more operational activities.

If operational concept exists outside of system model:

In the absence of an operational layer in the model under development, system/actor functions cannot be derived from operational activities and must be defined independently of the operational layer. This can be done on the basis of brainstorming using available operational concepts, even if an operational layer is not explicitly present in the model. It may be the case that multiple operational concepts are to be considered (e.g. from different IMs), in which case the definition of potential system/actor functions must be performed under consideration of all of those concepts.

A system/actor function that is defined independent of the operational layer must fulfill the same criteria defined within this process step for operational activities that are to be transitioned to the system layer.

The decision and rationale for the creation of each of these system/actor functions shall be documented in AMOD-121 Record of system and actor functions.

Tools and non-human resourcesConfluence or Excel for creation of AMOD-121 Record of system and actor functions
CardinalityOnce per operational activity
Completion criteriaThe output view contains a valid decision and rationale for each operational activity in the model.
Design review
Step done by (Responsible)Lead system architect
Provides input to/assists (Contributes)
  • Operational concept architect
  • System architect
  • Engineer
  • Cross-cutting engineer
Uses outputs (Informed)None directly