Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.098 Define selected subsystem option
Goal | Definition/Modelling of a set of subsystems and deploy logical components. |
---|---|
Requirements met by this process step | ISO 15288 6.4.4.3 c) ISO 15288 6.4.4.3 d) EN 50126-1 7.3.2.1 b) |
Inputs | |
Outputs | AMOD-093 Subsystem architecture definition AMOD-085 Subsystem architecture definition (single realised capability) |
Methodology | Main steps
Create the viewpoint AMOD-085 Subsystem architecture definition (single realised capability) for the realised capability of interest. A selection of subsystems shall be modeled there including the deployed logical components, their logical exchanges to the involved actors and the allocated functions.
Note: it is possible to copy the layout (functionality which is provided by Capella) from the logical level AMOD-125 because this viewpoint only added the subsystem. The rest of the content should be the same which is shown on AMOD-125 for a single realised capability. Create AMOD-093 Subsystem architecture definition. All subsystems shall be modelled there concretely in an overall picture including the deployed logical components and their logical exchanges to actors.
Note: Functions are not shown in AMOD-093 Subsystem architecture definition. Guidance: Physical links between two subsystems may not be modelled always. A physical link doesn't always exist between two subsystems directly but rather could go into for example a network port of the communications platform. This will be added in later steps of the process. |
Tools and non-human resources | Team for Capella |
Cardinality | Once per subsystem with selected subsystem boundaries. |
Completion criteria | All intended subsystems are defined. |
Design review | |
Step done by (Responsible) | Lead systems architect |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | None. |