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
Note: In case the component is a new development, :need:`wp__sw_component_class` shall be removed from the above list (and also from the folders).
258
205
In case an OSS element is used in the module, part 6 has to be filled out.
@@ -262,63 +209,70 @@ OSS (sub-)component qualification plan
262
209
263
210
For the selected OSS component the following work products will be implemented (and why):
264
211
265
-
If the OSS element is classified as a
212
+
If the OSS element is classified as
266
213
- component, then the below table shall match the above, adding the reasoning for tailoring of work products according to the OSS component classification.
267
214
- lower level component, then no work products additional to the component’s will be planned and activities below are part of the component’s issues.
268
215
269
216
.. list-table:: OSS (sub-)component <name> Work products
270
217
:header-rows: 1
271
218
272
219
* - Work product Id
273
-
- Link to issue
274
220
- Reasoning for tailoring
275
221
276
222
* - :need:`wp__requirements_comp`
277
-
- <Link to issue>
278
223
- Always needed (for Q and QR classification) and also improves process Id 2
279
224
280
225
* - :need:`wp__requirements_comp_aou`
281
-
- <Link to issue>
282
226
- Always needed (for Q and QR classification) and also improves process Id 5
283
227
284
228
* - :need:`wp__requirements_inspect`
285
-
- n/a
286
-
- Checklist used in Pull Request Review
229
+
- <Reasoning for tailoring>
287
230
288
231
* - :need:`wf__cr_mt_comparch`
289
-
- <Link to issue>
290
232
- <Reasoning for tailoring, needed for example in case of deficits in process Id 3&4 and complexity Ids 1&4>
291
233
292
234
* - :need:`wp__sw_component_fmea`
293
-
- <Link to issue>
294
235
- <Reasoning for tailoring, could help arguing too high cyclomatic complexity covered by safety mechanisms>
295
236
296
237
* - :need:`wp__sw_arch_verification`
297
-
- <Link to issue>
298
238
- <Reasoning for tailoring, needed if also wf__cr_mt_comparch is required>
299
239
300
240
* - :need:`wp__sw_implementation`
301
-
- n/a
302
-
- If source code is modified, this is not a OSS qualification any more.
241
+
- Tailored - If source code is modified, this is not a OSS qualification any more.
303
242
304
243
* - :need:`wp__verification_sw_unit_test`
305
-
- <Link to issue>
306
244
- <Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 3>
307
245
308
246
* - :need:`wp__sw_implementation_inspection`
309
-
- <Link to issue>
310
247
- <Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 2>
311
248
312
249
* - :need:`wp__verification_comp_int_test`
313
-
- <Link to issue>
314
250
- Always needed (for Q and QR classification)
315
251
316
252
* - :need:`wp__sw_component_class`
317
-
- <Link to issue>
318
253
- Always needed as basis for tailoring.
319
254
320
-
Work Product Status (for Safety Package)
321
-
========================================
255
+
Module Safety Package
256
+
=====================
257
+
258
+
To create the safety package (according to :need:`gd_guidl__saf_package`) the following
259
+
documents and work products status have to go to "valid" (after the relevant verification were performed).
260
+
261
+
Module Documents Status
262
+
-----------------------
263
+
264
+
For all the work product documents the status can be seen by following the "Link to WP".
265
+
A summary of the status is also documented in the project's documentation management plan.
266
+
267
+
See <add here the section reference to the documentation management plan>
268
+
269
+
Component Documents Status
270
+
--------------------------
271
+
272
+
For all the work product documents the status can be seen by following the "Link to WP".
273
+
A summary of the status is also documented in the project's documentation management plan.
274
+
275
+
See <add here the section reference to the documentation management plan>
0 commit comments