Pressman, 7th Edition

COURSE CODE: CSE 319

COURSE TITLE: SOFTWARE ENGINEERING
CHAPTER: SOFTWARE QUALITY ASSURANCE
INSTRUCTOR: SANJIDA NASREEN TUMPA, LECTURER, DEPT OF CSE, MIST
 Quality Assurance
• Technical Review or Peer Review
• Testing

Technical Review or Peer Review

• A technical review (TR) is the most effective filter from a

quality control standpoint.

• Conducted by software engineers (and others) for

software engineers

• The TR is an effective means for uncovering errors and

improving software quality.
DIFFERENCE BETWEEN DEFECT, ERROR, BUG
DIFFERENCE BETWEEN DEFECT, ERROR, BUG,
FAILURE AND FAULT!

A mistake in coding is called Error, error found by tester is

called Defect, defect accepted by development team then it
is called Bug, build does not meet the requirements then it Is
Failure.

Bugs are found by the testers, defects can be found by the

end users
 DEFECT AMPLIFICATION AND REMOVAL-1

• A defect amplification model can be used to illustrate

the generation and detection of errors during the
design and code generation actions of a software
• process. The

Defect Amplification Model

DEFECT AMPLIFICATION AND REMOVAL-2

Defect Amplification – No reviews

DEFECT AMPLIFICATION AND REMOVAL-2

Defect Amplification – Reviews

conducted
 FTR and It’s Objectives
• A formal technical review (FTR) is a software quality control
activity performed by software engineers (and others).

• The objectives of an FTR are:

- to uncover errors in function, logic, or implementation for any
representation of the software;
- to verify that the software under review meets its
requirements;
- to ensure that the software has been represented according to
predefined standards;
- to achieve software that is developed in a uniform manner; and
 FTR and It’s Objectives
• A formal technical review (FTR) is a software quality control
activity performed by software engineers (and others).

• The objectives of an FTR are:

- to uncover errors in function, logic, or implementation for any
representation of the software;
- to verify that the software under review meets its
requirements;
- to ensure that the software has been represented according to
predefined standards;
- to achieve software that is developed in a uniform manner; and
- to make projects more manageable.
 Review Meeting
Regardless of the FTR format that is chosen, every review
meeting should abide by the following constraints:

• Between three and five people (typically) should be involved in

the review.

• Advance preparation should occur but should require no more

than two hours of work for each person.

• The duration of the review meeting should be less than two

hours.
 10 ELEMENTS OF SQA
Standards Education

Review And Vendor

Audits Management
Security
Testing
Management
Error/Defect
Collection And Safety
Analysis
Change Risk
Management Management
 10 ELEMENTS OF SQA

1. STANDARDS

• The IEEE, ISO, and other standards organizations

have produced a broad array of software engineering
standards and related documents.

• The job of SQA is to ensure that standards that have

been adopted are followed and that all work products
conform to them.
 10 ELEMENTS OF SQA

2. REVIEW AND
AUDITS

• Technical reviews are a quality control activity

performed by software engineers for software
engineers . Their intent is to uncover errors.

• Audits are a type of review performed by SQA

personnel with the intent of ensuring that quality
guidelines are being followed for software
engineering work.
 10 ELEMENTS OF SQA

3. TESTING

• Software testing is a quality control function that has

one primary goal - to find errors.

• The job of SQA is to ensure that testing is properly

planned and efficiently conducted so that it has the
highest likelihood of achieving its primary goal.
 10 ELEMENTS OF SQA

4. ERROR/DEFECT
COLLECTION AND
ANALYSIS

• SQA collects and analyzes error and defect data to

better understand how errors are introduced and what
software engineering activities are best suited to
eliminating them
 10 ELEMENTS OF SQA

5. CHANGE
MANAGEMENT

• If it is not properly managed, change can lead to

confusion, and confusion almost always leads to poor
quality.

• SQA ensures that adequate change management

practices have been instituted.
 10 ELEMENTS OF SQA

6. EDUCATION

• Education of software engineers, their managers, and

other stakeholders.

• The SQA organization takes the lead in software

process improvement and is a key proponent and
sponsor of educational programs.
 10 ELEMENTS OF SQA
7. VENDOR
MANAGEMENT
• Three categories of software are acquired from
external software vendors -
• Shrink-wrapped packages (e.g., Microsoft Office)
• Tailored shell that provides a basic skeletal
structure that is custom tailored to the needs of a
purchaser
• Contracted software that is custom designed and
constructed from specifications provided by the
customer organization..
 10 ELEMENTS OF SQA
7. VENDOR
MANAGEMENT
• Three categories of software are acquired from external software vendors -
• Shrink-wrapped packages
• Tailored shell
• Contracted software

• SQA organization ensures that high-quality software

results by suggesting specific quality practices that
the vendor should follow and incorporating quality
mandates as part of any contract with an external
vendor.
 10 ELEMENTS OF SQA

8. SECURITY
MANAGEMENT

• SQA ensures that appropriate process and technology

are used to achieve software security.
 10 ELEMENTS OF SQA

9. SAFETY

• The impact of hidden defects can be catastrophic

• SQA may be responsible for assessing the impact of

software failure and for initiating those steps required
to reduce risk.
 10 ELEMENTS OF SQA

10. RISK
MANAGEMENT

• SQA organization ensures that risk management

activities are properly conducted and that risk-related
contingency plans have been established.