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 - Problem definition & architectural design process area




Contact: Maxime Mahé 

Purpose


The main purpose of the ARCH process area is to provide a shared and agreed reference architecture that meets stakeholder needs. This is achieve by defining the problem and designing architectural solutions. The reference architecture can be later instantiated and specialized to produce potential architecture solutions to fulfill individual business purposes.

Scope


The scope of ARCH process area covers the left part of the V-cycle and it is aimed to be a specification process. The ARCH process area covers systems engineering activities that are performed in a holistic way. It includes activities such as:

  • stakeholder needs analysis
  • requirement analysis
  • architecture design
  • trade-off studies
  • RAMS & Security risk analysis

Note: the activity structure of ARCH does not exactly match the bullets above

Outcome


As a result of successful implementation of this process:

  • The reference model is produced
  • All information needed to create regulated documents is available

High-level summary of this process area

Input / Output


Required key input information / deliverables

  • Enterprise goals
  • Major stakeholders identification
  • Business requirements
  • Management plans


Expected key output information / deliverables

  • System architecture description (as a collection of model views)
  • Subsystems description
  • Stakeholders, system and subsystems requirements
  • Requirements traceability
  • Architecture traceability
  • Life cycle concepts
  • Architecture rationale
  • Interfaces definition
  • Measure of performance
  • Risk assessment record
  • Problem statement

Key Stakeholders


User

  • SYD Circle Lead
  • Operational Concept Architect
  • Lead Systems Architect
  • TechCircles Engineer
  • DBS Design Authority
  • RCA AR Lead
  • RAMS Manager
  • Security Manager

Manager

  • SuperTechCircles Lead
  • Project System Architect
  • Project Lead Systems Architect
  • DBS Circle Lead
  • DB Netz Managers
  • RCA M&T leader
  • EULYNX Lead

Customer

  • Inner SSI Circle Leads
  • Process Area Owners
  • SSI SuperCircle Lead
  • System Pillar Core Group Lead

Interested party

  • Linx4Rail Lead
  • OCORA Lead
  • System Pillar Architecture & Migration domain Lead
  • Innovation Pillar Coordination & Communication Railway
  • Innovation Pillar Coordination & Communication Industry
  • Process authorities

Above is a highlight of stakeholders for ARCH. A detailed stakeholders list can be found here: 03 SEM stakeholders

Version History / Change Log

Version 0.1

initial release

PUBLISHED

Version 0.2updated but still initial version

PUBLISHED  

Version 0.3

updated but still initial version

RCAMT-407 - RCA methodology-related documentation - continuous improvement release 0.3 Finished

PUBLISHED

Version 0.4

RCAMT-689 - RCA methodology-related documentation - continuous improvement release 0.4 In Implementation

PUBLISHED

ARCH specific roles


    • System Engineer
    • System Architect
    • Subsystem Architect
    • Operational Concept Architect
    • Lead System Architect
    • RAMS Engineer
    • Security Engineer
    • Design Authority

Detailed process flow definition

Date uploaded

File + Image

Checked-in?

Notes

Modifier

Confluence Tags updated?

 

ARCH process area diagram.graphml

ARCH process area diagram.svg

Published version 0.4

Checked in (Lorenzo Grenier  )

Rename of ARCH.158Lorenzo Grenier Updated

 

Check old version of file from

in page history

Superseded (Dennis Kunz )

updated name and status of AMOD-111 and name of AMOD-089Dennis Kunz No updates

 

Check old version of file from

in page history

Superseded (Lorenzo Grenier)

Merged of ARCH.158 and ARCH.057 according to Method for definition of system interfaces.

Modification of the links for AMOD-112&113

RCAMT-658 - 04_2022_01 Populate Confluence page of the method for definition of interfaces Finished

Lorenzo Grenier Updated

 

Check old version of file from in  page history

Published version 0.3

Superseded(Jorge Block )

Merged ARCH.161 and ARCH.159 + ARCH.055 and ARCH.056 because of tension in the tension board.Jorge Block Updated

Released process step descriptions

Last released documents can be accessed in column "status" in the following table.

Click here to expand...

