© 2012 IBM Corporation Rational Insight | Back to Basis Series Working on Enhancement/Defect Nick Hu Shuai 2012/05/17.

Slides:



Advertisements
Similar presentations
Object Oriented Analysis And Design-IT0207 iiI Semester
Advertisements

Process and Product Quality Assurance (PPQA)
SERVICE MANAGER 9.2 PROBLEM MANAGEMENT TRAINING JUNE 2011.
Creating and Submitting a Necessary Wayleave Application
Course Web Site – Also linked from Blackboard Course Materials – Excel Tutorials – Access Tutorials – PPT.
E-Portfolio July2014 Managing Multi-source Feedback.
0 Chicago, IL March 6 th, 2007 Use Case Requirements, Design and Standards Selection HITSP Use Case Requirements, Design and Standards Selection Date:
CS405 Project Management 1. Project Management “A well-planned project will take twice as long as originally expected; a poorly-planned project, three.
More CMM Part Two : Details.
Evaluating Requirements. Outline Brief Review Stakeholder Review Requirements Analysis Summary Activity 1.
Software Delivery. Software Delivery Management  Managing Requirements and Changes  Managing Resources  Managing Configuration  Managing Defects 
Need your MyMathLab card with your access code Need a Valid Address Need to know Purdue’s zip code is and your course ID for your Class You.
ITIL Problem Management Tool Guide Gerald M. Guglielmo ITIL Problem Manager CD-doc
TEAM FOUNDATION SERVER (TFS) By Sunny Niranjana Devi. M.
© Mahindra Satyam 2009 Project Metrics QMS Training.
Case Submittal Best Practice
Solutions Summit 2014 Discrepancy Processing & Resolution Terri Sullivan.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
System Analysis and Design
LBTO IssueTrak User’s Manual Norm Cushing version 1.3 August 8th, 2007.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Translation Verification Testing Rational Insight - Jiang Xuan
© 2012 IBM Corporation Rational Insight | Back to Basis Series Chao Zhang Unit Testing.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Work on a Defect from QA Liu Xue Ning.
SEIMS SUPPORT N.C. State Board of Elections
Chapter 1: Introduction to Project Management
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
CMPT 275 Software Engineering
SPS policy – Information Presentation Presentation to ROS June 16, 2004.
Copyright (c) Cem Kaner. 1 Software Testing 1 CSE 3411 SWE 5411 Assignment #1 Replicate and Edit Bugs.
Table of Contents (click on an error to jump to that slide)
DEBUGGING. BUG A software bug is an error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Chao Zhang Code Review.
SOML Large Optics Daily Reporting Guide to using the new ETSEDMS server for Large Optics Daily Reporting.
BMTRY 789 Lecture 11: Debugging Readings – Chapter 10 (3 rd Ed) from “The Little SAS Book” Lab Problems – None Homework Due – None Final Project Presentations.
Human Resources 1 G-Top Global Workflow Employee View September 2014.
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
CSC 4700 Software Engineering
Chapter 8 Testing. Principles of Object-Oriented Testing Å Object-oriented systems are built out of two or more interrelated objects Å Determining the.
Test status report Test status report is important to track the important project issues, accomplishments of the projects, pending work and milestone analysis(
Evaluating Requirements
Chapter 5 How are software packages developed?. What are the main steps in software project development? Writing Specifications - Analysis Phase Developing.
TESTING FUNDAMENTALS BY K.KARTHIKEYAN.
Chapter 16 Maintaining Information Systems. Objectives:  Explain and contrast four types of system maintenance.  Describe factors affecting maintenance.
Software Maintenance1 Software Maintenance.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
Zortec Business Tax: Session 2 Local Government Corporation
Chapter 25 – Configuration Management 1Chapter 25 Configuration management.
Use Cases Discuss the what and how of use cases: Basics Examples Benefits Parts Stages Guidelines.
Swat Team Responsibilities and Best Practices
BU Power Tools & Accessories – PT&A Task management – Definitions
David Hatten Developer, UrbanCode 17 October 2013
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Causal Analysis & Resolution (CAR) Support Category
Regression Testing with its types
Fighting bugs or piling them? Anton Březina
Use Cases Discuss the what and how of use cases: Basics Benefits
Security SIG in MTS 05th November 2013 DEG/MTS RISK-BASED SECURITY TESTING Fraunhofer FOKUS.
Chapter 18 Maintaining Information Systems
Reliance Supplier Corrective Action Process
Roberta Roth, Alan Dennis, and Barbara Haley Wixom
Adding and editing users
Adding and Editing Users
FTS 2 Failure Tracking System 2 Repair Process Flow
Reliance Supplier Corrective Action Process
Welcome to Corporate Training -1
Maintaining Information Systems (SAD- 18)
CS5123 Software Validation and Quality Assurance
Project Name - Testing Iteration 1 UAT Kick-off
Workflows at Austin Water Labs
Presentation transcript:

© 2012 IBM Corporation Rational Insight | Back to Basis Series Working on Enhancement/Defect Nick Hu Shuai 2012/05/17

© 2012 IBM Corporation Rational Insight | Back to Basis Series 2 9/29/2016 Definitions A software enhancement is used to implement the software requirement. In engineering, a requirement is a singular documented physical and functional need that a particular product or service must be or perform. (Wikipedia) A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. (Wikipedia)

© 2012 IBM Corporation Rational Insight | Back to Basis Series 3 9/29/2016 States

© 2012 IBM Corporation Rational Insight | Back to Basis Series 4 9/29/2016 New  Triage Assign to owner. It means a preliminary investigation of the solution. The owner can over the WI to others, if its not his/her field to resolve it. Metric: Must Fill: Estimation: How much time you will need to accomplish the WI. Abs(timspent- estimation)/estimation < 50%. Planned For: Assign it to an appropriate Iteration. Priority: Change the Priority to a certain level, based on if it’s urgent. Response to the historical comments if necessary. Search for potential duplicate and duplicate it. Add subscribers and adjust other items if necessary.

© 2012 IBM Corporation Rational Insight | Back to Basis Series 5 9/29/2016 Triage  In Progress It means the implementation of the enhancement, or the resolution of the defect. Must Fill: Timespent: Daily update the time spent Correction: If the estimate isn’t correct Due Date: Expected date when the WI can be resolved. Priority: Change it if necessary Discussion: Comments should be well composed – *Touch the spot. – *If you need his/her actions, please Relations If the WI depends on the resolutions of other WI, please create “Dependency” between them. If the WI has certain relations: Same root cause, Causal relation and etc, Please link them as related If you break down the WI into smaller unit, please create the Parent-Child relation. If the WI needs a technote, please create a Task for UA and link them.

© 2012 IBM Corporation Rational Insight | Back to Basis Series 6 9/29/2016 In Progress  Resolved It means new functions will be added to the system, and errors will be adjusted without affecting existing functions. Metric Must do: Unit test to make sure the deliverable works as expected. Run personal build to make sure the deliverable won’t break build Check in the change set and Submit for review. The mandatory is any WI above “Major” severity or code change > 50 lines. Specify the test case in comments (What scenario is covered) Fill time spent

© 2012 IBM Corporation Rational Insight | Back to Basis Series 7 9/29/2016 In Progress  Resolved Resolutions: (R:RRDI,I:Insight) (I,R)“Duplicate” needs to specify the work item duplicated in links section. (I,R)“Won’t Fix” indicates that this is an issue but won’t be fixed for some reason. (I,R)“Works for Me” means the defect can’t be reproduced on owner’s machine (I,R)“Invalid” indicates that it is an invalid defect. (R)“Track Elsewhere” indicates there’s another WI tracking the same issue (R)“Information Provided” can’t or don’t have to fix it, because there’s an official document to address the issue. Defer:

© 2012 IBM Corporation Rational Insight | Back to Basis Series 8 9/29/2016

© 2012 IBM Corporation Rational Insight | Back to Basis Series 9 9/29/2016 Revision History AuthorDateVersionComment Initial Draft