You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: process/process_areas/architecture_design/architecture_concept.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -280,7 +280,7 @@ The *static view* shows the *building blocks* of the architecture. It shall be c
280
280
- comp_arc_sta
281
281
- comp_arc_sta_t
282
282
283
-
To represent the CI build tool artifact an additional container (or package) is introduced. It can only contain components:
283
+
To represent the CI build tool module (for example a `Bazel Modules <https://bazel.build/external/module>`_) an additional container (or package) is introduced. It can only contain components:
284
284
285
285
.. list-table:: Definition of the static module view
Copy file name to clipboardExpand all lines: process/process_areas/safety_management/index.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ Safety Plans
64
64
65
65
This SW platform project defines two levels of planning: platform and module. There will be one safety plan on platform level and several safety plans on module level (one for each module).
66
66
This is how we organize our development teams and repositories. Each of these safety plan "creates" one SEooC.
67
-
The :need:`Platform Safety Plan <wp__platform_safety_plan>` exists only once and is part of the :need:`Platform Management Plan <wp__platform_mgmt>` of S-CORE.
67
+
The :need:`Platform Safety Plan <wp__platform_safety_plan>` exists only once and is part of the :need:`Platform Management Plan <wp__platform_mgmt>`.
0 commit comments