Application Problem Resolution The “Invisible Problem” or

Slides:



Advertisements
Similar presentations
Testing Workflow Purpose
Advertisements

Test Execution and Defect management. 2 Module Objectives Introduction to Test Execution Checklist of Test Execution Defect management Defect Classification.
Automated Software Testing: Test Execution and Review Amritha Muralidharan (axm16u)
Chapter 4 Quality Assurance in Context
Validata Release Coordinator Accelerated application delivery through automated end-to-end release management.
04b | Manage Test Execution (2 of 2) Steven Borg | Co-founder & Strategist, Northwest Cadence Anthony Borton | ALM Consultant, Enhance ALM.
Mike Azocar Sr. Developer Technical Specialist Microsoft Corporation
SwE 434. Rational Quality Manager Rational Quality Manager is a collaborative, Web-based tool that offers comprehensive test planning, test construction,
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Defect Tracking Solution Nethzah Inc.. Defect tracking overview Defect Tracking Solution module of Nethzah CRM is designed for small, medium and large.
0 Copyright 2008 Global 360, Inc. All Rights Reserved Presentation of Success Story Robert Lang.
QWise software engineering – refactored! Testing, testing A first-look at the new testing capabilities in Visual Studio 2010 Mathias Olausson.
Introduction Optimizing Application Performance with Pinpoint Accuracy What every IT Executive, Administrator & Developer Needs to Know.
By Touseef Tahir Software Testing Basics. Today's Agenda Software Quality assurance Software Testing Software Test cases Software Test Plans Software.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Software Research, Inc. Setting the Standard for Software Testing Windows Solution.
1 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. GET PROACTIVE! With Oracle Premier Support.
Copyright © 2003 by Release Engineering Inc. All Rights Reserved. Software Manufacturing: Leveraging Release Management Sandy Currier CTO.
Introduction to Software Engineering. Why SE? Software crisis manifested itself in several ways [1]: ◦ Project running over-time. ◦ Project running over-budget.
Software Engineering 2004 Jyrki Nummenmaa 1 BACKGROUND There is no way to generally test programs exhaustively (that is, going through all execution.
CSC444F'07Lecture 41 CSC444 Software Engineering Top 10 Practices.
Incident Management A disruption in normal or standard business operation that affects the quality of service Goal: restore normal service as quickly as.
Requirements. Outline Definition Requirements Process Requirements Documentation Next Steps 1.
Perfecto We help customers deliver exceptional digital experiences.
Test Automation Steffen Goerlitz Barry Lange Mitchell Meerman Harry Schultz Trevor Spees.
ABOUT COMPANY Janbask is one among the fastest growing IT Services and consulting company. We provide various solutions for strategy, consulting and implement.
SAP MDG (Master Data Governance) online training Online | classroom| Corporate Training | certifications | placements| support CONTACT US: MAGNIFIC TRAINING.
NEWGEN SOFTWARE TECHNOLOGIES INC.
Requirements Determination
Configuration Management
Test Lab Management and
Applied Software Testing
Kick Your Microsoft® Excel® Habit with Autodesk® PLM 360
Payment Approval Workflow Automation
Use Cases Discuss the what and how of use cases: Basics Benefits
CompTIA Server+ Certification (Exam SK0-004)
Approaches to ---Testing Software
Introduction to Marketing Research
SOFTWARE TESTING OVERVIEW
Improving the Defect Life Cycle Management Process
Chapter 18 Maintaining Information Systems
Computer Aided Software Engineering (CASE)
TIM 58 Chapter 3: Requirements Determination
ServiceNow Implementation Knowledge Management
IT Service Operation - purpose, function and processes
Solution Summary Business Service Management Solution on AIX® 6.1.
HCI in the software process
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
Software Engineering (CSI 321)
Software Quality Engineering
ITIL: Why Your IT Organization Should Care Service Support
Engineering Processes
ITIL: Why Your IT Organization Should Care Service Support
Automated Testing and Integration with CI Tool
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
Amendment Invoice Task Force Progress Report
HCI in the software process
Baisc Of Software Testing
HCI in the software process
ITIL: Why Your IT Organization Should Care Service Support
Amendment Invoice Task Force Progress Report
Principles of Customer Service
Human Computer Interaction Lecture 14 HCI in Software Process
Rapid software development
Accelerating Product Development with EPM
Requirements Engineering
To Brihaspathi. Software Development Services
3PL Logistic Software. What is a 3PL? You take the orders. Your third-party logistics provider (3PL) fulfils them. It’s that simple and if it’s seamless,
Presentation transcript:

Application Problem Resolution The “Invisible Problem” or True Process Improvement Opportunity? Bob Levy Sr. Systems Engineer – Process Improvement ©2007 BMC Software

Problem Resolution – Manual Process The manual process is the way problem resolution has always been performed We MUST improve this process with automation Document / Gather Recreate Analyze Fix Automated Virtually Eliminated Accelerated Unchanged ©2007 BMC Software

Why is Problem Resolution so Difficult? Problem Resolution is all about getting root cause 80% 20% ROOT CAUSE ANALYSIS FIX GATHER  RECREATE  ANALYZE Because symptoms rarely reflect the root cause, the process of root cause analysis is manual, based on trial-and-error and therefore highly inefficient and time-consuming. ©2007 BMC Software

Root Cause Analysis Stages Gather Information Recreate Problem Analyze Information Problem information gathering is manual and consumes a very long time Information includes screen prints, textual descriptions, etc. Incorrect problem categorization results in gathering the wrong information Problems must be recreated on-demand, multiple times throughout the process Often, symptoms are recreated rather than true root cause Every re-creation is a manual process that takes a long time Based on categorization of the problem Multiple iterations are often required for obtaining additional information Multiple specialized tools are often used ©2007 BMC Software

Problem Resolution in Pre-Release Workflow Testing Development   - Problem is uncovered during a test Problem information is gathered and documented in a defect tracking tool  - Developer receives a defect report - Requests additional information  - Tester/user recreates the problem - Gathers additional information  - Developer requests different data  - Recreates the problem - Gathers additional information  - Recreates the problem - Analyzes the problem - Fixes the problem - Delivers a patch ©2007 BMC Software

Problem Resolution in Maintenance Workflow Support/Operations End-Users/ Production   A problem is reported to support/operations  Support/operations engineers gather information and try to resolve the issue  Developers analyze the problem, determine root cause and fix it  Most problems are resolved – small percentage of problems are escalated to development  Development communicates with support/operations multiple times to gather information and attempt to recreate the problem Development ©2007 BMC Software

Proposed Solution: A black box application recorder like the blackbox on an airplane... ©2007 BMC Software

Proposed solution to Application Problem Resolution Root Cause Analysis Capture full problem information (like a black box on an airplane) Eliminate the need to manually gather Information Eliminate need to recreate problems or problem environments Eliminate need to access production data Becomes a standard part of the process Provide 25%–35% efficiency to the development organization ©2007 BMC Software

Pre-Release Problem Resolution Automation Testing Development Test Lab  integrated into defect tracking process   records all problem information during test execution  - Developer receives a defect report Opens the information in recording - Analyze without recreating  - Developer fixes problem ©2007 BMC Software

Maintenance Workflow with Automation Support/Operations End-Users/ Production  A problem is reported to support/operations  Support/operations engineers gather information and try to resolve the issue  A very small percentage of problems are escalated to development  Development activates recording and retrieves problem log Development  Development analyzes recording, determines root cause and fixes the problem ©2007 BMC Software

Problem Resolution Automation Summary Eliminate problems recreation Eliminate non-reproducible problems Reduce back and forth Integrate with existing defect/problem process Deliver consistent and accurate and complete information Deliver improved quality Deliver improved customer satisfaction Deliver faster time to market My contact information Bob Levy blevy@bmc.com 708.205.5373 ©2007 BMC Software