View: Pending | Approved | Rejected
Approvals: Review this page
Title Last Updated By Updated State Status
ARCH.176 Create subsystem exchange scenarios Lorenzo Grenier 28.09.2022 17:21   Draft     (v.6) Approved by Stefan St Lemke on 28.09.2022 15:11
ARCH - Problem definition & architectural design process area Jorge Block 28.09.2022 14:54   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:47
ARCH.087 Model data flowing between logical functions Jorge Block 17.08.2022 14:24   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:12
ARCH.054 Model data flowing between system functions Jorge Block 17.08.2022 14:19   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 12:27
ARCH.153 Model data flowing between operational activities Jorge Block 17.08.2022 14:17   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 12:27
Process step descriptions Jorge Block 29.06.2022 09:59   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 12:26
ARCH.130 Define interface layer exchange scenarios Lorenzo Grenier 28.06.2022 16:52   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 12:26
ARCH.086 Create or update exchange scenarios at logical level Lorenzo Grenier 28.06.2022 16:41   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 12:26
ARCH.904 Incorporate risk control measures in the operational needs Lorenzo Grenier 28.06.2022 16:35   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 12:25
ARCH.078 Create bare business operational scenario Lorenzo Grenier 28.06.2022 16:33   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 12:25
ARCH.916 Incorporate risk control measures in the system needs Lorenzo Grenier 28.06.2022 16:24   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:12
ARCH.158 Model external system interface Lorenzo Grenier 28.06.2022 16:23   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:13
ARCH.052 Create initial system exchange scenarios Lorenzo Grenier 28.06.2022 16:17   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 11:51
ARCH.116 Define subsystem specific requirements Dennis Kunz 15.06.2022 12:04   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:13
ARCH.157 Consolidate system data Lorenzo Grenier 14.06.2022 10:30   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 11:53
ARCH.183 Consolidate operational data Lorenzo Grenier 14.06.2022 10:29   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:14
ARCH.008 Define abstract concepts relevant to the wider system of interest Lorenzo Grenier 14.06.2022 10:27   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:14
ARCH.096 Allocate logical functions to logical components (including alternative allocations) Lorenzo Grenier 13.06.2022 14:50   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:16
ARCH.177 Complete the definition of the operational capability of interest Jorge Block 19.05.2022 16:39   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:17
ARCH.002 Create initial set of operational capabilities Jorge Block 19.05.2022 16:36   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:17
ARCH.049 Define set of potential system capabilities/missions Jorge Block 19.05.2022 16:36   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:22
ARCH.036 Identify all alternative system boundaries Jorge Block 19.05.2022 16:30   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:22
ARCH.119 Define consolidated set of system capabilities/missions Jorge Block 19.05.2022 16:29   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:23
ARCH.097 Evaluate subsystem boundary options against the architectural tradeoff criteria Jorge Block 18.05.2022 15:39   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:26
ARCH.042 Select system boundary (or set of variants) Jorge Block 16.05.2022 18:47   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:26
ARCH.192 Refine capability realisations for the subsystem architecture Jorge Block 11.05.2022 09:54   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:27
ARCH.191 Refine capability realisations for the logical architecture Jorge Block 11.05.2022 09:53   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:28
ARCH.055 Model system and actor states Jorge Block 08.04.2022 09:57   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:10
ARCH.190 Consolidate logical data Jorge Block 07.04.2022 15:15   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:10
ARCH.159 Model operational states Jorge Block 07.04.2022 13:40   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:11
ARCH.088 Define system functions and functional exchanges Jorge Block 06.04.2022 13:44   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:11
ARCH.098 Define selected subsystem option Jorge Block 06.04.2022 12:22   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:11
ARCH.111 Execute automatic transition of logical elements to physical level Jorge Block 06.04.2022 12:21   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:11
ARCH.118 Identify implementation constraints on the subsystem solution Jorge Block 06.04.2022 12:21   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:12
ARCH.090 Identify alternative subsystem options Jorge Block 06.04.2022 12:21   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:13
ARCH.154 Consolidate logical functional flow Jorge Block 06.04.2022 12:19   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:14
ARCH.181 Reconcile candidate logical components Jorge Block 06.04.2022 12:18   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:14
ARCH.085 Create or update functional chains at logical level Jorge Block 06.04.2022 12:17   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:15
ARCH.182 Split the system functions Jorge Block 06.04.2022 12:17   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:15
ARCH.084 Execute automatic transition of system elements to logical level Jorge Block 06.04.2022 12:16   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:15
ARCH.082 Trade off system requirements and constraints Jorge Block 06.04.2022 12:16   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:15
ARCH.081 Update constraints on system solution Jorge Block 06.04.2022 12:15   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:16
ARCH.152 Consolidate system functionality Jorge Block 06.04.2022 12:14   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:16
ARCH.058 Define measures of performance Jorge Block 06.04.2022 12:13   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:16
ARCH.053 Create initial system functional chains Jorge Block 06.04.2022 12:11   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:18
ARCH.179 Complete the definition of the system capability of interest Jorge Block 06.04.2022 12:10   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:18
ARCH.051 Align the system context with collaboration projects Jorge Block 06.04.2022 12:09   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:18
ARCH.044 Define requirements from non-actor stakeholders Jorge Block 06.04.2022 12:09   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:18
ARCH.045 Define complete set of system-level actors Jorge Block 06.04.2022 12:08   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:19
ARCH.048 Identify system implementation constraints Jorge Block 06.04.2022 12:08   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:19
ARCH.039 Define set of potential system and actor functions Jorge Block 06.04.2022 12:07   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:19
ARCH.043 Define set of potential system actors Jorge Block 06.04.2022 12:06   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:20
ARCH.041 Transfer or trace upper level model elements to system level Jorge Block 06.04.2022 12:06   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:20
ARCH.035 Identify constraints on the system solution Jorge Block 06.04.2022 12:02   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:20
ARCH.180 Define logical component candidates Jorge Block 05.04.2022 16:49   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:20
ARCH.936 Assess risks associated with subsystem architecture Jorge Block 05.04.2022 16:05   Published     (Current) Approved by Martin Lippmann on 08.04.2022 13:00
ARCH.106 Identify new functions needed for mitigating hazards introduced by architecture choice Jorge Block 05.04.2022 16:03   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:20
ARCH.105 Identify new non-functional requirements needed to mitigate hazards introduced by architecture choice Jorge Block 05.04.2022 16:03   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:20
ARCH.101 Carry out failure modes, effects and criticality analysis (FMECA) Jorge Block 05.04.2022 16:02   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:21
ARCH.103 Identify new functions needed for robustness to failures Jorge Block 05.04.2022 16:02   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:22
ARCH.935 Finalise the subsystem architecture Jorge Block 05.04.2022 16:01   Published     (Current) Approved by Martin Lippmann on 08.04.2022 13:00
ARCH.029 Allocate risk control responsibilities (op. activity to op. entity/actor) Jorge Block 01.04.2022 14:34   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:22
ARCH.022 Define operational security measures Jorge Block 01.04.2022 14:31   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:22
ARCH.015 Define business risk control measures Jorge Block 01.04.2022 14:30   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:22
ARCH.028 Define operational safety measures Jorge Block 01.04.2022 13:36   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:22
ARCH.127 Define location kinds Jorge Block 01.04.2022 09:47   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:23
ARCH.018 Identify internal & external issues affecting successful security Jorge Block 31.03.2022 18:07   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:23
ARCH.156 Define single inter-subsystem interface Dennis Kunz 22.03.2022 11:06   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:23
ARCH.121 Consolidate operational activities and interactions Jorge Block 22.03.2022 10:56   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:24
ARCH.080 Model operational activities and interactions Jorge Block 22.03.2022 10:52   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:24
ARCH.079 Create bare business operational process Jorge Block 22.03.2022 10:50   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:24
ARCH.009 Define measures of effectiveness Jorge Block 22.03.2022 10:47   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:24
ARCH.007 Create set of initial operational activities Jorge Block 22.03.2022 10:31   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:25
ARCH.006 Create initial set of operational states for operational entities/actors Jorge Block 22.03.2022 10:30   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:25
ARCH.001 Define boundary of wider system of interest (operating entity of system of interest) Jorge Block 22.03.2022 10:28   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:25
ARCH.140 Consolidate the allocation of operational activities Jorge Block 15.03.2022 18:19   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:25
ARCH.135 Carry out HAZID on tenderable elements Jorge Block 04.03.2022 09:15   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:25
ARCH.104 Identify new non-functional requirements needed for robustness to failures Jorge Block 04.03.2022 09:14   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:26
ARCH.128 Define functions of single interface layer Jorge Block 03.03.2022 11:53   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:26
ARCH.129 Model data flowing between interface layer functions Dennis Kunz 23.02.2022 19:19   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:26
ARCH.117 Align the subsystems with collaborative project Jorge Block 23.02.2022 17:58   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:27
AMOD-093 Subsystem architecture definition Jorge Block 23.02.2022 17:45   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:27
ARCH.083 Agree the system requirements with stakeholders Jorge Block 23.02.2022 13:48   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:27
ARCH.937 Allocation/Derivation of NFRs Jorge Block 22.02.2022 09:24   Published     (Current) Approved by Martin Lippmann on 08.04.2022 13:02
ARCH.125 Define structure of communication assets Jorge Block 21.02.2022 17:42   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:29
ARCH.144 Define enterprise goals Maxime Mahé 21.02.2022 10:10   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:29
ARCH.026 Define the state model of accidents, hazardous and safe state Elisabeth Helwig 16.02.2022 09:50   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:29
ARCH.108 Define acceptance criteria for non-functional requirements Jorge Block 03.02.2022 15:55   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:29
ARCH.107 Apportion non-functional requirements to logical functions Jorge Block 03.02.2022 15:55   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:29
ARCH.151 Refine system interface to subsystem interface to actor Dennis Kunz 20.01.2022 16:56   Published     (Current) Approved by Martin Lippmann on 08.04.2022 13:00
ARCH.114 Define single interface layer Dennis Kunz 20.01.2022 13:36   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:29
ARCH.020 Identify & classify operational deviations Elisabeth Helwig 25.11.2021 17:12   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:30
ARCH.186 Consolidate single subsystem interface Dennis Kunz 22.11.2021 11:42   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:40
ARCH.004 Analyse trade space factors Jorge Block 16.11.2021 14:08   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:40
ARCH.137 Allocate interface NFRs to interface layers/interface functions Jorge Block 12.11.2021 15:48   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:40
ARCH.133 Derive & allocate NFRs to computation assets Jorge Block 12.11.2021 15:46   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:40
ARCH.132 Derive & allocate NFRs to communication assets Jorge Block 12.11.2021 15:45   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:40
ARCH.131 Derive & allocate NFRs to location kinds Jorge Block 12.11.2021 15:45   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:40
ARCH.109 Consolidate traceability between model elements at system level and model elements at operational level Jorge Block 11.11.2021 11:43   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:41
ARCH.005 Define set of system of interest lifecycle variants Markus Reimann 08.11.2021 15:16   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:41
ARCH.040 yyTransfer OA to system level function, allocate entirely to actor Jorge Block 11.10.2021 14:25   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:41
AMOD-146 System needs and constraints tradeoff decision record Lorenzo Grenier 07.10.2021 11:14   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:41
ARCH.155 Allocate hazard mitigation NFRs to subsystems Julien Rey [X] 29.09.2021 14:39   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:41
ARCH.027 Evaluate operational safety risks Hans-Ulrich Plate 22.09.2021 15:38   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:42
ARCH.100 Obtain stakeholder acceptance of preferred architecture Jorge Block 26.08.2021 13:48   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:42
ARCH.110 Consolidate traceability between model elements at logical level and model elements at system level Syed-Murtaza Hasan [X] 23.07.2021 11:30   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:42
ARCH.023 Identify relevant safety legislation and regulation Jorge Block 16.07.2021 17:49   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:42
ARCH.013 Identify risks to business effectiveness (business loss-risk mapping) Jorge Block 09.07.2021 18:43   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:42
ARCH.170 Identify security losses and threats Jorge Block 09.07.2021 18:24   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:43
ARCH.126 Define structure of computation assets Maxime Mahé 07.07.2021 17:55   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:43
ARCH.012 Determine measure of effectiveness target values Jorge Block 07.07.2021 09:51   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:43
AMOD-004 Fault tree (per operational deviation) Markus Reimann 17.06.2021 13:17   Published     (Current) Approved by Martin Lippmann on 02.07.2021 07:56
ARCH.066 Identify system level deviations Joseph Silmon 19.05.2021 09:43   Published     (Current) Approved by Martin Lippmann on 31.05.2021 15:58
ARCH.068 Assess deviation probability (external constraints) Joseph Silmon 18.05.2021 16:08   Published     (Current) Approved by Martin Lippmann on 31.05.2021 15:59
ARCH.067 Populate the fault tree Joseph Silmon 18.05.2021 15:29   Published     (Current) Approved by Martin Lippmann on 31.05.2021 15:58
ARCH.069 Add system level risk measures Joseph Silmon 18.05.2021 15:06   Published     (Current) Approved by Martin Lippmann on 31.05.2021 15:59
ARCH.070 Calculate system deviation probability Joseph Silmon 18.05.2021 15:00   Published     (Current) Approved by Martin Lippmann on 31.05.2021 16:01
ARCH.019 Determine need for information availability, confidentiality, integrity Markus Reimann 14.05.2021 11:50   Published     (Current) Approved by Martin Lippmann on 31.05.2021 13:49
ARCH.914 Produce the unregulated system documents Simon Heller 06.05.2021 11:29   Published     (Current) Approved by Martin Lippmann on 31.05.2021 15:57
Model view specifications Jorge Block 03.03.2021 18:07   Published     (Current) Approved by Markus Reimann (on 30.03.2021 13:57), Oliver Lemke (on 30.03.2021 13:58), Wolfgang Benten (on 30.03.2021 14:14 - Initial draft version of ARCH process moved to RCA space to continue process development, testing, and achieving of early feedback) and Joseph Silmon (on 30.03.2021 14:59)
ARCH.930 Define the physical architecture Jorge Block 03.03.2021 18:04   Published     (Current) Approved by Markus Reimann (on 30.03.2021 13:58), Oliver Lemke (on 30.03.2021 13:58), Wolfgang Benten (on 30.03.2021 14:14 - Initial draft version of ARCH process moved to RCA space to continue process development, testing, and achieving of early feedback) and Joseph Silmon (on 30.03.2021 14:59)
ARCH.920 Define the logical architecture Jorge Block 03.03.2021 18:02   Published     (Current) Approved by Markus Reimann (on 30.03.2021 13:58), Oliver Lemke (on 30.03.2021 13:58), Wolfgang Benten (on 30.03.2021 14:14 - Initial draft version of ARCH process moved to RCA space to continue process development, testing, and achieving of early feedback) and Joseph Silmon (on 30.03.2021 15:00)
ARCH.900 Determine the operational needs Jorge Block 03.03.2021 18:01   Published     (Current) Approved by Markus Reimann (on 30.03.2021 13:58), Oliver Lemke (on 30.03.2021 13:58), Wolfgang Benten (on 30.03.2021 14:15 - Initial draft version of ARCH process moved to RCA space to continue process development, testing, and achieving of early feedback) and Joseph Silmon (on 30.03.2021 15:00)
ARCH.910 Determine the system requirements Jorge Block 03.03.2021 18:00   Published     (Current) Approved by Markus Reimann (on 30.03.2021 13:59), Oliver Lemke (on 30.03.2021 13:59), Wolfgang Benten (on 30.03.2021 14:15 - Initial draft version of ARCH process moved to RCA space to continue process development, testing, and achieving of early feedback) and Joseph Silmon (on 30.03.2021 15:00)
ARCH.021 Evaluate security risks Oscar Rubinstein [X] 28.09.2020 18:04   Published     (Current) Approved by Martin Lippmann on 31.05.2021 14:01
ARCH.014 Evaluate risks to business effectiveness Oscar Rubinstein [X] 28.09.2020 18:01   Published     (Current) Approved by Martin Lippmann on 31.05.2021 13:56

