EMI SA2 - Quality Assurance

About EMI SA2

• Type of activity: OTHER
• Work package number: WP4
• Start month 1
• End month 36
• Lead beneficiary: CERN
• Work Package Leader: Alberto Aimar

Objectives

• Define and establish a common software quality assurance process and metrics for all engineering activities
• Allow the EMI middleware to consistently pass the customer acceptance criteria and continually improve the software quality and the process itself by monitoring the metrics value trends, reviewing quality control activities and related tests, providing support and consultancy in QA matters
• Enable a continuous integration and testing process by selecting and maintaining tools and resources for building and testing software either within the project of in collaboration with external resource providers

EMI SA2.1 – Work Package coordination (Task leader: CERN, all partners participate to the meetings and reviews) This task deals with the regular coordination of the Work Package, reporting and review of milestones and deliverables.

EMI SA2.2 – Quality Assurance Process Definition and Monitoring (Task leader: CERN. Participants: CINECA, INFN, UPJS) This task deals with the definition of a standards-compliant software engineering process and the continual activity of monitoring its correct application within the activities of the EMI project. The success criteria of this task are the availability of an agreed, documented and regularly updated process and the minimization of deviation in its application by the project members.

EMI SA2.3 – Metrics and KPIs Definition and Reporting (Task leader: TCD. Participants: CERN) This task deals with the definition and continual collection and reporting of software quality metrics according to the A-QCM model or other suitable models. This task provides information to the Project Executive Board and other project decisional bodies on the status of the software as an instrument to take corrective actions. The success criteria of this task are the regular production of reports and their use to identify improvement areas.

EMI SA2.4 – Tools and Repositories Selection, Maintenance and Integration (Task leader: CERN. Participants: CINECA, GRNET, INFN, UPJS) This task deals with the definition and when necessary maintenance of the tools required to support the QA process. The task includes any supporting activity to software providers to integrate required information to and from other tools maintained outside the EMI project. The task also include the setup and maintenance of repositories for storing the EMI software packages, tests, build and test reports and metrics generated during all software development activities within EMI.

EMI SA2.5 – QA Implementation Review and Support (Task leader: UPJS. Participants: CERN, INFN, TCD) This task includes review activities of the QA, test and certification implementations done by the Product Teams, such as sample review of test plans and tests, compliance with packaging and porting guidelines, validation of documentation, etc. The task also includes supporting the Product Teams in effective design and implementation of tests to be used with testing tools such as ETICS. The success criterion for this task is the correct usage of tools and procedures by all project members to be measured by regular surveys and verifications

EMI SA2.6 – Testbeds Setup, Maintenance and Coordination (Task leader: INFN. Participants: CERN, CESNET, DESY, JUELICH, UPJS) This task consists in the setup and maintenance of distributed testbeds for the project continuous integration and testing operations and the coordination and provision of larger-scale testbeds from collaborating resource providers. The success criteria for this task are the availability and reliability metrics of the execution nodes.