Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.158 Model external system interface
SM-3429
-
Create Confluence page for activity definition ARCH.158
Finished
RCAMT-514
-
Update viewpoint AMOD-114 and ARCH.158 and related process steps plus modelling rules
Finished
RCAMT-658
-
04_2022_01 Populate Confluence page of the method for definition of interfaces
Finished
Goal | Define the characterisations of external interfaces (e.g. identify the constraints on system design arising from external interfaces) |
---|---|
Requirements met by this process step | EN 50126-1 7.3.2.1 b) and c) ISO 15288 6.4.4.3 c 1) |
Inputs | AMOD-056 System functions and exchanges (single system capability) AMOD-058 Initial system exchange scenario ARCH.M.030 Method for definition of interfaces ARCH.M.050 Method for definition of data model Method for definition of scenarios Interface standards/specifications from elsewhere |
Outputs | |
Methodology | At the system level, the system communicates with external actors via interfaces. It is possible that these external interfaces impose constraints on the way the system should be designed. Thus, we can distinguish two cases:
Note: the existing scenarios used as input to this activity provide the functions and functional exchanges that interact across the system boundary. |
Tools and non-human resources | Team for Capella |
Cardinality | Once per external interface |
Completion criteria | The output views conform to their modelling rules The interface model content is a correct match for the known constraints applying to that interface |
Design review | ARCH.R.3 System capability review |
Step done by (Responsible) | Lead system architect |
Provides input to/assists (Contributes) |
|
Uses outputs (Informed) | None directly |