EMI SA2 Internal Wiki Area

EMI SA2 Useful Links

• Weekly Meetings: SA2 Indico Agenda
• Task List: SA2 Savannah Tracker, InstructionsEmiSa2Tracker
• Mailing List Archive: http://mail.eu-emi.eu/mailman/private/emi-sa2/
• Official EMI Deliverables and EMI Milestones
• Contacts: WP and Area Leaders, EMI Product Teams, SA2 Members
• Documents: EMI TEMPLATES, EMI DoW Document, public parts (as of 20100624)

• IssuesForEMITFMunich
• PreparationEMITF2013

• IssuesforEMIAhm

EMI SA2 Tasks

• TSA2.1 – Work Package coordination (Leader: CERN, all partners participate to the meetings and reviews)
• TSA2.2 – Quality Assurance Process Definition and Monitoring (Leader: CERN. Participants: CINECA, INFN, UPJS)
• TSA2.3 – Metrics and KPIs Definition and Reporting (Leader: TCD, Participants:CERN)
• TSA2.4 – Tools and Repositories Selection, Maintenance and Integration (Leader: CERN. Participants: CINECA, GRNET, INFN, UPJS)
• TSA2.5 – QA Implementation Review and Support (Leader: UPJS. Participants: CERN, INFN, TCD, UPJS)
• TSA2.6 – Testbeds Setup, Maintenance and Coordination (Leader: INFN. Participants: CERN, CESNET, FZJ, UPJS)
• TSA2.7 – Quality Control (Task leader: CINECA. Participants: TBA)

EMI SA2 Deliverables

• DSA4.1 - Quality Assurance Plan: Definition of the global software QA processes, procedures, roles and responsibility and the related metrics and measurement methodologies. [M1]
• DSA4.2.1 - QA Tools Documentation: Describes the software engineering tools and the repository management systems provided by SA2 to EMI and third-party users. This document is updated and revised regularly [M2]
• DSA4.4 - Continuous Integration and Certification Testbeds: Describes the distributed certification testsbeds for internal and acceptance certification and its access and usage requirements [M3]
• DSA4.2.2 - QA Tools Documentation: Describes the software engineering tools and the repository management systems provided by SA2 to EMI and third-party users. Updated and revised regularly [M10]
• DSA4.2.3 - QA Tools Documentation: Describes the software engineering tools and the repository management systems provided by SA2 to EMI and third-party users. [M22]
• DSA4.3.1 - Periodic QA Reports: A report on the compliance with and results of the quality assurance process is produced monthly by the activity manager and is reported every twelve months to the EC [M3]
• DSA4.3.2 - Periodic QA Reports: A report on the compliance with and results of the quality assurance process is produced monthly by the activity manager and is reported every twelve months to the EC [M12]
• DSA4.3.3 - Periodic QA Reports: A report on the compliance with and results of the quality assurance process is produced monthly by the activity manager and is reported every twelve months to the EC [M24]
• DSA4.3.4 - Periodic QA Reports: A report on the compliance with and results of the quality assurance process is produced monthly by the activity manager and is reported every twelve months to the EC [M36]

Task Details

TSA2.2 – Quality Assurance Process Definition and Monitoring (Task leader: CERN. Participants: CINECA, INFN, UPJS)
Definition of a standards-compliant software engineering process
Continual activity of monitoring its correct application within the activities of the EMI project.
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

TSA2.3 – Metrics and KPIs Definition and Reporting (Task leader: TCD. Participants: CERN)
Definition and continual collection and reporting of software quality metrics according to suitable QA models.
Provides information to the PEB and other project bodies on status of software as an instrument for corrective actions.
Success criteria are the regular production of reports and their use to identify improvement areas.

TSA2.4 – Tools and Repositories Selection, Maintenance and Integration (Leader: CERN. Participants: CINECA, GRNET, INFN, UPJS)
Definition and when necessary maintenance of tools required to support the QA process.
Support software providers to integrate required information to and from tools maintained outside the EMI project.
Setup and maintenance of repositories for storing EMI software packages, tests, build and test reports and metrics generated during all software development activities within EMI

TSA2.5 – QA Implementation Review and Support (Task leader: UPJS. Participants: CERN, INFN, TCD, UPJS)
Review activities of QA, test and certification implementations done by the Product Teams
Sample review of test plans and tests, compliance with packaging, porting guidelines, validation of documentation, etc.
Support Product Teams in effective design and implementation of tests to be used with testing tools such as ETICS.
Success criterion for is the usage of tools and procedures by all project members to be measured by surveys and verifications

TSA2.6 – Testbeds Setup, Maintenance and Coordination (Task leader: INFN. Participants: CERN, CESNET, FZJ)
Setup and maintenance of distributed testbeds for the project continuous integration and testing operations
Coordination and provision of larger-scale testbeds from collaborating resource providers.
Success criteria for this task are the availability and reliability metrics of the execution nodes

TSA2.7 – Quality Control (Task leader: CINECA. Participants: TBA)