JAYAWANT SHIKSHAN PRASARAK MANDAL’s

Bhivrabai Sawant Polytechnic

(Approved by AICTE, New Delhi, Govt. of Maharashtra, Affiliated to MSBTE Mumbai)
Gat No. 720 (1&2), Wagholi, Pune-Nagar Road, Pune-412207)
Phone: 020 – 65335100 Tele fax: - + 91-020-65335100
E-mail: [email protected] Website: www.jspm.edu.in
(Academic Year 2023-24)

Unit IV (PIP) Solution

Course: - Software Testing Course Code : 22518

Que. Bloom’s Relevance

No. Level to
CO
1 1,2 Which are different causes of software defect?

Marking Scheme (2M)

Answer Defect: A defect is an error or a bug, in the application which is created. A programmer while COI504.4
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.

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

2 1,2 Explain Defect Classification. COI504.4

Marking Scheme (2M)

Answer

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
 Data base Error: Error in the database schema/Design
 Missing Design: Design features/approach missed/not documented in the design

Status Wise:
 Open
 Closed
 Deferred
 Cancelled

3 1,2 Describe steps in Defect Management Process COI504.4

Marking Scheme (2M)
Answer Defect Prevention - Implementation of techniques, methodology and standard processes to reduce the risk
of defects.
Deliverable Baseline - Establishment of milestones where deliverables will be considered complete and
ready for further development work.

Defect Discovery - Identification and reporting of defects for development team acknowledgment. A defect is
only termed discovered when it has been documented and acknowledged as a valid defect by the development
team member(s) responsible for the component(s) in error.
Defect Resolution -- Work by the development team to prioritize, schedule and fix a defect, and document
the resolution. This also includes notification back to the tester to ensure that the resolution is verified.

Process Improvement -- defects Identification and analysis of the process in which a

defect originated to identify ways to improve the process to prevent future occurrences
of similar.
Management Reporting -- Analysis and reporting of defect information to assist management with risk
management, process improvement and project management.
 4 1,2 COI504.4
Draw the diagram of Defect I Bug life cycle and explain its process.

Marking Scheme (4M)

Answer

New: When the bug is posted for the first time,

its state will be “NEW”. This means
that the bug is not yet approved.
 Open: After a tester has posted a bug, the lead of the tester approves that the bug is
genuine and he changes the state as “OPEN”.
 Assign: Once the lead changes the state as “OPEN”, he assigns the bug
corresponding developer or developer team. The state of the bug now is changed to “ASSIGN”.

 Test/Retest: Once the developer fixes the bug, he has to assign the bug to the testing
team for next round of testing. Before he releases the software with bug fixed, he
changes the state of bug to “TEST”. It specifies that the bug has been fixed and is
released to testing team.// At this stage the tester do the retesting of the changed code
which developer has given to him to check whether the defect got fixed or not.
 Deferred: The bug, changed to deferred state means the bug is expected to be fixed in
next releases. The reasons for changing the bug to this state have many factors. Some
of them are priority of the bug may be low, lack of time for the release or the bug may
not have major effect on the software.
 Rejected: If the developer feels that the bug is not genuine, he rejects the bug. Then
the state of the bug is changed to “REJECTED”.
 Verified: Once the bug is fixed and the status is changed to “TEST”, the tester tests
the bug. If the bug is not present in the software, he approves that the bug is fixed and
changes the status to “VERIFIED”.
  Reopened: If the bug still exists even after the bug is fixed by the developer, the
tester changes the status to “REOPENED”. The bug traverses the life cycle once
again.
 Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug
no longer exists in the software, he changes the status of the bug to “CLOSED”.

5 1,2 Explain defect management process with proper diagram. COI504.4

Marking Scheme (4M)

Answer

Defect Prevention - Implementation of techniques, methodology and standard processes to reduce the risk
of defects.
Deliverable Baseline - Establishment of milestones where deliverables will be considered complete and
ready for further development work. When a deliverable is baseline, any further changes are controlled. Errors
in a deliverable are not considered defects until after the deliverable is baseline.
Defect Discovery - Identification and reporting of defects for development team acknowledgment. A defect
is only termed discovered when it has been documented and acknowledged as a valid defect by the
development team member(s) responsible for the component(s) in error.
Defect Resolution -- Work by the development team to prioritize, schedule and fix a defect, and document
the resolution. This also includes notification back to the tester to ensure that the resolution is verified.

Process Improvement -- Identification and analysis of the process in which a defect

originated to identify ways to improve the process to prevent future occurrences of
similar defects. Also the validation process that should have identified the defect earlier is
analyzed to determine ways to strengthen that process.
Management Reporting -- Analysis and reporting of defect information to assist management with risk
management, process improvement and project management.
 6 1,2 COI504.4
