Defect MgmtBugDay Bangkok 2009: Defect Management

1

Defect Management

2

By. Maysinee NakmaneeBy. Maysinee Nakmanee

Background: Maysinee Nakmanee

Re-engineering Projects-BankingCenter of Software EngineeringTeaching/Guest Speaker for public/private org.Thompson-Reuters/Global Development– Global configuration management tool– Global defect tracking tool

(current) DSTi- IFDS Group– International Financial Development Service

3


What is defect?

Something wrong in the systemCan we live in the “defect-free” world?What people can do to prevent the defect?

4


Defect/Bug TypesMild - misspell output, lack of white spaceModerate - output may be misleading or redundantAnnoying - users need tricks to get system to workDisturbing - refuses to handle legitimate transactionSerious - looses track of transaction and its occurrenceVery serious - bug causes system to incorrect transactionExtreme - problem limited to a few user or a few transaction type, frequent, and arbitraryIntolerable -long term unrecoverable corruption of database, system shutdown may need to occurInfectious - corrupts other systems, system that causes loss of life

5


Defect Management Process

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

6


Defect Reporting

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

7


Defect Severity vs. Priority

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.

8


A sample defect tracking process

I. Run Test

II. Log Defects

III. Investigate Defects

IV. Defect Resolution Process

1. Priority the correction2. Schedule the correction3. Correct the defect4. Report the resolution

V. Report the resolution

9


10


“Traceability”

11


Traceability of Requirement to Testing

Traceable from– Requirements – Planning– Development– Testing

12


TestingUnit Test

System TestRegression Test

Stabilization TestUser Acceptance Test

Testing

13


14


Defect Information

What is the defectsWho foundWho will fixIn which area

15

By. Maysinee NakmaneeBy. Maysinee NakmaneeDefect Type

• 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 but not the code issue.

16

By. Maysinee NakmaneeBy. Maysinee NakmaneeRoot cause of defects

• 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.

17

By. Maysinee NakmaneeBy. Maysinee NakmaneePriority of defects

18


Impacted Area

Impact: Fix one part may affect to other parts. This may cause “Defective fix” defect.Review of impacted area is the most important before any resolution

19


Fix Defects

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

20


Fix Defects

Would that be possible that some defects have never been fixed?What will affect to the system?Why we do that?

21


Defect Metrics

22


Defects Metrics

Phase InjectedPhase foundHow many priority defectsHow quick we can resolve the defectsRoot cause of the defectsHow long a defect has been openned

23


Defect Management

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

24


Defects as requirements

Collection of defects from previous release/version can be come requirements for next release.– Production issue defects– Minor defects

25


Summary

Defect management is the most important process that all stakeholders need to aware of.

Considering defect information to support defect management.

Date post:	20-Nov-2014
Category:	Technology
Upload:	guest476528
View:	1,632 times
Download:	3 times

Defect MgmtBugDay Bangkok 2009: Defect Management

Technology