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.036 Identify all alternative system boundaries

GoalEnable decisions to be made about whether functionality is to be included inside the system, or left to external actors.
Requirements met by this process stepISO 15288 6.4.1.3 c 2)
Inputs

AMOD-024 Operational activity definition and allocation

AMOD-122 Record of system actors

AMOD-121 Record of system and actor functions

AMOD-120 Record of system capabilities and missions

Contemporary CCS project material relevant to responsible enterprise (specifically about system capabilities and activities, system target picture etc.)

OutputsAMOD-041 System boundary options
Methodology

Based on the viewpoints listed in the Inputs field, perform the following:

Where there is doubt on the allocation of the function between the system or actors, sketch the options, showing each alternative with the candidate functionality of the system and the candidate functionality of actors. Produce one sketch per doubted function, or per themed group. Do not attempt to sketch all permutations of all alternative function allocations together. Each specific decision should be handled individually.

Tools and non-human resourcesAny drawing tool
CardinalityOne-off, with revisions permitted
Completion criteria

The produced views comply with their modelling rules

For each individual allocation question, the set of alternatives produced is complete and reasonable

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