Software Quality Engineering

CT051-3.5-3

Software Quality Assurance Plan

Software Engineering

Prepared by: xxx First Prepared on: xx-xx-xx Last Modified on: xx-xx-xx
Quality checked by: xxx
Copyright 2004 Asia Pacific Institute of Information Technology
Topic & Structure of the lesson

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1

 Learning Outcomes

By the end of this lecture, YOU should be

able to :
• Explain what is software quality
assurance
• Justify the importance of Software
Quality Assurance Plan (SQAP)
• Create a Software Quality Assurance
Plan

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1

Key Terms you must be able to use

If you have mastered this topic, you should

be able to use the following terms correctly
in your assignments and exams:
• Software Quality Assurance Plan

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1

 SQA Definition

• IEEE definition
• Quality assurance is
• A planed and systematic pattern of all actions
necessary to provide adequate confidence that an
item or product conforms to established technical
requirements.
• A set of activities designed to evaluate the process by
which the products are developed or manufactured.

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1

 The Uniqueness of SQA

• High complexity
• Invisibility of software
• Nature of the product development
• Production process
– Need for SQA methodologies and tools

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1

Why do we care about Quality?

Development cost Correction cost & source

– Specification : 6% – Specification : 56%
– Design : 5% – Design : 24%
– Coding : 7% – Coding : 10%
– V&V (Testing) : 15% – Others : 10%
– Maintenance : 67%

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1

 Importance of SQAP

 Communication

 Describes the review and audit activities

 Everyone knows and understands the plan

 Roles and responsibilities are clear

 Monitor the process and detect inadequacies

 Settle disputes and manages risks

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1

 Quality Assurance Plan

• The plan for quality assurance activities

should be in writing
• Decide if a separate group should perform
the quality assurance activities
• Some elements that should be considered
by the plan are: defect tracking, unit
testing, source-code tracking, technical
reviews, integration testing and system
testing.

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1

 Quality Assurance Plan

• Defect tracing – keeps track of each defect found, its

source, when it was detected, when it was resolved, how
it was resolved, etc
• Unit testing – each individual module is tested
• Source code tracing – step through source code line by
line
• Technical reviews – completed work is reviewed by
peers
• Integration testing -- exercise new code in combination
with code that already has been integrated
• System testing – execution of the software for the
purpose of finding defects.

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1

 SQA Plan – 1

• Management section
– describes the place of SQA in the structure of the
organization
• Documentation section
– describes each work product produced as part of
the software process
• Standards, practices, and conventions
section
– lists all applicable standards/practices applied
during the software process and any metrics to be
collected as part of the software engineering work

11
CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1
 SQA Plan - 2

• Reviews and audits section

– provides an overview of the approach used
in the reviews and audits to be conducted
during the project
• Test section
– references the test plan and procedure
document and defines test record keeping
requirements

12
CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1
 SQA Plan - 3

• Problem reporting and corrective action

section
– defines procedures for reporting, tracking, and
resolving errors or defects, identifies
organizational responsibilities for these activities
• Other
– tools, SQA methods, change control, record
keeping, training, and risk management

13
CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1
 Quick Review Question

Question 1

Why SQAP is become the most important

document in software development
projects?

Question 2
Why it is said that developers and quality
assurance executives cannot get along?
CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1
 Tutorial 3

1. Identify TWO other definitions for SQA

2. How SQAP can be useful for:
a) Programmers
b) System Analyst
c) Testers
d) Project Manager

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1

Summary of Main Teaching Points

1. Definition SQA

2. Importance of SQAP

3. SQAP document

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1

 Question and Answer Session

Q&A

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1

 Next Session

1. Quality Standard

CT051-3-3 -Software Quality Engineering Requirement Analysis Part 1