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.

Search results

Jump to navigation Jump to search
  • === 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) - 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 (288 words) - 22:55, 24 December 2014
  • === Task TNA1.4: Quality Assurance ===
    2 KB (305 words) - 22:56, 24 December 2014
  • ...ry from software development teams, aka Technology Providers (TP), Quality Assurance and Reporting.  #'''Software Assessment''' – through Quality Assurance & Staged Rollout
    7 KB (984 words) - 11:48, 19 February 2019
  • | UMD Roadmap Capabilities coverage with Quality Criteria | Expresses the coverage of UMD Capabilities with Quality Criteria. Value is given in percent.
    3 KB (444 words) - 19:26, 9 January 2015
  • ...ry from software development teams, aka Technology Providers (TP), Quality Assurance and Reporting. #'''Software Assessment''' – through Quality Assurance & Staged Rollout
    4 KB (697 words) - 18:31, 3 March 2017
  • *[[2016-bidding/UMD CMD quality assurance|UMD and CMD quality assurance]] *[[2015-bidding/umd quality|UMD quality assurance]]
    7 KB (868 words) - 09:54, 24 June 2021
  • === Task TNA1.4: Quality Assurance ===
    3 KB (449 words) - 22:59, 24 December 2014
  • === Task TNA1.4: Quality Assurance ===
    3 KB (475 words) - 22:59, 24 December 2014
  • ...able to service providers more quickly and directly, bypassing the quality assurance steps. The task must coordinate with the UMD and CMD quality assurance task as well as EGI Operations when necessary, and with the AppDB provider
    5 KB (711 words) - 09:46, 25 October 2016
  • *[[EGI-InSPIRE SA1 Quality Metrics]] *EGI-InSPIRE [[Quality Assurance:Main Page|quality assurance processes and metrics]]
    7 KB (1,002 words) - 23:36, 24 December 2014
  • #The evaluation of the overall performance of the project and the quality assurance and timely submission of deliverables.<br> It has representation from all the work packages and Quality manager.
    9 KB (1,362 words) - 11:11, 17 September 2015
  • ...MD repositories because they contain software verified through the quality assurance process of UMD.
    2 KB (316 words) - 16:06, 7 March 2016
  • TNA1.4 Quality assurance
    2 KB (309 words) - 23:04, 24 December 2014
  • ...ocess]]: That handles software delivery from Technology Providers, Quality Assurance and Reporting.
    3 KB (406 words) - 18:17, 7 February 2017
  • * Service name: UMD and CMD quality assurance The quality criteria are the functional and nonfunctional requirements that a product m
    5 KB (764 words) - 15:27, 21 October 2016
  • ...e UMD repositories''', which contain software verified through the quality assurance process of UMD.
    7 KB (1,044 words) - 15:27, 25 October 2017
  • * Service name: UMD quality assurance The quality criteria are the functional and nonfunctional requirements that a product m
    4 KB (682 words) - 15:21, 6 June 2016
  • | UMD quality assurance<br> | UMD quality assurance
    16 KB (1,737 words) - 09:57, 24 June 2021
  • | UMD quality assurance<br> | UMD quality assurance
    16 KB (1,721 words) - 09:58, 24 June 2021
  • | Software provisioning team, quality assurance ...included products in (1) generate a Release Candidate. Notify quality UMD assurance team.
    9 KB (1,392 words) - 16:38, 7 January 2019
  • == UMD quality assurance == The quality criteria are the functional and nonfunctional requirements that a product m
    10 KB (1,384 words) - 09:54, 24 June 2021
  • ...e UMD repositories''', which contain software verified through the quality assurance process of UMD.
    9 KB (1,263 words) - 15:27, 25 October 2017
  • ...se based on WLCG, which also provides some internal monitoring and quality assurance
    4 KB (451 words) - 12:41, 18 February 2013
  • Task 4: Quality Assurance (Catherine Gater, Project Manager, EGI.eu) Task 2: Definition of UMD Quality Criteria
    4 KB (471 words) - 12:57, 6 January 2015
  • ...the UMD repositories, which contain software verified through the quality assurance process of UMD.''
    8 KB (1,224 words) - 13:44, 9 May 2016
  • ...the UMD repositories, which contain software verified through the quality assurance process of UMD.''
    8 KB (1,237 words) - 10:58, 18 April 2016
  • ...e UMD repositories''', which contain software verified through the quality assurance process of UMD.
    8 KB (1,215 words) - 14:25, 10 October 2016
  • ...e not eligible to access the Platform, and provides an additional level of assurance for the resource providers who enable the catch-all VO (vo.access.egi.eu ) #*This is not a review of the quality of the research, but only checks that the resources devoted to the user wil
    3 KB (512 words) - 09:04, 27 October 2016
  • ...the UMD repositories, which contain software verified through the quality assurance process of UMD.''
    7 KB (1,108 words) - 16:42, 14 March 2016
  • === Task NA1.3 Quality and Risk Management === *[[EGI-Engage:Quality Assurance#Review_process_for_deliverables_and_milestones|Review process for deliverab
    5 KB (627 words) - 09:20, 28 April 2015
  • ...ters into the SR and even goes into production but that doesn´t follow the quality criteria defined in TSA2.2. Some of the reasons for doing the verification ...ier (QCV) so that the QCV can assess that the TP has tested in advance the quality of the software. Depending on the type of release, different actions will b
    13 KB (2,253 words) - 21:18, 1 December 2012
  • ...ters into the SR and even goes into production but that doesn´t follow the quality criteria defined in TSA2.2. Some of the reasons for doing the verification ...ier (QCV) so that the QCV can assess that the TP has tested in advance the quality of the software. Depending on the type of release, different actions will b
    10 KB (1,239 words) - 19:51, 9 December 2014
  • 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
  • ...ted by the EGI-InSPIRE project on a three-month basis are reported in the "Quality Plan and Project Metrics" document, produced by NA2 on annually: * [https://documents.egi.eu/document/55 "Quality Plan and Project Metrics" for project year '''one''' (May 2010 - April 2011
    18 KB (2,263 words) - 19:29, 24 December 2014
  • ...e UMD repositories''', which contain software verified through the quality assurance process of UMD.
    8 KB (1,160 words) - 15:37, 5 December 2016
  • == UMD and CMD quality assurance == The quality criteria are the functional and nonfunctional requirements that a product m
    13 KB (1,910 words) - 09:55, 24 June 2021
  • The task must coordinate with the UMD quality assurance task as well as EGI Operations when necessary, and with the AppDB provider
    4 KB (642 words) - 15:47, 6 June 2016
  • ...e UMD repositories''', which contain software verified through the quality assurance process of UMD.
    11 KB (1,581 words) - 11:06, 14 June 2016
  • * [https://documents.egi.eu/secure/ShowDocument?docid=33&version=3 Quality assurance procedures]: more comprehensive description of the review process and docum
    7 KB (951 words) - 20:45, 24 December 2014
  • ...e UMD repositories''', which contain software verified through the quality assurance process of UMD.
    13 KB (1,956 words) - 16:16, 26 September 2016
  • ...the UMD repositories, which contain software verified through the quality assurance process of UMD.''
    11 KB (1,725 words) - 14:07, 9 May 2016
  • TNA1.4 Quality assurance
    4 KB (611 words) - 23:04, 24 December 2014
  • ## Certification report(s) (from the agreed quality assurance documentation and tests) or a link.
    6 KB (1,035 words) - 23:22, 24 December 2014
  • ...e UMD repositories''', which contain software verified through the quality assurance process of UMD.
    12 KB (1,759 words) - 15:31, 7 November 2016

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)