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: docs/modules/communication/docs/safety_mgt/module_safety_plan.rst
+52-53Lines changed: 52 additions & 53 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Module Safety Plan
29
29
Functional Safety Management Context
30
30
====================================
31
31
32
-
This Safety Plan adds to the :need:`doc__platform_safety_plan` all the module development relevant work products needed for ISO 26262 conformity.
32
+
This Safety Plan adds to the :need:`doc__score_platform_safety_plan` all the module development relevant work products needed for ISO 26262 conformity.
Additional to the tailoring in the SW platform project as defined in the :need:`doc__platform_safety_plan` we define here the additional tailoring on module level.
58
+
Additional to the tailoring in the SW platform project as defined in the :need:`doc__score_platform_safety_plan` we define here the additional tailoring on module level.
59
59
60
60
- Excluded for this module are additionally the following work products (and their related requirements):
To create the safety package (according to :need:`gd_guidl__saf_package`) the following
202
+
documents and work products status have to go to "valid" (after the relevant verification were performed).
203
+
204
+
Module Documents Status
205
+
-----------------------
206
+
207
+
For all the work product documents the status can be seen by following the "Link to WP".
208
+
A summary of the status is also documented in the project's documentation management plan.
209
+
210
+
See :ref:`documents_docs_modules_communication_docs`
211
+
212
+
Component Documents Status
213
+
--------------------------
214
+
215
+
For all the work product documents the status can be seen by following the "Link to WP".
216
+
A summary of the status is also documented in the project's documentation management plan.
217
+
218
+
See :ref:`documents_docs_modules_communication_components`
219
+
220
+
Component Requirements Status
221
+
-----------------------------
222
+
223
+
not documented as needs, `lola trlc <https://github.com/eclipse-score/communication/blob/main/score/mw/com/requirements/component_requirements/component_requirements_ipc.trlc>`_
224
+
shows no status attribute
225
+
226
+
Component AoU Status
227
+
--------------------
228
+
229
+
.. needtable::
230
+
:filter: "communication" in docname and "requirements" in docname and docname is not None
231
+
:style: table
232
+
:types: aou_req
233
+
:tags: communication
234
+
:columns: id;status;tags
235
+
:colwidths: 25,25,25
236
+
:sort: title
237
+
238
+
Component Architecture Status
239
+
-----------------------------
240
+
241
+
see document link :need:`doc__lola_architecture` (as above)
0 commit comments