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.
Search results
Jump to navigation
Jump to search
Page title matches
- Welcome to the Quality Assurance pages for EGI-InSPIRE. The Quality team is responsible for ensuring the high quality of the output of the project - the services, deliverables and processes.369 bytes (45 words) - 18:03, 24 December 2014
- #REDIRECT [[EGI-Engage:Quality Plan]]37 bytes (4 words) - 17:36, 25 May 2015
- Everything that concerns Quality Assurance should go here, e.g.: ...is responsible of generating the Quality Criteria Documents that drive the Quality Criteria Verification.15 KB (2,364 words) - 16:13, 23 March 2016
- #REDIRECT [[EGI-InSPIRE:Quality Assurance]]43 bytes (4 words) - 18:03, 24 December 2014
- |Unit= UMD/CMD Quality Assurance ...unit is responsible to handle issues about the EGI UMD Quality Assurance (Quality Criteria585 bytes (76 words) - 14:11, 29 November 2019
- #REDIRECT [[GGUS:UMD/CMD Quality Assurance FAQ]]48 bytes (7 words) - 13:50, 29 November 2019
- * Service name: UMD and CMD quality assurance The quality criteria are the functional and nonfunctional requirements that a product m5 KB (764 words) - 15:27, 21 October 2016
- 23 bytes (2 words) - 18:02, 20 November 2019
Page text matches
- |Unit= UMD/CMD Quality Assurance ...unit is responsible to handle issues about the EGI UMD Quality Assurance (Quality Criteria585 bytes (76 words) - 14:11, 29 November 2019
- #REDIRECT [[EGI-InSPIRE:Quality Assurance]]43 bytes (4 words) - 18:03, 24 December 2014
- #REDIRECT [[GGUS:UMD/CMD Quality Assurance FAQ]]48 bytes (7 words) - 13:50, 29 November 2019
- #REDIRECT [[2016-bidding/UMD CMD quality assurance]]52 bytes (6 words) - 15:27, 21 October 2016
- | Maintenance and Support/Quality Control | Software Quality2 KB (209 words) - 15:40, 24 November 2014
- Welcome to the Quality Assurance pages for EGI-InSPIRE. The Quality team is responsible for ensuring the high quality of the output of the project - the services, deliverables and processes.369 bytes (45 words) - 18:03, 24 December 2014
- ...to EGI must meet, Quality Control ensures that the software will meet the quality described earlier. Hence, Quality Control in EGI is involved in two phases of Quality Control in the relationships between EGI and its Technology Providers:3 KB (447 words) - 17:45, 29 November 2012
- * EGI Quality Assurance |service quality= Base602 bytes (77 words) - 14:13, 29 November 2019
- ...Providers as a regular forum for continuous review and improvements of the Quality Criteria defined within EGI.3 KB (362 words) - 16:58, 30 June 2021
- ...e successful execution of the project and that all its outputs are of high quality by: * Quality assurance efforts to monitor the progress of the project against its defined metrics7 KB (991 words) - 15:13, 24 December 2014
- === Task TNA1.4: Quality Assurance ===2 KB (249 words) - 21:02, 24 December 2014
- === Task TNA1.4: Quality Assurance ===2 KB (249 words) - 21:03, 24 December 2014
- === Task TNA1.4: Quality Assurance ===2 KB (249 words) - 21:03, 24 December 2014
- === Task TNA1.4: Quality Assurance ===2 KB (249 words) - 21:03, 24 December 2014
- === Task TNA1.4: Quality Assurance ===2 KB (251 words) - 21:04, 24 December 2014
- === Task TNA1.4: Quality Assurance ===2 KB (251 words) - 21:04, 24 December 2014
- === Task TNA1.4: Quality Assurance ===2 KB (251 words) - 22:55, 24 December 2014
- === Task TNA1.4: Quality Assurance ===2 KB (251 words) - 22:54, 24 December 2014
- === Task TNA1.4: Quality Assurance ===2 KB (251 words) - 22:55, 24 December 2014
- === Task TNA1.4: Quality Assurance ===2 KB (251 words) - 22:56, 24 December 2014