Released model view specifications

Last released documents can be accessed in column "status" in the following table.

Click here to expand...

View: Pending | Approved | Rejected
Approvals: Review this page
Title Last Updated By Updated State Status
AMOD-148 Subsystem capability realisation Lorenzo Grenier 21.09.2022 15:29   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:29
AMOD-094 Interface layer exchange items Jorge Block 26.08.2022 10:31   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:30
AMOD-091 Logical data objects [L.CDB] Jorge Block 26.08.2022 10:23   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:31
AMOD-025 Abstract concepts Jorge Block 26.08.2022 10:20   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:32
AMOD-112 System data objects [S.CDB] Jorge Block 26.08.2022 10:19   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:32
AMOD-105 Operational data objects [O.CDB] Jorge Block 26.08.2022 10:01   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:33
AMOD-113 System exchange items [S.CDB] Jorge Block 19.08.2022 12:16   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:33
AMOD-092 Logical exchange items [L.CDB] Jorge Block 19.08.2022 12:15   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:34
AMOD-110 Operational exchange items [O.CDB] Jorge Block 19.08.2022 11:53   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:35
AMOD-056 System functions and exchanges (single system capability) Lorenzo Grenier 28.06.2022 16:18   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:36
AMOD-089 Subsystem lifecycle definition Dennis Kunz 21.06.2022 08:39   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:37
AMOD-114 System interface definition Lorenzo Grenier 06.05.2022 12:18   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:37
AMOD-115 External interface behaviour Dennis Kunz 29.04.2022 17:00   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:38
AMOD-060 System/actor states Jorge Block 07.04.2022 14:49   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:44
AMOD-055 System functions to state allocation map [Matrix] Jorge Block 07.04.2022 14:15   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:45
AMOD-028 Operational activities and interaction definitions (single operational capability) Jorge Block 07.04.2022 13:30   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:45
AMOD-023 Operational entity/actor states Jorge Block 07.04.2022 13:29   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:45
AMOD-024 Operational activity definition and allocation Jorge Block 07.04.2022 11:36   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:45
AMOD-045 System capabilities Jorge Block 05.04.2022 16:00   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:45
AMOD-125 Logical architecture definition Jorge Block 05.04.2022 15:36   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:45
AMOD-095 Location kind definitions Jorge Block 01.04.2022 11:18   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:46
AMOD-106 Enterprise goals Jorge Block 31.03.2022 18:05   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:46
AMOD-133 Consolidated system function allocation Jorge Block 29.03.2022 17:33   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:46
AMOD-137 Single operational capability context Jorge Block 28.03.2022 17:52   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:46
AMOD-035 Operational business process with risk control measures Jorge Block 28.03.2022 17:51   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:46
AMOD-033 Operational business scenario with risk control measures Jorge Block 28.03.2022 17:50   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:47
AMOD-059 Initial system functional chain description Jorge Block 28.03.2022 17:42   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:48
AMOD-058 Initial system exchange scenario Jorge Block 28.03.2022 17:41   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:48
AMOD-118 System functional chain descriptions with risk control measures [SFCD] Jorge Block 23.03.2022 17:12   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:48
AMOD-117 System exchange scenarios with risk control measures [S.ES] Jorge Block 23.03.2022 17:11   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:49
AMOD-101 Consolidated operational activities & interactions Jorge Block 15.03.2022 18:17   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:49
AMOD-021 Operational capabilities definition Jorge Block 15.03.2022 17:58   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:49
AMOD-022 Enterprise & environment definition Jorge Block 15.03.2022 11:00   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:49
AMOD-097 Computation asset structure Jorge Block 01.03.2022 14:44   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:49
AMOD-099 Interface layer exchange scenario Dennis Kunz 23.02.2022 19:21   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:49
AMOD-093 Subsystem architecture definition Jorge Block 23.02.2022 17:45   Published     (Current) Approved by Martin Lippmann on 08.04.2022 11:27
AMOD-085 Subsystem architecture definition (single realised capability) Jorge Block 23.02.2022 17:41   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:49
AMOD-080 Subsystem option sketch Jorge Block 23.02.2022 13:02   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:50
AMOD-010 Trade space assessment Jorge Block 21.02.2022 17:27   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:50
AMOD-124 Subsystem architecture tradeoff record Jorge Block 15.02.2022 10:34   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:50
AMOD-018 Organisation future process framework Jorge Block 04.02.2022 17:52   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:50
AMOD-121 Record of system and actor functions Jorge Block 04.02.2022 10:28   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:51
AMOD-120 Record of system capabilities and missions Jorge Block 04.02.2022 10:26   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:52
AMOD-116 System implementation constraints Jorge Block 25.01.2022 09:36   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:52
AMOD-143 Inter-subsystem interface definition Dennis Kunz 21.01.2022 09:09   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:52
AMOD-100 Interface layer definition Dennis Kunz 21.01.2022 09:05   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:53
AMOD-075 Subsystem implementation constraints Jorge Block 20.01.2022 16:04   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:53
AMOD-046 Selected system boundary tradeoff record Jorge Block 07.01.2022 12:34   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:53
AMOD-119 System context definition Jorge Block 11.11.2021 15:59   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:53
AMOD-079 Agreed system requirements baseline (functional + non functional) Jorge Block 10.11.2021 18:41   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:54
AMOD-138 Single system capability context Jorge Block 10.11.2021 18:16   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:54
AMOD-122 Record of system actors Jorge Block 10.11.2021 18:15   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:54
AMOD-103 Consolidated system functions Jorge Block 10.11.2021 17:03   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:54
AMOD-104 System level - operational level traceability report Jorge Block 27.10.2021 14:12   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:54
AMOD-144 Behaviour definition (interface layer function) Dennis Kunz 21.10.2021 10:42   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:54
AMOD-050 Stakeholder non-functional requirements Jorge Block 13.10.2021 12:05   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:55
AMOD-049 Non-functional requirements implementation Jorge Block 13.10.2021 12:05   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:55
AMOD-098 Consolidated tenderable element structure Lorenzo Grenier 08.10.2021 10:37   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:55
AMOD-146 System needs and constraints tradeoff decision record Lorenzo Grenier 07.10.2021 11:14   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:41
AMOD-031 Unified risk model (to be discussed) José Minguez-Garrigues 02.10.2021 17:09   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:55
AMOD-142 Single subsystem definition Jorge Block 30.09.2021 18:14   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:55
AMOD-041 System boundary options Jorge Block 30.09.2021 14:46   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:55
AMOD-088 Consolidated logical functional flow definition Jorge Block 10.09.2021 16:27   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:56
AMOD-096 Communication asset structure Jorge Block 02.09.2021 15:33   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:56
AMOD-126 Logical level - system level traceability report Syed-Murtaza Hasan [X] 17.08.2021 07:50   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:56
AMOD-081 Logical functional flow definition (single system capability realisation) Luis L Valdés [X] 06.08.2021 15:48   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:56
AMOD-082 Logical functional chain definition Luis L Valdés [X] 06.08.2021 15:48   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:56
AMOD-084 Logical exchange scenario definition Luis L Valdés [X] 06.08.2021 15:48   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:56
AMOD-027 Operational bare business scenario Luis L Valdés [X] 06.08.2021 15:42   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:56
AMOD-029 Operational bare business process Luis L Valdés [X] 06.08.2021 15:42   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:56
AMOD-136 Single operational capability deviation analysis report Jorge Block 02.08.2021 13:14   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:57
AMOD-057 Measures of performance Jorge Block 20.07.2021 09:34   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:57
AMOD-071 System failure modes and effects analysis Jorge Block 08.07.2021 17:03   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:57
AMOD-004 Fault tree (per operational deviation) Markus Reimann 17.06.2021 13:17   Published     (Current) Approved by Martin Lippmann on 02.07.2021 07:56
AMOD-026 Service reliability/ availability targets Elsa Lamblin [X] 11.06.2021 17:05   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:04
AMOD-015 Example CONOPS from other railway Elsa Lamblin [X] 11.06.2021 17:04   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:04
AMOD-012 System lifecycle model Elsa Lamblin [X] 11.06.2021 15:59   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:15
AMOD-145 Security compliance strategy Elsa Lamblin [X] 11.06.2021 14:53   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:15
AMOD-135 Consolidated operational deviation analysis report Elsa Lamblin [X] 11.06.2021 14:52   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:15
AMOD-131 Security loss and threat state model Elsa Lamblin [X] 11.06.2021 14:52   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:16
AMOD-130 Business loss and risk state model Elsa Lamblin [X] 11.06.2021 14:51   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:16
AMOD-129 Relevant safety legislation/regulations Elsa Lamblin [X] 11.06.2021 14:51   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:16
AMOD-128 Safety compliance strategy Elsa Lamblin [X] 11.06.2021 14:50   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:16
AMOD-107 Safety hazard, security issue, business risk log Elsa Lamblin [X] 11.06.2021 12:01   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:17
AMOD-032 Allocated risk control measures Elsa Lamblin [X] 11.06.2021 11:59   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:17
AMOD-030 Accident and hazard state model Elsa Lamblin [X] 11.06.2021 11:57   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:18
AMOD-147 Logical capability realisation Joseph Silmon 09.06.2021 12:00   Published     (Current) Approved by Martin Lippmann on 02.07.2021 08:20
Physical level Jorge Block 03.03.2021 18:11   Published     (Current) Approved by Martin Lippmann on 02.06.2021 08:10
Logical level Jorge Block 03.03.2021 18:11   Published     (Current) Approved by Martin Lippmann on 02.06.2021 08:03
System level Jorge Block 03.03.2021 18:09   Published     (Current) Approved by Martin Lippmann on 02.06.2021 08:00
Operational level Jorge Block 03.03.2021 18:09   Published     (Current) Approved by Martin Lippmann on 01.06.2021 14:26
Enterprise level Jorge Block 03.03.2021 18:08   Published     (Current) Approved by Martin Lippmann on 01.06.2021 14:12
Model view specifications Jorge Block 03.03.2021 18:07   Published     (Current) Approved by Markus Reimann (on 30.03.2021 13:57), Oliver Lemke (on 30.03.2021 13:58), Wolfgang Benten (on 30.03.2021 14:14 - Initial draft version of ARCH process moved to RCA space to continue process development, testing, and achieving of early feedback) and Joseph Silmon (on 30.03.2021 14:59)
Views produced outside ARCH Joseph Silmon 27.05.2020 10:48   Published     (Current) Approved by Martin Lippmann on 02.06.2021 08:12

