Difference between revisions of "EGI Quality Criteria Definition"

From EGIWiki
Jump to: navigation, search
(Replaced content with "{{Tech menubar}} {{SWProv menubar}} {{TOC_right}}")
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{Tech menubar}}
 
{{Tech menubar}}
{{Tech QA submenu}}
+
{{SWProv menubar}}
 +
 
 
{{TOC_right}}
 
{{TOC_right}}
 
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 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 Technoogy]] 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.
 
 
For a given UMD Release, there is only one '''FINAL''' version of the QC documents.
 
 
=== Quality Criteria Change Management ===
 
Changes in the criteria documents are triggered by one of the following sources of changes:
 
* Requirements from User Community
 
* Requirements from Operations Community (especially software incidents found in production)
 
* Deficiencies in criteria found in Verification or Stage Rollout
 
* Analysis of reference implementations of UMD Capabilities
 
* Review and analysis of feedback from Technology Providers
 
 
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.
 

Latest revision as of 14:55, 23 March 2016