Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.151 Refine system interface to subsystem interface to actor
RCAMT-517
-
Populate Confluence page for activity definition: ARCH.151 Refine system interface to subsystem interface to actor
Finished
Goal | Refine a system interface to a subsystem interface to an actor. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Requirements met by this process step | None defined | ||||||||
Inputs | AMOD-093 Subsystems definition | ||||||||
Outputs | AMOD-111 Subsystem interface definition to external system / actor | ||||||||
Methodology | First step: analyse the subsystem interface to an external system / actor Analyse a pair of a subsystem and external system / actor provided by AMOD-085 and AMOD-093. A candidate for a subsystem interface to an external system / actor is indicated from the situation that are existing logical exchanges between logical components deployed to the subsystem and the external system / actor crossing those boundary of those systems. This process step covers the refinement of system interfaces defined in the previous process area (i.e. ARCH.920 Define the logical architecture). Decide then which kind of interface is intended and needed. This shall take into account design decisions made in ARCH.934 for the physical architecture as well as the existing content provided by AMOD-085 and AMOD-093 which can constrain the possibilities.
Note: Where it is not possible or practical to model the interface with the aforementioned categories, another one shall be identified and selected. Second step: define the subsystem interface This process step as well as the corresponding process steps ARCH.114 Define single interface layer in parallel. This is required to define the subsystem interface in the whole showing the interconnections of all interface layers as well as to focus on details of each interface layer itself.
Guidance The subsystem interfaces to an external system / actor are the actual interfaces for these situations which can be identified and exist. They include of additional elements inside and between these two interfacing systems to enable technology-dependent interaction and therefore are highly influenced by the used technology. | ||||||||
Tools and non-human resources | Team for Capella | ||||||||
Cardinality | Once per every identified pair of a subsystem and an external system / actor. | ||||||||
Completion criteria | The output views conform to their modelling rules. | ||||||||
Design review | |||||||||
Step done by (Responsible) |
| ||||||||
Provides input to/assists (Contributes) |
| ||||||||
Uses outputs (Informed) | none |