Project-X 3.0 Quality Criteria. QA Criteria Milestones Ø System Integration Complete (September) ùReady to start building production servers. Ø Project-X.

Slides:

Advertisements

Similar presentations

IOTAP Software Build Process Author: Aman Choudhary Draft Version – Work In Progress.

Advertisements

© Copyright 2006 FPT Software 1 © FPT SOFTWARE – TRAINING MATERIAL – Internal use 04e-BM/NS/HDCV/FSOFT v2/3 How to work in Fsoft project Authors: KienNT.

QuEdge Testing Process Delivering Global Solutions.

SOFTWARE TESTING. Software Testing Principles Types of software tests Test planning Test Development Test Execution and Reporting Test tools and Methods.

PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.

Web Development Engineering Processes Introduction to Web Development Outsourcing Processes.

Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)

Quality Management System

Software Project Transition Planning

CSE 115 Week 14 April , Announcements April 14 – Exam 10 April 14 – Exam 10 April 18 – Last day to turn in Lab 8 for any credit April 18.

Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.

 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.

Software Engineering Institute Capability Maturity Model (CMM)

Release & Deployment ITIL Version 3

Using The WDK For Windows Logo And Signature Testing Craig Rowland Program Manager Windows Driver Kits Microsoft Corporation.

4/20/2017 6:38 PM © 2004 Microsoft Corporation. All rights reserved.

EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks gLite Release Process Maria Alandes Pradillo.

Test Organization and Management

Software Testing Life Cycle

From Research Prototype to Production

A Microsoft Perspective Kirby Bartholomew Product Manager Application Platform & Developer Marketing

EMI SA2: Quality Assurance (EMI-SA2 Work Package) Alberto Aimar (CERN) WP Leader.

EMI INFSO-RI EMI SA2 Report Quality Assurance Alberto Aimar (CERN) SA2 WP Leader.

1 © Quality House QUALITY HOUSE The best testing partner in Bulgaria.

Installation and Maintenance of Health IT Systems

1.  Project: temporary endeavor to achieve some specific objectives in a defined time  Project management ◦ Dynamic process ◦ Controlled and structured.

EMI SA2: Quality Assurance (EMI-SA2 Work Package) Alberto Aimar (CERN) WP Leader.

EMI INFSO-RI SA2 - Quality Assurance Alberto Aimar (CERN) SA2 Leader EMI First EC Review 22 June 2011, Brussels.

Software Engineering Project: Research Expert Prabhavathi Kumarasamy Joshua Thompson Paul Varcholik University of Central Florida.

Project Post-Mortem University of California Berkeley Extension Copyright © 2008 Patrick McDermott From an AutoContent Wizard 10/27/2007.

Erich Gatejen Exec Status 30 May Overall Status Project-X is on schedule. Application-Y on schedule  We are spending a lot of time working on the.

QUALITY ASSURANCE PRACTICES. Quality Plan Prepared and approved at the beginning of project Soft filing system approach followed. Filing location – –

Software Development A Proposed Process and Methodology.

Network design Topic 6 Testing and documentation.

EMI INFSO-RI Guidelines and SQA Process Maria Alandes Pradillo (CERN) SA2.2 Task Leader.

Rob Davidson, Partner Technology Specialist Microsoft Management Servers: Using management to stay secure.

EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Task tracking SA3 All Hands Meeting Prague.

European Middleware Initiative (EMI) The Software Engineering Model Alberto Di Meglio (CERN) Interim Project Director.

Economic Justification. Good Enough Quality Time to market Time to market Time to profit Time to profit.

Timesheet training Version: Introduction Duration: 1.5 hours Purpose: Guide on how to use Timesheet.

Sprint 113 Review / Sprint 114 Planning August 12th, 2013.

Cyberinfrastructure Release 2 Production Readiness Review 12 December 2013.

RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct

JRA1 Meeting – 09/02/ Software Configuration Management and Integration EGEE is proposed as a project funded by the European Union under contract.

EMI INFSO-RI SA2: Quality Assurance Status Report Alberto Aimar(SA2) SA2 Leader EMI First EC Review 22 June 2011, Brussels.

AGILE PROJECT MANAGEMENT WITH TEAM FOUNDATION SERVER 2010 Brian Keller Microsoft.

Softheme Service Model Software Outsourcing Solutions.

INFSOM-RI WP3: WP3: Software configuration tools and methodologies Status Report ETICS All-Hands – 23 May 2007 E. Ronchieri.

Software Configuration Management (SCM)

Constructing Deploying and Maintaining Enterprise Systems

Managing the Project Lifecycle

[Project Name] Post-Mortem

Software and System Delivery

PROJECT NAME POST-MORTEM

Description of Revision

CMGT 410 NEW Become Exceptional/ newtonhelp.com. CMGT 410 All Assignments (New Syllabus) For more course tutorials visit CMGT 410 Assignment.

Raytheon Parts Management

YeahMobi CD Practice based on Container -- openstack meetup

Amendment Invoice Task Force Progress Report

What is user acceptance testing and how is it different than system testing Kusum daga.

Continuous Localization

Internal QA in Open Source Development

Baisc Of Software Testing

Overall Project RAG Status

Development Lifecycle

[Project Name] Post-Mortem Presentation Template

Project Name Post-Mortem

Amendment Invoice Task Force Progress Report

Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.

{Project Name} Organizational Chart, Roles and Responsibilities

Presentation transcript:

Project-X 3.0 Quality Criteria

QA Criteria Milestones Ø System Integration Complete (September) ùReady to start building production servers. Ø Project-X QA Complete (November) ùQA accepts the software Ø Franchise GA(late-November) ùReady for shipment to external customer

System Integration Complete Criteria Ø Code complete Ø Integration tests complete Ø Application integration and interoperability testing complete Ø No backlog of bugs ùNo OPEN bugs over 3 days old Ø System running in staging environment

System Integration Complete QA assessment of progress against criteria Goal = 0 Percent complete

Project-X QA Complete Criteria Ø QA testing completed Ø Staging and Testing community testing complete Ø All bugs closed (Fixed or Postponed) Ø No Priority 1 or Priority 2 bugs in system Ø Final documentation reviewed and approved Ø Software ready for mass production and packaging

Project-X Franchise GA Criteria Ø Final media verified ùDocumentation ùSoftware media (i.e. CDs) ùPackaging Ø System put into production Ø Marketing and sales collateral ready Ø Training materials are ready Ø Prof Serv, Customer Support, Deployment enabled

Staging and Testing Community Lab Ø Create a model of the “real world” in lab environment Ø Enable end-to-end tests with all products Ø Integrate 3rd party products and connectivity, such as suppliers, for testing and certification. Ø Provide a realistic environment to test all software, patches and configurations before rolling them into production. Ø Now building this lab for current products

Staging and Trading Community Testing Ø Build the staging and trading community lab Ø Execute planned end-to-end testing of all products that will interact with system Ø Test both software and operational procedures Ø Verify documentation and deployment processes Ø Test and certify all initial external integrations Ø Dry-run “power-on” for live 3.0 service

QA Progress Ø Functional testing in process. Expect to complete in September. Ø Now tracking Bug Metrics Ø Now tracking Test Metrics

Quality Assurance Metrics Bug Metrics - Week 33

Quality Assurance Metrics Test Metrics - Week 33 Major Categories of Testing and QA Tasks