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.008 Define abstract concepts relevant to the wider system of interest

GoalIdentify the most important items of data that are known at the beginning of the process to be necessary for the achievement of the project
Requirements met by this process step

None.

Inputs

Previously documented domain knowledge 

Knowledge of participants

ARCH.M.050 Method for definition of data model

Outputs

AMOD-025 Abstract concepts (limited scope)

AMOD-034 Abstract concept states

Methodology

Abstract concepts must be aligned with any international collaborations. Therefore, this task may be done jointly with other railway organisations if it makes sense to do the work once jointly and then adopt the outcome for ourselves.

Using expert knowledge or existing models, capture model elements to represent abstract concepts. Operationally, these objects exist even if they are not currently/typically transmitted by electronic communication.

Check the page Method for a conceptual data model for more guidance and rules on the concepts used.

See as an addition the 5. Modelling Rules for Data. and Best practices to maintain a consistent conceptual data model

Tools and non-human resourcesTeam for Capella
CardinalityOnce per area of expertise (limited scope) (this could be the area of a technical circle, or of an operational aspect; not necessary to capture everything exhaustively, just capture what is known at the start)
Completion criteria

Output model views conform to their modelling rules.

All known initial sources of abstract concepts have been captured to a SETT level.

Design review

ARCH.R.1 Operational capability review

ARCH.R.2 Operational review - consolidated

Step done by (Responsible)Operational concept architect
Provides input to/assists (Contributes)

Domain experts

System architect

Uses outputs (Informed)None directly