Difference between revisions of "EGI Quality Criteria Definition"

From EGIWiki
Jump to: navigation, search
m
m
Line 5: Line 5:
 
The Quality Criteria (QC) Definition Task is responsible of generating the Quality Criteria Documents that drive the Quality Criteria Verification.
 
The Quality Criteria (QC) Definition Task is responsible of generating the Quality Criteria Documents that drive the Quality Criteria Verification.
  
== Quality Criteria Roadmap ==
+
== Quality Criteria Lifecycle ==
Quality Criteria definition is a continuous process driven by the requirements of users and operations communities, however the verification of new software releases is done against fixed release dates of the QC documents every 6 months. Between major these major releases, two minor releases are made available for lightweight review (one minor release every 2 months). The QC releases are done in coordination with the [[EGI Roadmap and Technology]] releases.
+
 
 +
Quality Criteria definition is a continuous process driven by the requirements of users and operations communities, however the verification of new software releases is done against fixed date releases of the QC documents, due every 6 months. Between major these releases, two draft versions are made available for lightweight review.  
 +
 
 +
The QC releases are done in coordination with the [[EGI Roadmap and Technology]] releases.
  
 
There are 3 different possible states for the Quality Criteria documents:
 
There are 3 different possible states for the Quality Criteria documents:
Line 13: Line 16:
 
* '''DEPRECATED''', for documents that are no longer used in verification.
 
* '''DEPRECATED''', for documents that are no longer used in verification.
  
For a given UMD Release, there is only one '''FINAL''' version of the QC documents.
+
Please check the [[EGU_Quality_Criteria_Dissemination|dissemination information]] in order to ensure that you are using the correct version of the QC documents.
 +
 
 +
=== Quality Criteria and UMD Releases ===
 +
 
 +
The QC documents collect criteria for capabilities of a specific [[UMD_Release_Process|UMD Major Release]]. Only one '''FINAL''' version of QC documents is active for any given UMD Release. In the case of having more than one major UMD release active, i.e. new products are verified and made available in different UMD repositories, the verification will use the '''FINAL''' version of QC documents for each UMD release. Check the [[EGU_Quality_Criteria_Dissemination|dissemination information]] for determining which QC version should be used for the verification.
  
 
== Quality Criteria Change Management ==
 
== Quality Criteria Change Management ==
Line 27: Line 34:
  
 
Moreover, the Quality Criteria Release Notes include an overview of the most relevant changes produced in the whole set of criteria documents.
 
Moreover, the Quality Criteria Release Notes include an overview of the most relevant changes produced in the whole set of criteria documents.
 +
 +
== Quality Criteria Metrics ==

Revision as of 11:59, 4 April 2011

Technology Software Component Delivery Software Provisioning UMD Middleware Cloud Middleware Distribution Containers Distribution Technology Glossary


Quality Assurance | Quality Criteria Definition | Quality Criteria Dissemination | Quality Criteria Verification | Verifier Guideline | Verification Testbed | Glossary





The Quality Criteria (QC) Definition Task is responsible of generating the Quality Criteria Documents that drive the Quality Criteria Verification.

Quality Criteria Lifecycle

Quality Criteria definition is a continuous process driven by the requirements of users and operations communities, however the verification of new software releases is done against fixed date releases of the QC documents, due every 6 months. Between major these releases, two draft versions are made available for lightweight review.

The QC releases are done in coordination with the EGI Roadmap and Technology releases.

There are 3 different possible states for the Quality Criteria documents:

  • FINAL, meaning that the documents are actively used for verification of software products
  • DRAFT, for documents that are in preparation and will be used in the future for verification.
  • DEPRECATED, for documents that are no longer used in verification.

Please check the dissemination information in order to ensure that you are using the correct version of the QC documents.

Quality Criteria and UMD Releases

The QC documents collect criteria for capabilities of a specific UMD Major Release. Only one FINAL version of QC documents is active for any given UMD Release. In the case of having more than one major UMD release active, i.e. new products are verified and made available in different UMD repositories, the verification will use the FINAL version of QC documents for each UMD release. Check the dissemination information for determining which QC version should be used for the verification.

Quality Criteria Change Management

Changes in the criteria documents are triggered by one of the following sources of changes:

Any change to criteria is tracked in the Related Information field that includes any links to direct source of change for the criterion (e.g. RT ticket with user requirement) and the Revision Log field, that records the historic information about the changes in the criterion.

Moreover, the Quality Criteria Release Notes include an overview of the most relevant changes produced in the whole set of criteria documents.

Quality Criteria Metrics