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.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

GoalDefine 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:


  • Externally constrained system interface
    1. Decide on an appropriate set of interface layers for the constraint system interface. Guidance can be found in Method for definition of system interfaces chapter Context.
    2. Represent only the interfacing actor and the system in an AMOD-114 System interface definition. Guidance can be found in Method for definition of system interfaces chapter Pattern for externally constrained interfaces.
    3. Depending on the need, define interface-specific behaviours in an AMOD-115 External interface behaviour. See the chapter "Specific guidance for scenarios applicable at the system analysis" in Method for definition of scenarios for more guidance.
    4. Based on the interface layers identified, capture the necessary exchange information in their own independent instances of AMOD-112 and AMOD-113 as appropriate (this includes packet structure, header definitions etc. for each layer of an interface). For more guidance see the methodology on ARCH.M.050 Method for definition of data model.

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 reviewARCH.R.3 System capability review
Step done by (Responsible)

Lead system architect

Provides input to/assists (Contributes)
  • System architect
  • Engineer
  • Cross-cutting engineer
Uses outputs (Informed)None directly