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

Slides:

Advertisements

Similar presentations

QuEdge Testing Process Delivering Global Solutions.

Advertisements

CD FY08 Tactical Plan Status FY08 Tactical Plan Status Report for Network Investigations Rick Finnegan April 22, 2008.

Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13

MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.

ITIL: Service Transition

Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.

EmpowHR 9.0 Upgrade Status Meeting Thursday, June 12, :30 A.M. – 4:00 P.M. (EDT)

Visual Studio Online. What it Provides Visual Studio Online, based on the capabilities of Team Foundation Server with additional cloud services, is the.

© The McGraw-Hill Companies, Software Project Management 4th Edition Monitoring and control Chapter 9.

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)

Rational Unified Process

Mike Azocar Sr. Developer Technical Specialist Microsoft Corporation

Outline (Mis)communicating expectations Schedule of class-related deliverables Specific final release deliverables Your questions Intellectual activity:

Implementation/Acceptance Testing CSE Week 8 / 1 CSE9020 Case Study Week 8 Implementation and Acceptance Testing.

Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.

Testing - an Overview September 10, What is it, Why do it? Testing is a set of activities aimed at validating that an attribute or capability.

1 Walk-in slide. 2 How to Manage a System Upgrade The Good, The Bad and The Ugly of Conversions David Cervelli Managing Consultant April 25, 2006.

Agile Testing with Testing Anywhere The road to automation need not be long.

SAIC-F QA Internal Process (DRAFT ) Sudha Chudamani QA Team, Frederick National Lab Jan 2, 2013.

National Finance Center’s 2008 Customer Forum EmpowHR 9.0 Billy Dantagnan Teracore.

PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.

Release & Deployment ITIL Version 3

Effective Methods for Software and Systems Integration

CERN - European Organization for Nuclear Research Windows 2000 at CERN HepNT- Orsay, France April 24 th, 2001.

“Here’s why you need the new wheels, too…” Shawn and Steve Image from

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

US Dept. of Housing and Urban Development Office of Community Planning and Development IDIS Project Status December 15, 2005.

Project Management Development & developers

Transaction Processing Systems and System Development Life Cycle

CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.

T Project Review Magnificent Seven Project planning iteration

CORE Executive Board March 31, 2010 Next CEB April 28, 2010.

EGEE is a project funded by the European Union under contract IST Testing processes Leanne Guy Testing activity manager JRA1 All hands meeting,

AWIPS II Update Shannon White. AWIPS I Status Due to the AWIPS II transition, only critical bug fixes have been deployed in the last year With the delay.

Sampleminded® Support Overview Last Updated: 1/22/

T Project Review X-tremeIT I1 Iteration

Overview & High Level Plan Date: Team: Todd Kaywood, Alex Wiechers, Andy Idema.

Status of Windows 2000 deployment at CERN Alberto Pace, for the IT/IS group - April 2002

N O T E “CLICK” TO CONTINUE… If the slide show is not launched, click on View  Slide Show in the menu bar at the top of the Power Point window. When the.

Planning Iteration Demo Suunto Training Program Planner.

Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)

Rational Unified Process Mr Hisham AlKhawar. Iterative versus Waterfall  We need to use a life cycle model in order to approach developing a system easily,

September Interface Kickoff Sunflower Project Statewide Management and Reporting Tool Update September 02, 2009.

TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.

What is Testing? Testing is the process of exercising or evaluating a system or system component by manual or automated means to verify that it satisfies.

Novell Compliance Management Platform Update CMP & CMP Extension for SAP Environments Leo Castro Product Marketing Manager Patrick Gookin.

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

March 11, 2008 Texas Nodal Market Redesign Program Commercial Operations Subcommittee.

February 5, 2009 Technical Advisory Committee Meeting Texas Nodal Program Implementation: Program Update Trip Doggett.

Retail Business Processes PR 50121_07 Project Update Retail Market Subcommittee September 13, 2006 Adam Martinez Mgr, Market Operations DPO.

Project management Topic 1 Project management principles.

July, 2008 Impati – Software Test Solutions. July, Contents Testing Service Overview and Approach Test Services and Industries Key Services Offering.

JWST PRDS Project Mangement Case Study Jesse Doggett Project Engineer, ITEB/OED.

Nodal Program Update Mike Cleary Sr. VP and Chief Technology Officer.

TPTF CIM Health Check Raj Chudgar Program Director for Market Redesign.

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

Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.

T Project Review RoadMappers I2 Iteration

Cyberinfrastructure Release 2 Production Readiness Review 12 December 2013.

The Next Level Of Agile: DevOps and CD אוקטובר 2015.

Chapter 7: Delivery, Installation, and Documentation Ronald J. Leach Copyright Ronald J. Leach, 1997, 2009, 2014,

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

Items to consider before automating an application

Amendment Invoice Task Force Progress Report

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

Software Development Process

Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC

Amendment Invoice Task Force Progress Report

Amendment Invoice Task Force Progress Report

Amendment Invoice Task Force Progress Report

Presentation transcript:

Erich Gatejen Exec Status 30 May 2002

Overall Status Project-X is on schedule. Application-Y on schedule  We are spending a lot of time working on the documentation. Product-F 1.1 (Cycle 2) is 50% done.  We are a little behind.  Fix pack in test. Service Packs (July Release) are ahead of schedule. GOLD Labs and other services all ok.

Status of outstanding milestones Project-X Functional Testing is done. Application-Y is about 20% done.  We have to create the documentation.  Unit Testing is done.  Functional Testing started. Working on Cycle II of Project-F. Services Pack for W2K Testing is done.  Strange bug found. # It will take several days to investigate. (MEDIUM Schedule Risk)  Issues may require a new cycle of testing. Solaris packs underway.  All done except Module-J.  Bug numbers are in line with expectations.

Project-X Dashboard ComponentWindows due 11 JunSolaris due 11 Jun Platformpassed Portaltesting Tracking and Accountingtestingloading Connectorstesting Management Consoleproblemstesting Conversion subsystemtestingloading Content Managertesting User Managerpassedloading Interface Managertesting Application-YloadingN/A Application-ZtestingN/A {blank}loadingproblemstestingpassed

Key Items from Tasking Orders For the week of 27 May  Slack time for Service Packs Load any Cycle II service packs, if they fix critical issues.  Resume Application-T deployment (Bravo-1).  Module-J testing (round 2)  Application-Y integration and handoff (round 1)  Project-F testing (cycle 2) For the week of 3 Jun  Complete Application-T deployment (Bravo-1).  Accept Release Candidates for Project-X  Complete Module-J testing  Project-F testing (cycle 3)  Acceptance Testing for any outstanding Service Packs.

Lab Delivery Schedule: 6/4Application-Y and Application-Z (build cycle 5/27) - Handoff to developers for bug regression testing. 6/4SP releases for both, Windows and Solaris. - Delivered early. 6/10Direct Connect lab (Solaris) 6/11SP releases after Final Acceptance (for both, Windows and Solaris) - Handoff for training. 6/17GOLD updates

Issues & Risk  The component teams *must* meet build and install criteria for this schedule to work.  I.e. automated installers, migration in less than an hour for standard test data set, et al.  Content Manager currently violates this criteria. We have a workable solution that involves documenting manual steps.  All others appear ok.  Application-X and Application-Y documentation need a lot of work.  We may have to continue this after the RTM and roll the documentation CD later.