Software Quality Engineering

Functional
Requirements
Software RE vs Software QE

Functional
Requirements
 Functional
requirements define
what system should
do.

 Define particular
behavior of the
system when
conditions are true.
Software RE vs Software QE

Functional
Requirements
 May be calculations,
technical details to
achieve desired
functionality.

 Functional
requirements are
captured using Use
Cases.
Software Quality Engineering

Template for
Functional
Requirements
Software RE vs Software QE
Software RE vs Software QE

Template for
Functional
Requirements
 Use cases serve as
basis as connector
between different
phases of SDLC
Software Quality Engineering

Example-I: Filled
Functional
Requirements
Software RE vs Software QE
Software RE vs Software QE
Software RE vs Software QE

Example – I: Filled
Functional
Requirement

 Use Case # is used to

make the
requirements
traceable
Software Quality Engineering

Example-II: Filled
Functional
Requirements
Software RE vs Software QE
Software RE vs Software QE
Software RE vs Software QE

Example – II: Filled

Functional
Requirement

 Use Case Templates

are used to generate
use case diagrams
Software Quality Engineering

Changing
Requirements
Software RE vs Software QE

Changing
Requirements
 Demoable software
leads to WishLists or
Change Requests
 Change Request
Templates is used as
appendix to manage
it.
 Functional
requirements as CR
Software RE vs Software QE

Changing
Requirements
 Functional
requirements as
Change request have
extra effort.
 Impact analysis is
performed and to be
communicated to
client
Software Quality Engineering

What is Software
Release
Software RE vs Software QE

What is Software
Release
 Product development
is achieved via
Release.
 Release includes set
of features,
environment variables
and backlog
 Features are divided
into doable releases
Software Quality Engineering

How Release is build

Software RE vs Software QE

How Release is build

 Features are provided
by Sales Team
 Environment Variable
majorly includes next
software version to be
compatiable with
product
 Environment variable
are provided by
technical team
Software RE vs Software QE

How Release is build

 Backlogs are
discussed and
finalized between
Sales and Technical
Team
 Each Release is a
Project
 Each Release have
tangible deadlines
Software Quality Engineering

Release Management
Software RE vs Software QE

Release Management
 Features are provided
by Sales Team
 Environment Variable
majorly includes next
software version to be
compatiable with
product
 Environment variable
are provided by
technical team
Software Quality Engineering

What are Release

Notes in General
Software RE vs Software QE
What are Release
Notes in General
 Release notes are part
of final build that
contain of scope of
particular release.

 Usually these are part

and parcel of
Software Products
Software RE vs Software QE
What are Release
Notes in General
 Release notes are part
of final build that
contain of scope of
particular release.
 Usually include
known-issues,
features-delivered
and performance
benchmarks
 QA is owner
Software Quality Engineering

What is Software
Quality Assurance
Software RE vs Software QE
What is Software
Quality Assurance
 SQA ensure that
software developed is
meeting the
requirements with
Quality
 SQA is on-going
process
 SQA is part of every
phase of SDLC
Software Quality Engineering

What is Software
Requirements vs
Software Quality
Assurance
Software RE vs Software QE
What is Software
Requirements vs
Software Quality
Assurance
 Requirements have to
be QA approved.

 Test cases are written

against Use Cases
 QA close Test case as
per Use Case
Software Quality Engineering

Verifying
Requirements
Software RE vs Software QE
Verifying Requirements
 Requirement
verifications are
formally , structurally
achieved thorough
Quality Assurance.

 Verification ensure a
planned and
documented
Procedure to identify
defects.
Software RE vs Software QE
Verifying Requirements

 Software Quality
Assurance is not
one-go process
Software Quality Engineering

People Expectation
from Quality
Engineering
Software RE vs Software QE
People Expectation
from Quality
Engineering
 Quality Engineering
should ensure
reliability and stable
product.

 In context of software
there should be no
bugs or defects.
Software RE vs Software QE
People Expectation
from Quality
Engineering
 Software with Zero-
bug count is
practically not
possible
 Expectation mismatch
open lead to financial
loss, clientage loss,
law suits.
Software Quality Engineering

Quality Assurance
Basics
 BG # 1Assurance
Software Quality
Quality Assurance
Basics
 Correctness centric
activities are the basis
of QA.
 Objective is to reduce
defects to minimum
to ensure minimum
disruption.
 High Priority areas
should be defect free.
Software Quality Engineering

QA and Defect
 BG # 1Assurance
Software Quality
QA and Defect

 QA and Defect are

always head-to-head.

 Different strategies
are adopted to ensure
minimum damage to
software system.

 Critical functionality
should work atleast.
 BG # 1Assurance
Software Quality
QA and Defect

 Defect should not

impact critical
working
Software Quality Engineering

QA and Defect:
Classification Scheme
 BG # 1Assurance
Software Quality
QA and Defect:
Classification Scheme

 Defects can be
classified into 3-
Categories.

 Defect Prevention
through Error Source
Removal.
 BG # 1Assurance
Software Quality
QA and Defect:
Classification Scheme

 Defect Detection
through fault
detection removal

 Defect Containment