Give the defect classification and its meaning.
Marking Scheme (2M)
Requirement/Specification Defects:
Requirement-related defects arise in a product when one fails to understand what the
customer requires.
These defects may be due to the customer gap, where the customer is unable to define his
requirements.
Answer Producer gap, where the developing team is not able to make a product as per requirements.
Design Defects:
Design defects occur when system components, interactions between system components,
interactions between the outside software/hardware, or users are incorrectly designed.
Design defects generally refer to the way of design creation or its usage while creating a
product.
Coding Defects:
This defect arises when variables are not initialized properly or variables are not declared
correctly or database is not created properly.
Coding also needs adequate commenting to make it readable and maintainable in future.
Testing Defects:
These would encompass incorrect, incomplete, missing inappropriate test cases and test
procedures.
½ M for each
classification
and meaning
7 1,2 Prepare defect report after executing test cases for any login form. COI504.4
Marking Scheme (4M)
Answer Defect Report in Software Testing is a detailed document about bugs found in the software

application

Following is Defect report after executing test cases for Email-log in form.

ID number #123

Name loginform - Unable to login Email

Reporter Person’s name (xyz)

Submit Date 03/01/2023

Summary When I put my mail id and password, I am unable to

login while login credentials are right.

URL www.gmail.com

Screenshot https://accounts.google.com/signin/

Platform AngularJS

Operating System OS X 10.12.0

Browser Chrome 53

Severity Major

Assigned to /

Priority High

Description

When I put mail id and password, I am unable to login while login credentials are right.

Steps to reproduce

> go to the www.gmail.com

> Click on login button

> Put Right mail id and password and click next.

> and take Screenshot.

Expected result

The mail account should logged in after putting the right mail id and password.

Actual result
 The mail account is not logging in after putting the right details

8 Prepare defect report after executing test cases for withdrawn of amount from ATM COI504.4
1,2
machine
Marking Scheme (4M)
Answer ID R1

Project Cash Simulator Cash (ATM)

Product http://www.motc.gov.qa/en/ditoolkit/migrantworkers/cash

-machine-simulator-atm

Release Version: v1.0

Module Home Page> Our Programs > Digital Inclusion tools

Detected Build Version: V1.1

Summary Limited denomination options in cash withdrawal

function, restricting cash withdrawal only till 3000

Description No option of withdrawing of amount excess of 3000.

Steps to Replicate

1. Open the website

2. Select our programs

3. Proceed to Digital Inclusion tools and select cash

machine simulator (ATM)

4. Select language and skip to simulator

5. Enter the card

 6. Select the account type

7. Go to Other functions and select cash withdrawal

Expected

Results

It should add more options in denominations in

withdrawal function or it should take amount input from

the user.

Actual Results It is displaying limited options of denominations in cash

withdrawal option.

Attachments

Remarks Causes inconvenience to the user in terms of limited cash

withdrawal options.

Defect Severity: High

Defect Priority: High

Reported By Test Engineer1

Assigned To XYZ

Status Assigned

9 1,2 What do you mean ‘Defect Impact’? Explain how to estimate the defect impact. COI504.4

Marking Scheme 4M
Answer Defect Impact: The degree of severity that a defect has on the development or operation of a component or
system.
How to Estimate the defect impact

Once the critical risks are identified, the financial impact of each risk should be estimated.
This can be done by assessing the impact, in dollars, if the risk does become a problem
combined with the probability that the risk will become a problem. The product of these
two numbers is the expected impact of the risk. The expected impact of a risk (E) is
calculated as E = P * I, where: P= probability of the risk becoming a problem and

I= Impact in dollars if the risk becomes a problem.Once the expected impact of each risk
is identified, the risks should be prioritized by the expected impact and the degree to
which the expected impact can be reduced. While guess work will constitute a major role
in producing these numbers, precision is not important. What will be important is to
identify the risk, and determine the risk's order of magnitude.

Large, complex systems will have many critical risks. Whatever can be done to reduce the
probability of each individual critical risk becoming a problem to a very small number
should be done. Doing this increases the probability of a successful project by increasing
the probability that none of the critical risks will become a problem.One should assume
that an individual critical risk has a low probability of becoming a problem only when
there is specific knowledge justifying why it is low. For example, the likelihood that an
important requirement was missed may be high if developers have not involved users in
the project. If users have actively participated in the requirements definition, and the new
system is not a radical departure from an existing system or process, the likelihood may
be low.

For example:

An organization with a project of 2,500 functions points and was about medium at defect
discovery and removal would have 1,650 defects remaining after all defect removal and
discovery activities.

The calculation is 2,500 x 1.2 = 3,000 potential defects.

 The organization would be able to remove about 45% of the defects or 1,350 defects.
The total potential defects (3,000) less the removed defects (1,350) equals the remaining defects
of1,650.

Subject Teacher Module Coordinator H.O.D.