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/quality_management/guidance/quality_plan_guideline.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
@@ -47,7 +47,7 @@ Guideline Quality Management Plan
47
47
|Tailoring is done for the whole SW platform by defining only the relevant processes and their resulting outcomes and an argumentation why the others are not needed in `ASPICE 4.0 <https://eclipse-score.github.io/process_description/main/standards/aspice_40/aspice.html>`_.
48
48
|
49
49
|**Planning quality activities:**
50
-
|In the Quality Management Plan the nomination of the quality manager :need:`rl__quality_manager` and the project lead :need:`rl__project_lead` is documented.
50
+
|In the Quality Management Plan the nomination of the :need:`rl__quality_manager` and the :need:`rl__project_lead` is documented.
51
51
|The planning of quality activities is done using issues in the :need:`wp__issue_track_system` as specified in the Project Management part of the Project Management Plan.
Copy file name to clipboardExpand all lines: process/process_areas/quality_management/guidance/quality_review_checklist.rst
+51-51Lines changed: 51 additions & 51 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,7 @@ Project Management plan review checklist template
84
84
* - PJP_00_01
85
85
- Are the purpose and goals of the project defined (including references to related projects, if existing)?
86
86
-
87
-
-
87
+
- The purpose and goals should be clearly stated.
88
88
-
89
89
* - PJP_00_02
90
90
- Is the scope of the project defined?
@@ -94,7 +94,7 @@ Project Management plan review checklist template
94
94
* - PJP_00_04
95
95
- Is the project life-cycle defined?
96
96
-
97
-
-
97
+
- The project life-cycle shall match to the purpose and goals of the project.
98
98
-
99
99
* - PJP_00_05
100
100
- Are major project metrics to track the progress described?
@@ -110,7 +110,7 @@ Project Management plan review checklist template
110
110
* - PJP_01_02
111
111
- Are skill needs and planned trainings documented/referenced?
112
112
-
113
-
-
113
+
- Check training plan and issue tracking system for related issues.
114
114
-
115
115
* - PJP_02_01
116
116
- Are the project milestones described/referenced? (And are they feasible?)
@@ -135,17 +135,17 @@ Project Management plan review checklist template
135
135
* - PJP_02_05
136
136
- Is the technical infrastructure and resources needed described?
137
137
-
138
-
-
138
+
- Check if technical infrastructure and resources match to the project needs.
139
139
-
140
140
* - PJP_03_01
141
141
- Are communication interfaces between all involved parties defined (who communicates, what, in which intervals, over which channels, internal vs. Customer communication)?
142
142
-
143
-
-
143
+
- Check if communication interfaces are defined and followed.
144
144
-
145
145
* - PJP_04_01
146
-
- Have the reports for the project being defined? (Including required content, maintenance schedule etc.)
147
-
-
146
+
- Have the reports for the project being defined? (Including required content, maintenance schedule etc.).
148
147
-
148
+
- Check if reports are defined and available.
149
149
-
150
150
151
151
@@ -171,7 +171,7 @@ Security Management plan review checklist template
171
171
172
172
* - Review Id
173
173
- Link to checklist
174
-
* - SafMP_00_01
174
+
* - SecMP_00_01
175
175
- :need:`gd_chklst__security_plan`
176
176
177
177
@@ -193,69 +193,69 @@ Quality Management plan review checklist template
193
193
- Are the quality objectives and scope aligned with the project’s standards and stakeholder requirements?
194
194
-
195
195
* - QMP_00_02
196
-
- Are all work products in the process area of quality management defined?
197
-
-
196
+
- Are work product quality goals defined?
198
197
-
198
+
- Check the definition and also if they are reachable.
199
199
-
200
200
* - QMP_00_03
201
201
- Are roles and responsibilities in the process area of quality management defined?
202
202
-
203
-
-
203
+
- Check if all needed roles are assigned to team members.
204
204
-
205
205
* - QMP_01_01
206
206
- Are quality goals and metrics for in the project specified, tracked and are they suitable for process improvement?
207
207
-
208
-
-
208
+
- Check if the defined metrics are measurable and suitable for process improvement. Check if there is a tracking done in the issue tracking system.
209
209
-
210
210
* - QMP_01_02
211
211
- Do all quality metrics have an acceptance criteria specified?
212
212
-
213
-
-
213
+
- Check if acceptance criteria are defined for all quality metrics.
214
214
-
215
215
* - QMP_01_03
216
216
- Is quality reporting described including cadence, relevant parties and documentation?
217
217
-
218
-
-
218
+
- Check if the quality reporting is following the defined cadence and if all relevant parties are involved.
219
219
-
220
220
* - QMP_02_01
221
221
- Are the quality milestones described or referenced in a quality Schedule, and are they feasible?
222
222
-
223
-
-
223
+
- Check the planning boards in the issue tracking system.
224
224
-
225
225
* - QMP_03_01
226
226
- Is the approach of conducting work product reviews defined and appropriate?
227
227
-
228
-
-
228
+
- Check if the work product reviews are following the defined process and if all relevant parties are involved.
229
229
-
230
230
* - QMP_03_02
231
231
- Is the approach of conducting process audits defined and appropriate?
232
232
-
233
-
-
233
+
- Check if the process audits are following the defined process and if all relevant parties are involved.
234
234
-
235
235
* - QMP_04_01
236
236
- Is the process of handling problems and/or non-conformances defined?
237
237
-
238
-
-
238
+
- Check if there is a defined process for handling problems and non-conformances. Check if there are related issues in the issue tracking system.
239
239
-
240
240
* - QMP_04_02
241
241
- Is there a specification on how to ensure the resolution of process non-conformances?
242
242
-
243
-
-
243
+
- Check if there are defined actions for resolving non-conformances and if they are tracked in the issue tracking system.
244
244
-
245
245
* - QMP_04_03
246
246
- Is there a specification on how to escalate process non-conformances in situations where goals of quality management conflict with those of other process areas?
247
247
-
248
-
-
248
+
- Check if there is a defined escalation process for non-conformances.
249
249
-
250
250
* - QMP_04_04
251
251
- Do the described mechanisms show that quality assurance has the independence and authority to escalate problems to appropriate levels of management?
252
252
-
253
-
-
253
+
- Check if the quality assurance has the independence and authority to escalate problems. This should be ensured by the project set up.
254
254
-
255
255
* - QMP_05_01
256
256
- Are process improvement activities planned, monitored, and documented?
257
257
-
258
-
-
258
+
- Check if there are planned process improvement activities and if they are tracked in the issue tracking system. Check if they are up to date and planned in a realistic way.
259
259
-
260
260
261
261
@@ -274,32 +274,32 @@ Configuration Management plan review checklist template
274
274
* - CMP_00_01
275
275
- Are the objectives and scope defined?
276
276
-
277
-
-
277
+
- Check if the objectives and scope are clearly defined and understood by all relevant parties.
278
278
-
279
279
* - CMP_00_02
280
280
- Is the project lifecycle according to the configuration management plan?
281
281
-
282
-
-
282
+
- Check if the project lifecycle is followed as defined in the configuration management plan.
283
283
-
284
284
* - CMP_00_03
285
285
- Are retrievals(s) described?
286
286
-
287
-
-
287
+
- Check if the retrieval processes are clearly described and followed.
288
288
-
289
289
* - CMP_00_04
290
290
- Are the branches and baselines described?
291
291
-
292
-
-
292
+
- Check if the branching and baseline strategies are clearly defined and followed.
293
293
-
294
294
* - CMP_00_05
295
295
- Is the backup and recovery for the project described?
296
296
-
297
-
-
297
+
- Check if the backup and recovery procedures are clearly described and followed.
298
298
-
299
299
* - CMP_00_06
300
300
- Is the configuration management tooling (inclusive tool names and CI build tools) described?
301
301
-
302
-
-
302
+
- Check if the configuration management tools are clearly described and used as defined.
303
303
-
304
304
305
305
@@ -312,7 +312,7 @@ Tool Management plan review checklist template
312
312
313
313
* - Review Id
314
314
- Link to checklist
315
-
* - SafMP_00_01
315
+
* - TMP_00_01
316
316
- :need:`gd_chklst__tool_cr_review`
317
317
318
318
@@ -331,7 +331,7 @@ Release Management plan review checklist template
331
331
* - RMP_00_01
332
332
- Are release notes available for every release?
333
333
-
334
-
-
334
+
- Check if release notes are created for every release. Check if the template is used and the content is complete.
335
335
-
336
336
337
337
@@ -344,7 +344,7 @@ Problem Resolution plan review checklist template
344
344
345
345
* - Review Id
346
346
- Link to checklist
347
-
* - SafMP_00_01
347
+
* - PMMP_00_01
348
348
- :need:`gd_chklst__problem_cr_review`
349
349
350
350
@@ -357,12 +357,12 @@ Change Management plan review checklist template
357
357
358
358
* - Review Id
359
359
- Link to checklist
360
-
* - SafMP_00_01
360
+
* - CMP_00_01
361
361
- :need:`gd_chklst__change_cr_review`
362
362
363
363
364
-
Release Management plan review checklist template
365
-
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
364
+
Software Verification plan review checklist template
@@ -376,32 +376,32 @@ Release Management plan review checklist template
376
376
* - SWV_00_01
377
377
- Are the objectives and scope defined?
378
378
-
379
-
-
379
+
- Check if the objectives and scope are clearly defined and understood by all relevant parties.
380
380
-
381
381
* - SWV_00_02
382
382
- Are the verification methods documented and up to date?
383
383
-
384
-
-
384
+
- Check if the verification methods are clearly described and followed.
385
385
-
386
386
* - SWV_00_03
387
387
- Are the test derivation methods documented and up to date?
388
388
-
389
-
-
389
+
- Check if the test derivation methods are clearly described and followed.
390
390
-
391
391
* - SWV_00_04
392
392
- Are the software quality criteria defined and documented?
393
393
-
394
-
-
394
+
- Check if the software quality criteria are clearly defined and understood by all relevant parties. Have a look on the reports to verify if the criteria are fulfilled.
395
395
-
396
396
* - SWV_00_05
397
397
- Are all used tools described?
398
398
-
399
-
-
399
+
- Check if all tools used for software verification are clearly described and used as defined. Are additional tools used that are not described?
400
400
-
401
401
* - SWV_00_06
402
402
- Are verification setups and variants described, documented and up to date?
403
403
-
404
-
-
404
+
- Check if the verification setups and variants are clearly described and followed.
405
405
-
406
406
407
407
@@ -414,7 +414,7 @@ Documentation Management plan review checklist template
414
414
415
415
* - Review Id
416
416
- Link to checklist
417
-
* - SafMP_00_01
417
+
* - DMP_00_01
418
418
- :need:`gd_chklst__documentation_review`
419
419
420
420
@@ -430,28 +430,28 @@ Software Development Plan review checklist template
430
430
- passed [yes | no]
431
431
- Remarks
432
432
- Issue link
433
-
* - SWV_00_01
433
+
* - SDP_00_01
434
434
- Are the objectives and scope defined?
435
435
-
436
+
- Check if the objectives and scope are clearly defined and understood by all relevant parties.
436
437
-
437
-
-
438
-
* - SWV_00_02
438
+
* - SDP_00_02
439
439
- Are the design and programming languages defined?
440
440
-
441
+
- Check if the design and programming languages are clearly defined and suitable for the project.
441
442
-
442
-
-
443
-
* - SWV_00_03
443
+
* - SDP_00_03
444
444
- Are coding guidelines available, documented and up to date?
445
445
-
446
+
- Check if coding guidelines are followed and if they are up to date.
446
447
-
447
-
-
448
-
* - SWV_00_04
448
+
* - SDP_00_04
449
449
- Is a software configuration guideline available, documented and up to date?
450
450
-
451
+
- Check if the software configuration guideline is followed and if deviations have an approved argumentation by the CODEOWNER.
451
452
-
452
-
-
453
-
* - SWV_00_05
453
+
* - SDP_00_05
454
454
- Are all SW development tools described?
455
455
-
456
-
-
456
+
- Check if all tools used for software development are clearly described. If possible check if they are used as defined.
Copy file name to clipboardExpand all lines: process/process_areas/quality_management/quality_concept.rst
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,12 +43,10 @@ Stakeholders for the Quality Management
43
43
* Consult and execute Quality Trainings
44
44
* Monitoring/improving of Quality activities
45
45
46
-
#. :need:`Technical Lead <rl__technical_lead>`
47
-
* Support the work products
48
-
* Approval of Quality Management Plan, Platform Process Audit, Feature Process Conformance Checks, Work Product Reviews, Consult and Execute Quality Trainings, Monitor/Improve Quality Activities
49
-
50
46
#. :need:`Project Lead <rl__project_lead>`
51
47
* Approval of Platform Release
48
+
* Support the work products
49
+
* Approval of Quality Management Plan, Platform Process Audit, Feature Process Conformance Checks, Work Product Reviews, Consult and Execute Quality Trainings, Monitor/Improve Quality Activities
52
50
53
51
#. :need:`Committer <rl__committer>`
54
52
* Support the Work Product Reviews
@@ -80,5 +78,5 @@ or in a continuous manner. Only 100% compliant work products / releases will be
80
78
81
79
Every person who contributes shall be trained according to Quality aspects. The committers will help to ensure the Quality
82
80
by following the workflows which are defined in the different process areas. The Quality Manager is responsible for the
83
-
Quality related workflows. The Quality Manager shall be independent from the development organisation with a escalation
81
+
Quality related workflows. The Quality Manager shall be independent from the development organization with a escalation
84
82
to the Project Lead Circle and the Technical Lead Circle.
0 commit comments