unit 1 various software testing description

UNIT I – INTRODUCTION
-
OriginsofDefects–Costofdefects
UNIT I – INTRODUCTION
-
OriginsofDefects–Costofdefects
1 of 9
IT8076 - SOFTWARE TESTING
2 February 2020

DEFECT CLASSES
• Defect can be classified in many ways.
• Defects are assigned to four major classes reflecting their
point of origin in the software life cycle.
• These classes are:-
– Requirements / Specification Defect Classes
– Design Defect Classes
– Code Defect Classes
– Testing Defect Classes
• Defect can be classified in many ways.
• Defects are assigned to four major classes reflecting their
point of origin in the software life cycle.
• These classes are:-
– Requirements / Specification Defect Classes
– Design Defect Classes
– Code Defect Classes
– Testing Defect Classes
2 February 2020 IT8076 - SOFTWARE TESTING 2 of 9

Requirements and Specification
Defects
• Functional Description Defects: The overall description of
what the product does, and how it should behave.
• Feature Defects: Features may be described as distinguishing
characteristics of a software component or system.
– Features refers to functional aspects of software that map to
functional requirement described by the user and the client, it also
maps quality such as performance and reliability.
– Feature defects are mainly due to features description that are
missing, incorrect, incomplete.
• Functional Description Defects: The overall description of
what the product does, and how it should behave.
• Feature Defects: Features may be described as distinguishing
characteristics of a software component or system.
– Features refers to functional aspects of software that map to
functional requirement described by the user and the client, it also
maps quality such as performance and reliability.
– Feature defects are mainly due to features description that are
missing, incorrect, incomplete.

3.Feature Interaction Defects:
These are due to an incorrect description of how the
features should interact. For example, suppose one feature of
a software system supports adding a new customer to a
customer database.
4.Interface Description Defects
These are defects that occur in the description of how the
target software is to interface with external software,
hardware, and users. For detecting many functional description
defects, black box testing techniques, which are based on
functional specifications of the software, offer the best
approach.
Requirements and Specification
Defects
3.Feature Interaction Defects:
These are due to an incorrect description of how the
features should interact. For example, suppose one feature of
a software system supports adding a new customer to a
customer database.
4.Interface Description Defects
These are defects that occur in the description of how the
target software is to interface with external software,
hardware, and users. For detecting many functional description
defects, black box testing techniques, which are based on
functional specifications of the software, offer the best
approach.

– Design defects occur when system components, interactions between
system components, interactions between the components and outside
software/hardware, or users are incorrectly designed. This covers
defects in the design of algorithms, control, logic, data elements,
module interface descriptions, and external software/hardware/user
interface descriptions.
– When describing these defects we assume that the detailed design
description for the software modules is at the pseudo code level with
processing steps, data structures, input/output parameters, and major
control structures defined. If module design is not described in such
detail then many of the defects types described here may be moved into
the coding defects class.
Design Defects
– Design defects occur when system components, interactions between
system components, interactions between the components and outside
software/hardware, or users are incorrectly designed. This covers
defects in the design of algorithms, control, logic, data elements,
module interface descriptions, and external software/hardware/user
interface descriptions.
– When describing these defects we assume that the detailed design
description for the software modules is at the pseudo code level with
processing steps, data structures, input/output parameters, and major
control structures defined. If module design is not described in such
detail then many of the defects types described here may be moved into
the coding defects class.

1.Algorithmic and Processing Defects
These occur when the processing steps in the algorithm as
described by the pseudo code are incorrect. For example, the pseudo code
may contain a calculation that is incorrectly specified, or the processing
steps in the algorithm written in the pseudo code language may not be in
the correct order. In the latter case a step may be missing or a step may be
duplicated. Another example of a defect in this subclass is the omission of
error condition checks such as division by zero. In the case of algorithm
reuse, a designer may have selected an inappropriate algorithm for this
problem.
Design Defects
1.Algorithmic and Processing Defects
These occur when the processing steps in the algorithm as
described by the pseudo code are incorrect. For example, the pseudo code
may contain a calculation that is incorrectly specified, or the processing
steps in the algorithm written in the pseudo code language may not be in
the correct order. In the latter case a step may be missing or a step may be
duplicated. Another example of a defect in this subclass is the omission of
error condition checks such as division by zero. In the case of algorithm
reuse, a designer may have selected an inappropriate algorithm for this
problem.
2 February 2020 7 of 9

2.Control, Logic, and Sequence Defects
Control defects occur when logic flow in the pseudo code is not correct. For
example, branching to soon, branching to late, or use of an incorrect branching
condition. Other examples in this subclass are unreachable pseudo code
elements, improper nesting, improper procedure or function calls. Logic
defects usually relate to incorrect use of logic operators, such as less than ( ),
greater than ( ), etc. These may be used incorrectly in a Boolean expression
controlling a branching instruction.
3.Data Defects
These are associated with incorrect design of data structures. For example, a
record may be lacking a field, an incorrect type is assigned to a variable or a
field in a record, an array may not have the proper number of elements
assigned, or storage space may be allocated incorrectly. Software reviews and
use of a data dictionary work well to reveal these types of defects.
Design Defects
2.Control, Logic, and Sequence Defects
Control defects occur when logic flow in the pseudo code is not correct. For
example, branching to soon, branching to late, or use of an incorrect branching
condition. Other examples in this subclass are unreachable pseudo code
elements, improper nesting, improper procedure or function calls. Logic
defects usually relate to incorrect use of logic operators, such as less than ( ),
greater than ( ), etc. These may be used incorrectly in a Boolean expression
controlling a branching instruction.
3.Data Defects
These are associated with incorrect design of data structures. For example, a
record may be lacking a field, an incorrect type is assigned to a variable or a
field in a record, an array may not have the proper number of elements
assigned, or storage space may be allocated incorrectly. Software reviews and
use of a data dictionary work well to reveal these types of defects.

4.Module Interface Description Defects
These are defects derived from, for example, using incorrect, and/or in-
consistent parameter types, an incorrect number of parameters, or an incorrect
ordering of parameters.
5.Functional Description Defects
The defects in this category include incorrect, missing, and/or unclear design
elements. For example, the design may not properly describe the correct
functionality of a module. These defects are best detected during a design
review.
6.External Interface Description Defects
These are derived from incorrect design descriptions for interfaces with COTS
components, external software systems, databases, and hardware devices (e.g.,
I/O devices). Other examples are user interface description defects where there
are missing or improper commands, improper sequences of commands, lack of
proper messages, and/or lack of feedback messages for the user.
Design Defects
4.Module Interface Description Defects
These are defects derived from, for example, using incorrect, and/or in-
consistent parameter types, an incorrect number of parameters, or an incorrect
ordering of parameters.
5.Functional Description Defects
The defects in this category include incorrect, missing, and/or unclear design
elements. For example, the design may not properly describe the correct
functionality of a module. These defects are best detected during a design
review.
6.External Interface Description Defects
These are derived from incorrect design descriptions for interfaces with COTS
components, external software systems, databases, and hardware devices (e.g.,
I/O devices). Other examples are user interface description defects where there
are missing or improper commands, improper sequences of commands, lack of
proper messages, and/or lack of feedback messages for the user.

unit 1 various software testing description

Recommended

More Related Content

Similar to unit 1 various software testing description (20)

Recently uploaded (20)

unit 1 various software testing description