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.035 Identify constraints on the system solution

GoalEnsure the system designed is fit for its purpose and its environment
Requirements met by this process step

ISO 15288 6.4.2.3 d 1)
EN 50126-1 7.3.2 b), 7.3.7 c)

Inputs

AMOD-010 Trade space assessment

AMOD-024 Operational activity definition and allocation

Knowledge of responsible and contributing roles

Railway domain source material from openly available sources

Contemporary CCS project material within the IM (DSTW/ETCS etc.)

Knowledge of system borders of collaborative projects (optional)

Outputs

AMOD-116 System implementation constraints

Methodology

The question to be answered is "how do the trade space considerations practically constrain our choice of system boundary and our implementation of that system?".

This task must be bounded carefully to avoid spending too much time in one go. It is not possible to capture every possible consideration just by brainstorming. Something like the "80:20" rule should be applied when determining the depth to which the constraints should be analysed.

The input information will be quite high-level and may not be focused on potential system boundaries. Where content from collaborative projects is planned to be implemented in the model under consideration, the system border of the respective project will be a constraint for this step.

This activity must convert this input information into a set of practical considerations and constraints for setting the system boundary and implementing the system physically on the infrastructure.

The considerations identified in the trade space assessment should all have some meaningful constraint on the physical system implementation.

Brainstorming could be used, with domain experts, to identify this meaning from the trade space assessment.

Material on "operational" (usage) target pictures from projects such as ETCS/DSTW might be useful as comparators.

Tools and non-human resources

General brainstorming materials

Team for Capella (to be decided, depending on format of AMOD-116)

CardinalityOne-off, with possible revisions.
Completion criteriaThe set of identified system implementation constraints is safe enough to try.
Design review
Step done by (Responsible)Lead system architect
Provides input to/assists (Contributes)

System architect

Railway operations expert

Uses outputs (Informed)None directly