BugDay Bangkok 2009 Defect Management
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

BugDay Bangkok 2009 Defect Management

on

  • 819 views

Session: Defect Management 1/3

Session: Defect Management 1/3
Event: BugDay Bangkok 2009
Venue: Sripatum University
Date: December 19th, 2009

Statistics

Views

Total Views
819
Views on SlideShare
818
Embed Views
1

Actions

Likes
1
Downloads
17
Comments
1

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • good info.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

BugDay Bangkok 2009 Defect Management Presentation Transcript

  • 1. Defect Management 1
  • 2. Background: Maysinee Nakmanee By. Maysinee Nakmanee Re-engineering Projects-Banking Center of Software Engineering Teaching/Guest Speaker for public/private org. Thompson-Reuters/Global Development – Global configuration management tool – Global defect tracking tool (current) DSTi- IFDS Group 2 – International Financial Development
  • 3. What is defect? By. Maysinee Nakmanee Something wrong in the system Can we live in the “defect-free” world? What people can do to prevent the defect? 3
  • 4. Defect/Bug Types By. Maysinee Nakmanee Mild - misspell output, lack of white space Moderate - output may be misleading or redundant Annoying - users need tricks to get system to work Disturbing - refuses to handle legitimate transaction Serious - looses track of transaction and its occurrence Very serious - bug causes system to incorrect transaction Extreme - problem limited to a few user or a few transaction type, frequent, and arbitrary Intolerable -long term unrecoverable corruption of database, system shutdown may need to occur Infectious - corrupts other systems, system that 4 causes loss of life
  • 5. Defect Management Process By. Maysinee Nakmanee Refer to as “Incident Management Tools” Prevent Defect Find the defect as quickly as possible Should be – Impact analysis – Root-cause analysis – Improve the process 5
  • 6. Defect Reporting By. Maysinee Nakmanee Defects are recorded for four major purpose – Ensure defect is corrected – Report status of the application – Gather statistics used to develop defect expectation in future application – To improve the software development process 6
  • 7. Defect Severity vs. Priority By. Maysinee Nakmanee Severity: Defect may be defined as one that causes data corruption or system crash, security violation. Priority: The order in which defects should be fixed. It is more subjective as it may be based on input from users regarding which defects are most important, resources available, risks. 7
  • 8. A sample defect tracking process By. Maysinee Nakmanee I. Run Test II. Log Defects III. Investigate Defects IV. Defect Resolution Process 1. Priority the correction 2. Schedule the correction 3. Correct the defect 4. Report the resolution V. Report the resolution 8
  • 9. By. Maysinee Nakmanee 9
  • 10. By. Maysinee Nakmanee “Traceability” 10
  • 11. Traceability of Requirement to Testing By. Maysinee Nakmanee Traceable from – Requirements – Planning – Development – Testing 11
  • 12. Testing By. Maysinee Nakmanee Testing Unit Test System Test Regression Test Stabilization Test User Acceptance Test 12
  • 13. By. Maysinee Nakmanee 13
  • 14. Defect Information By. Maysinee Nakmanee What is the defects Who found Who will fix In which area 14
  • 15. Defect Type By. Maysinee Nakmanee • When testers found the defects, we need to recheck first whether it is code issue or code related or not. • Sometimes, it may be defect from environment from data that has been conversed 15 but not the code
  • 16. Root cause of defects By. Maysinee Nakmanee • The most important thing in defect management is to be able to identify the root cause of defect in order to prevent the future problem. 16
  • 17. Priority of defects By. Maysinee Nakmanee 17
  • 18. Impacted Area By. Maysinee Nakmanee Impact: Fix one part may affect to other parts. This may cause “Defective fix” defect. Review of impacted area is the most important before 18 any resolution
  • 19. Fix Defects By. Maysinee Nakmanee Developer needs to provide – Resolution – When to finish the fix – Impacted area – Root cause of the defect – Unit test result of the fix Tester needs to – Re-assure the solution – Re-test and Close the defect 19
  • 20. Fix Defects By. Maysinee Nakmanee Would that be possible that some defects have never been fixed? What will affect to the system? Why we do that? 20
  • 21. Defect Metrics By. Maysinee Nakmanee 21
  • 22. Defects Metrics By. Maysinee Nakmanee Phase Injected Phase found How many priority defects How quick we can resolve the defects Root cause of the defects How long a defect has been openned 22
  • 23. Defect Management By. Maysinee Nakmanee Collaboration between all parties – Developers – Testes – Business Analyst – System Analyst Sometimes, Fix is a nice to have but may not be a need to do 23
  • 24. Defects as requirements By. Maysinee Nakmanee Collection of defects from previous release/version can be come requirements for next release. – Production issue defects – Minor defects 24
  • 25. Summary By. Maysinee Nakmanee Defect management is the most important process that all stakeholders need to aware of. Considering defect information to support defect management. 25