Released design reviews

Last released documents can be accessed in column "status" in the following table.

Click here to expand...

View: Pending | Approved | Rejected
Approvals: Review this page
Title Last Updated By Updated State Status
ARCH.R.1 Operational capability review Joseph Silmon 13.09.2022 16:14   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:39
ARCH.R.2 Operational review - consolidated Joseph Silmon 13.09.2022 14:10   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:39
Design review structure Joseph Silmon 07.06.2022 11:10   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:40
ARCH.R.3 System capability review Jorge Block 12.05.2022 14:02   Published     (Current) Approved by Stefan St Lemke on 28.09.2022 15:41
ARCH.R.6 Logical review - consolidated Jorge Block 08.04.2022 08:52   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:57
ARCH.R.5 Logical capability review Jorge Block 08.04.2022 08:51   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:58
ARCH.R.7 Subsystem capability review Jorge Block 05.04.2022 16:07   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:58
ARCH.R.8 Subsystem review - consolidated Jorge Block 05.04.2022 16:07   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:58
ARCH.R.4 System review - consolidated Jorge Block 29.03.2022 17:47   Published     (Current) Approved by Martin Lippmann on 08.04.2022 12:58
Definition of scope of compliance Joseph Silmon 25.05.2021 11:59   Published     (Current) Approved by Martin Lippmann on 02.06.2021 08:17
Design reviews Jorge Block 03.03.2021 18:12   Published     (Current) Approved by Martin Lippmann on 02.06.2021 08:18