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
|