TSA2.2 QC Change Management

Slides:



Advertisements
Similar presentations
Demand Planning Scenario Overview
Advertisements

Stoimen Stoimenov QA Engineer QA Engineer SitefinityLeads,SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
©© 2013 SAP AG. All rights reserved. Project Management Scenario Overview Planning Project Scenario Explorer Open Legend Project Manager Scenario Description.
Release & Deployment ITIL Version 3
3 Dec 2003Market Operations Standing Committee1 Market Rule and Change Management Consultation Process John MacKenzie / Darren Finkbeiner / Ella Kokotsis,
SQA Architecture Software Quality By: MSMZ.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI Unified Middleware Distribution (UMD): SW provisioning to EGI Mario David.
11-July-2011, SURFnet Heather Flanagan, COmanage Project Coordinator Benn Oshrin, COmanage Developer Scott Koranda, U. Wisconsin – Milwaukee and LIGO.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI Future support of EGI services Tiziana Ferrari/EGI.eu Future support of EGI.
EMI SA2: Quality Assurance (EMI-SA2 Work Package) Alberto Aimar (CERN) WP Leader.
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI SA2 services evolution (after the end of EGI-InSPIRE) Peter Solagna, Michel.
EMI INFSO-RI Guidelines and SQA Process Maria Alandes Pradillo (CERN) SA2.2 Task Leader.
JRA2: Quality Assurance Overview EGEE is proposed as a project funded by the European Union under contract IST JRA.
EMI INFSO-RI SA1 – Maintenance and Support Francesco Giacomini (INFN) SA1 Leader 1 st EMI Periodic Review Brussels, 22 June 2011.
EMI INFSO-RI SA1 Session Report Francesco Giacomini (INFN) EMI Kick-off Meeting CERN, May 2010.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI SA2 – Software Provisioning Michel Drescher Technical Manager EGI.eu SA2.
EMI INFSO-RI SA1 – Maintenance and Support Francesco Giacomini (INFN) EMI First EC Review Brussels, 22 June 2011.
Managing TDM Drawings Lifecycle WorkFlow Created: March 30, 2006 Updated: April 10, 2006 By: Tony Parker.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI WP5 Review Michel Drescher EGI.eu SA2 – Michel Drescher - EGI-InSPIRE EC.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI WP5 Review Michel Drescher EGI.eu SA2 – Michel Drescher - EGI-InSPIRE EC.
Project Services and Status reports Project Leader:Penelope Constanta Stakeholders:CD Project and Activity Leaders Resources: Ruth, Pordes, Penelope Constanta,
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI UMD Roadmap Steven Newhouse 14/09/2010.
©© 2013 SAP AG. All rights reserved. Product Development Scenario Overview Open Legend Project Manager Scenario Description The following business roles.
INDIGO Outreach and Exploitation process Peter Solagna, Matthew Viljoen EGI.eu.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI Evaluation of Liferay modules EGI-InSPIRE mini-project Gergely Sipos EGI.eu.
What’s New in SPEED APPS 2.3 ? Business Excellence Application Services.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI UMD Platform Documentation Álvaro Simón CESGA 02/12/2011 SA2 TF2011, Amsterdam1.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI EGI Software Repository Progress Report Kostas Koumantaros et al, GRNET 7/3/2016.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI EGI Release Process Michel Drescher, EGI Kostas Koumantaros, GRNET 7/5/2016.
EGI-InSPIRE RI EGI-InSPIRE RI EGI-InSPIRE Software provisioning and HTC Solution Peter Solagna Senior Operations Manager.
EGI-Engage is co-funded by the Horizon 2020 Framework Programme of the European Union under grant number Federated Cloud Update.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI MPI VT report OMB Meeting 28 th February 2012.
SA2 Steven Newhouse EGI-InSPIRE (INFSO RI ).
SLAs with Software Provider. Scope “…declare the rights and responsibilities between EGI.eu and the Software Provider for a particular component.” Which.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI SA2 – Software Provisioning Michel Drescher Technical Manager EGI.eu SA2.
Requirements Gathering
Documentation, Best Practices and Procedures: Roadmap
Visualising and sharing statistical narratives
HMA Follow On Activities
QA/QC in the United Kingdom National Atmospheric Emissions Inventory (NAEI) Task Force for Emissions Inventories and Projections – QA/QA Workshop, Krakow,
Software Development Life Cycle Waterfall Model
Configuration Management
Demand Planning Scenario Overview
EGI Operations Management Board
Managing the Project Lifecycle
Technical Coordination Board
Software Verification and Validation
Configuration Management
Outline Introduction Objectives Motivation Expected Output
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
9/18/2018 Department of Software Engineering and IT Engineering
SQA Role during Software Requirements Phase
CMMI – Staged Representation
Product Development Scenario Overview
Demand Planning Scenario Overview
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
BioMedBridges – Work Packages 2 & 12
Project Management Scenario Overview
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
EGI support services Science gateway developers
From STAB teleconference minutes
Evaluation use in practice
Proposal on TSC policy for ONAP release Maintenance
Street Manager Training approach
Balázs Kónya, Lund University NorduGrid Technical Coordinator
Implementing the ESS Vision 2020
ICG-WIGOS, eigth session, Jan 2019
Presentation transcript:

TSA2.2 QC Change Management SA2 F2F Amsterdam

QC QC relations Definition Verification Quality Control Operations Comm. User Comm. QC UMD Roadmap Verif. & SR TP

QC  Verification (I) QC releases every 6 months (along with UMD roadmap) Stable documents for TP and verification. Announcement of new versions at EGI wiki, TCB and software quality task force Release notes with most relevant information Only one QC Release is active at a given moment Current Release DocDB #240

QC  Verification (II) How to assure correct QC are used? Dissemination of latest version to interested parties (TP and SA2.3) through the available communication channels Is that enough? Watermark the non active documents? Provide only online versions?

QC  Verification (III) QC is an iterative and constant process 6 months releases ensure stability for verification and TP TPs and TSA2.3 need to anticipate changes New tests must be developed New verification templates must be created Proposal: DRAFT documents updated periodically every 2 months Should allow all stakeholders to plan their efforts

Definition QC Need a way to track all changes in QC documents Release notes of QC releases with most relevant changes History field of each criterion records changes Include in each criterion a new Source field with the actual source

QC Change Sources External (to SA2.2) sources : Requirements from User Community Requirements from Operations Community Especially software incidences found in production Verification and Stage Roll-out of products Internal (to SA2.2) sources: Analysis of UMD Capabilities (i.e. creation of initial criteria for new capabilities) Review of existing criteria, analysis of received feedback

QC Source Tracking External sources Internal sources Requirements from Users  RT ticket of requirement Requirements from Operations Community  RT and/or GGUS tickets Verification and Stage Roll-out of products  verification/SR summaries Internal sources Analysis of capabilities  reference(s) used in the analysis Review  history field is enough, it should already have a source.