Guideline Quality Management Plan#
Quality Management Plan Definitions Guideline
|
status: valid
|
||||
Overall quality management:
Quality culture:
Quality as well as Safety and Security Culture is planned to grow in the SW platform. This shall be fostered by doing process conformance checks and work product reviews, as well as lessons learned
after each feature development completion and a process audit after each platform/project release. Delta audits allowed based on variation statement.
The main outcome is the Process Improvement Report (wp__process_impr_report), which is used to improve the processes for the platform/project.
Quality Management:
ASPICE 4.0 standard is selected for quality management. Processes will always link to the ISO 26262 standard, ISO PAS 8926 standard, ISO/SAE 21434:2021(E) and to the ASPICE 4.0 standard.
Communication:
Cross functional teams are interdisciplinary, so the regular (sprint) planning and review meetings enable communication. The organization of the project is described in the Project Management Plan. Another main communication means are the Pull Request (PR) reviews.
Also the standard Eclipse Foundation communication strategies are used (e.g. mailing lists, messenger).
Quality issues, non-conformances and improvements:
Feedback from the field, but also during development of change requests to existing features, bug reporting by the Open Source community or integration of existing SW components into new features may lead to the discovery of issues, non-conformances or improvements.
Non-conformance can also be deviations from the development process with impact on safety or security.
If these are known at the time of creation of a release they will be part of the Platform Release Notes (wp__platform_sw_release_note) for the feature.
Other issues and non-conformances relevant for already delivered releases will be identified as such and communicated (as defined in Problem Resolution part of the Project Management Plan) via the Issue tracking system (wp__issue_track_system).
Tailoring quality activities:
Main tailoring driver is that the SW platform is pure SW development and is provided as “SW element” - this explains mainly the generic, platform wide tailoring.
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.
Planning quality activities:
In the Quality Management Plan the nomination of the Quality Manager (rl__quality_manager) and the Project Lead (rl__project_lead) is documented.
The planning of quality activities is done using issues in the Issue tracking system (wp__issue_track_system) as specified in the Project Management part of the Project Management Plan.
It contains for each issue
* objective - as part of the issue description
* dependencies on other activities or information - by links to the respective issues
* responsible person for the activity - as issue assignee
* required resources for the activity - by selecting a team label (or “project”) pointing to a team of committers dedicated to the issue resolution
* duration in time, including start and end point - by selecting a milestone
* UID of the resulting work products - stated in the issue title
The planning of quality activities is part of
* generic planning, dealing with all work products needed only once for the platform. This is included in the Quality Management Platform Plan.
Planning supporting processes:
Supporting processes (Requirements Management, Configuration Management, Change Management, Documentation Management, Tool Management) are planned within the Project Management Plan.
Planning integration and verification:
Integration on the target hardware is not done in the scope of the SW platform project, but SW/SW integration up to the feature level is performed and its test results are part of the Platform Verification Report (wp__verification_platform_ver_report).
The integration on the target hardware, done by the distributor or OEM, is supported by delivering a set of HW/SW feature integration and Platform Integration Tests which were already run successfully on a reference HW platform.
This is planned by the respective workproducts:
Verification planning is documented in Verification Plan (wp__verification_plan)
Scheduling of audits, conformance checks, work product reviews, release verification and approval:
Scheduling is done in the same way as for all work products definition by issues. The respective work products are listed in Work product Inspections Co... (doc_concept__wp_inspections).
Planning quality trainings:
Quality trainings are planned also by issues. They should cover the following aspects:
* Target audience
* Training objectives
* Training content
* Training schedule
* Responsible persons
|
|||||