Unit 4: Defect Management
CO4 : Identify bugs to create defect report of given application.
What is defect?
Defect: A defect is an error or a bug, in the application which is created. A programmer
while designing and building the software can make mistakes or errors. These mistakes or
errors mean that there are flaws in the software. These are called defects.
Defects in any system may arise in various stages of development life cycle. At each stage,
the impact and cost of fixing defects are dependent on various aspects including the defect
arising stage.
Different causes of software defects
Miscommunication of requirements introduces error in code
Unrealistic time schedule for development
Lack of designing experience
Lack of coding practices experience
Human factors introduces errors in code
Lack of version control
Buggy third-party tools
Last minute changes in the requirement introduce error
Poor Software testing skill
Defect Classification
Defect Classification
1.Severity Wise 2.Work Product Wise
3.Type Of Error Wise
, Unit 4: Defect Management
Severity Wise:
Major: A defect, which will cause an observable product failure or departure
from requirements.
Minor: A defect that will not cause a failure in execution of the product.
Fatal: A defect that will cause the system to crash or close abruptly or effect
other applications.
Work product wise:
SSD: A defect from System Study document
FSD: A defect from Functional Specification document
ADS: A defect from Architectural Design Document
DDS: A defect from Detailed Design document
Source code: A defect from Source code
Test Plan/ Test Cases: A defect from Test Plan/ Test Cases
User Documentation: A defect from User manuals, Operating manuals
Type of Errors Wise:
Comments: Inadequate/ incorrect/ misleading or missing comments in the
source code
Computational Error: Improper computation of the formulae / improper business
validations in code.
Data error: Incorrect data population / update in database
Database Error: Error in the database schema/Design
Missing Design: Design features/approach missed/not documented in the
design document and hence does not correspond to requirements
Inadequate or sub optimal Design: Design features/approach needs additional
inputs for it to be complete Design features described does not provide the best
approach (optimal approach) towards the solution required
In correct Design: Wrong or inaccurate Design
Ambiguous Design: Design feature/approach is not clear to the reviewer. Also
includes ambiguous use of words or unclear design features.
Boundary Conditions Neglected: Boundary conditions not addressed/incorrect
Interface Error: Internal or external to application interfacing error,
Incorrect handling of passing parameters, Incorrect alignment,
incorrect/misplaced fields/objects, un friendly window/screen positions
Logic Error: Missing or Inadequate or irrelevant or ambiguous functionality
in source code
CO4 : Identify bugs to create defect report of given application.
What is defect?
Defect: A defect is an error or a bug, in the application which is created. A programmer
while designing and building the software can make mistakes or errors. These mistakes or
errors mean that there are flaws in the software. These are called defects.
Defects in any system may arise in various stages of development life cycle. At each stage,
the impact and cost of fixing defects are dependent on various aspects including the defect
arising stage.
Different causes of software defects
Miscommunication of requirements introduces error in code
Unrealistic time schedule for development
Lack of designing experience
Lack of coding practices experience
Human factors introduces errors in code
Lack of version control
Buggy third-party tools
Last minute changes in the requirement introduce error
Poor Software testing skill
Defect Classification
Defect Classification
1.Severity Wise 2.Work Product Wise
3.Type Of Error Wise
, Unit 4: Defect Management
Severity Wise:
Major: A defect, which will cause an observable product failure or departure
from requirements.
Minor: A defect that will not cause a failure in execution of the product.
Fatal: A defect that will cause the system to crash or close abruptly or effect
other applications.
Work product wise:
SSD: A defect from System Study document
FSD: A defect from Functional Specification document
ADS: A defect from Architectural Design Document
DDS: A defect from Detailed Design document
Source code: A defect from Source code
Test Plan/ Test Cases: A defect from Test Plan/ Test Cases
User Documentation: A defect from User manuals, Operating manuals
Type of Errors Wise:
Comments: Inadequate/ incorrect/ misleading or missing comments in the
source code
Computational Error: Improper computation of the formulae / improper business
validations in code.
Data error: Incorrect data population / update in database
Database Error: Error in the database schema/Design
Missing Design: Design features/approach missed/not documented in the
design document and hence does not correspond to requirements
Inadequate or sub optimal Design: Design features/approach needs additional
inputs for it to be complete Design features described does not provide the best
approach (optimal approach) towards the solution required
In correct Design: Wrong or inaccurate Design
Ambiguous Design: Design feature/approach is not clear to the reviewer. Also
includes ambiguous use of words or unclear design features.
Boundary Conditions Neglected: Boundary conditions not addressed/incorrect
Interface Error: Internal or external to application interfacing error,
Incorrect handling of passing parameters, Incorrect alignment,
incorrect/misplaced fields/objects, un friendly window/screen positions
Logic Error: Missing or Inadequate or irrelevant or ambiguous functionality
in source code
