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.122 Define behaviour for interface layer functions

RCAMT-420 - Update and define ARCH.122 Define behaviour for interface layer functions Finished

Goal

Define the behaviour of an interface layer function

Requirements met by this process stepNone defined yet
Inputs

AMOD-100 Interface layer definition

ARCH.M.020 Method for definition of behaviour

ARCH.M.010 Method for definition of functionality

ARCH.M.030 Method for definition of interfaces

Outputs

AMOD-144 Behaviour definition (interface layer function)

Methodology

Introduction

The scope of this process step is to create a behavioural definition for an interface layer function. This means specifically to define how a function of an interface layer component transforms its inputs to its outputs. It consists of a precise definition how data objects of exchange items (inputs and outputs through functional exchanges) are produced and consumed via the function ports.


Preparation step

Before performing the three main steps of this process step try to describe what the function actually should do in an informal way. This can be done for example with natural language, drawings, tables or simple sketches. The goal here is to focus once more on content rather than formalising it directly. After that when there is an overall consistent picture of the function existing move on then with the first step.

Main step

Depending on the chosen behavioural model and notation create the corresponding viewpoint.


Guidance

Please consider the following pages:

Tools and non-human resources

Team for Capella

Cardinality

One off with allowed revisions.

Completion criteria

All functions of an interface layer component of an interface layer.

Design review

ARCH.R.7 Subsystem capability review

ARCH.R.8 Subsystem review - consolidated

Step done by (Responsible)

Subsystem architects of both interfacing subsystems

Provides input to/assists (Contributes)
  • subsystem architect for communication/computation
  • system architect
  • engineer
Uses outputs (Informed)None directly