Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

EGI Quality Assurance

From EGIWiki
Revision as of 18:22, 18 February 2011 by Michel (talk | contribs) (Created page with '{{Tech menubar}} {{TOC_right}} The Quality Assurance unit in EGI defines and executes the processes of * structuring, defining and assurance of technical accuracy of Quality Cri…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Technology Software Component Delivery Software Provisioning UMD Middleware Cloud Middleware Distribution Containers Distribution Technology Glossary



The Quality Assurance unit in EGI defines and executes the processes of

  • structuring, defining and assurance of technical accuracy of Quality Criteria
  • evolving Quality Criteria from a current set to a future set of criteria valid for assurance and control by Technology Providers

Contact

The contact person for Quality Assurance is Enol Fernandez del Castillo, enolfc@ifca.unican.es

Structure and Definition of Quality Criteria

EGI's Quality Critera are organised in a set of documents. The organisation of Quality Criteria follows the layout of the UMD Roadmap version for which the Quality Criteria [are valid].

One document in any given set of Quality Criteria defines Generic Quality Criteria, whereas the remaining documents define the Specific Quality Criteria.

Generic Quality Criteria apply to all Products delivered to EGI by a Technology Provider. However, some Generic Quality Criteria may not apply to a specific Product because the scope of the Product falls out of the coverage of the pertinent Generic Quality Criteria. The Quality Control team in EGI advises Technology Providers which Generic Quality Criteria apply to Products they wish to make available to EGI.

Specific Quality Criteria apply to all Products delivered to EGI that implement a specific UMD Capability. Conversely, if a Product implements more than one Capability at once, then all Specific Quality Criteria of all implemented Capabilities apply to the given Product.

Evolution of Quality Criteria

It is a well-proven fact in Software Engineering that user requirements for any given piece of software change over time. So, as requirements change, so must the software designed to satisfy these requirements. Consequently, Quality Criteria by which the quality of the software is assessed that is verified for production infrastructure availability, must evolve over time, too.

With change of Quality Criteria come multiple sets of Quality Criteria. To deliver software that matches EGI's quality demand, Technology Providers must know well in advance which set of Quality Criteria are in effect at any given point in time.


The following rules define the process of Quality Criteria validity:

  • A set of Quality Criteria covers the complete UMD Capabilities.
  • A set of Quality Criteria are valid for 6 calendar months, following the [UMD Roadmap publication schedule] with an offset of one month.
  • A set of Quality Criteria is stored in EGI's document database as a set of documents grouped in one storage location.
  • A set of Quality Criteria has a shared version, e.g. "QC-1"
  • At most one set of Quality Criteria is valid at any given point in time marked "FINAL" in EGI's document database.
  • There may be more than one set of Quality Criteria in "DRAFT" status, marked as such in the document database.
  • As time passes, FINAL sets of Quality Criteria may become "DEPRECATED" by the next version of Quality Criteria.
  • All DEPRECATED sets of Quality Criteria are kept publicly available for reference.


Quality Criteria may evolve to reflect changing user requirements. The process of evolution is captured as follows:

  1. Anyone interested in the Quality Criteria definition may review the documents, at any given point in time.
  2. Feedback and requests for change must be given through the appropriate channels associated with the reviewer's affiliation
    1. Reviews and comments from the resource operation communities must be given through the OMB
    2. Reviews and comments from the end user communities must be given, via the VRCs, to the UCB
  3. UCB and OMB are collating and prioritising the reviews and comments, and discuss them at regular TCB meetings.
  4. The TCB decides upon the changes, and in which DRAFT version of the Quality Criteria they shall be reflected.