Task SA2.7: Quality Control

Task Description

This task consists in the application of QA processes and procedures defined by SA2. All the releases of EMI components need to satisfy well-defined certification and validation criteria before being included in a stable EMI distribution, sufficient to guarantee to a high degree of confidence that all EMI products meet or exceed the requirements set by EGI and that no regression are introduced. The Product Teams are responsible to perform the QC task as part of their standard maintenance activities. This task also deals with security assessments of selected EMI components under the coordination of CSIC. The main success criterion of this task is the availability of regression tests for each resolved software defect.

The Quality Control task is responsible to carry out:

  • periodic reviews, on the base of predefined check-lists, to constantly control the performance of the SA1 team and collect measurements according to quality assurance metrics defined in SA2 (Task 2.3);
  • project deliverables to summarize the status and performance of the quality control tasks.

Periodic review

The quality control task is responsible to carry out periodic reviews, on the base of predefined check-lists, and collect measurements according to quality assurance metrics defined in SA2 (Task 2.3). Any problem, divergences from metric thresholds and inconsistence will be reported to SA2 for further evaluation.

Tracking the verification of components

  • The verification of certified components is tracked using the SA2.7 tracker

  • A verification cycle is scheduled every week and follows the EMI 1 Updates Schedule
    • first Monday (Mo1) - during the EMT meeting, the Release Manager communicates to QC leader which tasks among those certifies should be verified firs certified tasks
    • first Monday (Mo1) - the QC leader opens a new task on SA2 Tracker using a standard subject [SA2.7] Verification of components (i.e. Verification of components - Week August 1-5)

Test availability survey

EMI QC verification report template and script

Deliverables

  • DJRA1.7.1 - Software Development Quality Control Report

List of quality control reviews

Responsibilities Matrix

To carry out the quality control reviews, the collaboration of all the SA1 partners is needed. Thus, the following matrix reports (it is just a proposal), for each scheduled review, the partner which is responsible to perform it.

Each review must be completed 5 days (10 days in case it is due on the same date of a deliverable) before the deadline for internal review.

The wiki system must be used to write the review (click-on the PM number to access the template for the executing the review)

PM # Partner Comments Status
PM6 - end of October 2010 CINECA DSA1.3.1 Done
PM9 - end of January 2011 INFN To move to the end of February 2011 - DSA1.3.2 Done
PM12 - end of April 2011 CESNET   Done
PM15 - end of July 2011 UU  
PM18 - end of October 2011 UIO  
PM21 - end of January 2012 JUELICH To move to the end of February 2012 - DSA1.3.3
PM24 - end of April 2012 DESY  
PM27 - end of July 2012 SWITCH  
PM30 - end of October 2012 FOM  
PM33 - end of January 2013 CERN To move to the end of February 2013 - DSA1.3.4
PM36 - end of April 2013 UH  

Project deliverable

The Software Maintenance and Quality Control reports should summarize the results of the Software Release Plan Review, Software Release Schedule Review and Software Maintenance and Support Plan Review. It should also contains details on availability and execution of regression tests for the supported EMI components, the unit test availability and coverage and various static and dynamic metrics on released components. Each deliverable will include the responses obtained from the quality reviews.

List of quality control deliverables

  • DSA1.3.1 - Software Maintenance Quality Control Report End of October 2010.
  • DSA1.3.2 - Software Maintenance Quality Control Report End of February 2011.
  • DSA1.3.3 - Software Maintenance Quality Control Report End of February 2012.
  • DSA1.3.4 - Software Maintenance Quality Control Report End of February 2013.

Components validation activity

EMI Release Due date Status Details
EMI 1 March 21st 2011 HOLD GO

Security Assessment Activity

Regression Test Availability

Middleware Test Plan Test Report
ARC    
dCache    
gLite    
UNICORE X X

Test Plan

References

Topic attachments
I Attachment History Action Size Date Who Comment
PDFpdf EMI.SA1.cineca.pdf r1 manage 344.7 K 2010-07-15 - 10:08 GiuseppeGiacomoFiameniExCern SA1 Quality Control - Kick Off Presentation
Edit | Attach | Watch | Print version | History: r26 < r25 < r24 < r23 < r22 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r26 - 2012-11-12 - DoinaCristinaAiftimiei
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback