Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.043 Define set of potential system actors
SM-2779
-
Populate Confluence page for activity definition: ARCH.043 Select operational actors for transition/tracing to system level
Finished
Goal | Identify potential system actors based on either operational entities or other operational concepts that actually interact with the system |
---|---|
Requirements met by this process step | ISO 15288 6.4.2.3 a 1) |
Inputs | AMOD-024 Operational activity definition and allocation System-level actors from collaborative projects (optional) |
Outputs | |
Methodology | If operational concept exists in the same modelling tool as the system model: Each operational entity or operational actor shall be analysed to determine whether it shall be transferred to system level as an actor. In order to be selected for transfer, the operational entity or actor must fulfill the following conditions:
If both of the above-listed conditions are fulfilled, the system actor identified from analysing the operational entity or operational actor shall be included in AMOD-122 Record of system actors, along with a rationale for its definition. Note: the rationale should explain why the system actor is traced to one or more operational entities and/or operational actors, or why an operational actor is to be transitioned to the respective system actor. Note: it is not always possible to trace an operational entity directly to a system actor. If an entity is generic, the specific actor it represents on system level might be more specific and it scope would need to be defined before inclusion in AMOD-122 Record of system actors. If operational concept exists outside of system model: In the absence of an operational layer in the model under development, system actors cannot be derived from operational actors 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 actors must be performed under consideration of all of those concepts. A system actor that is defined independent of the operational layer must fulfill the same criteria defined within this process step for operational actors that are to be transitioned to the system layer. The rationale for the creation of each of these system actors shall be documented in AMOD-122 Record of system actors, similar to the case above. Once the system actor is defined, it must be assured that traceability is established to the operational layer, should it become relevant. |
Tools and non-human resources | Confluence or Excel for creation of AMOD-122 Record of system actors |
Cardinality | Once per operational entity or operational actor |
Completion criteria | For each operational entity that interacts with the system an actor at system level has been created and this actor is traced to the original operational entity. |
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 |