Quality Management Plan

Summary
See section 3.2.4: Every quality management related activity necessary to ensure the adequate implementation of the project plan and to assure the quality of the project results will be defined in WP600 – Project Management. SOCRATIC considers two concepts within QA: Project Quality Assurance (PQA) and Software Quality Assurance (SQA). These two elements will be part of the Quality Management Plan (D6.1) delivered in month 3. Project Quality Assurance (PQA): The PQA will establish agreed definitions of procedures for acceptance and quality control. The procedures to be described in the PQA will address those activities needed for the smooth and effective evolution of the project across its lifecycle, and will be oriented to achieve: (i) Quality of the work performed, (ii) Quality of the documentation generated during project performance. In order to assure high quality in the work performed, the PQA will define a methodology and procedures, though a certain degree of flexibility will be retained due to the specific needs of a research project. In particular they will refer to: Requirement specifications and quality objectives definition Organisation of the working team Roles and responsibilities of each participant Control actions planned Time schedules In addition, the PQA will define whenever necessary any contingence/corrective plan. Contingency plans will include a clear statement of the incident encountered, proposed measure and detailed activity plan, responsible/s partner/s to implement the activity and potential impact to the overall project execution in terms of project cost, duration etc. If any problem arises in the performance of the obligations of the partners, related to the prompt execution of their work, correction measures should be taken (this is one of the Project Coordinator’s responsibilities). At all times, resources claimed by the project partners should correspond with the actual work performed during the reporting period and will be subject to the approval of the PC. Corrective measures taken to address problems related to the fulfilment of the obligations of the partners may lead to amendments to the Project Plan. Major changes in the Work Plan, project budget or amendments to the Contract have to be proposed by the Project Coordinator and need a written approval by all contractors in accordance with the approval of the EC. To assure the high quality of the documentation generated during project performance, two specific measures will be taken: (1) Definition of harmonized templates in documentation and reporting stages; (2) Internal quality control of the documentation. Internal reviewers responsible for final quality checking of all deliverables and major documents will be appointed. The internal review template will be attached to each document. Both measures will facilitate the adherence of SOCRATIC documentation with the EC quality standards of deliverables and EC acceptance criteria. The Quality Management Plan will be a binding document and will have to be approved and signed by all partners. When the Quality Plan is not in accordance with the Contract, the Contract will be perceived as the final binding document. Software Quality Assurance (SQA): SQA activities within the project will be described and planned in the SQA Plan. These activities will be: (i) Verification activities, e.g. peer-reviews; (ii) Unit and Integration Testing; (iii) Validation; (iv) User and Accessibility Assessment definition and planning; (v) Communication and management of incidences, etc. This plan will contain: (i) Plans for Unit & Integration Testing and Validation; (ii) Templates for reporting unit and integration testing; (iii) Templates for the validation activities; (iv) Templates for the assessments. Regarding the execution of the plan, their results will be present in several deliverables: (i) Definition of the Validation (D4.1.1) and Assessment Methodology (D4.3) will be carried out in parallel to d