Scribd
Upload
31 views31 pages

Software Quality

This document discusses the evolution of approaches to software quality, from initial product inspection to modern quality systems. It describes key stages including quality control, quality assurance, total quality management, and business process reengineering. The goal has shifted from assuring quality of final products to assuring quality through continuous improvement and optimization of the development process.

Uploaded by

krishnapmurali2000
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
31 views31 pages

Software Quality

This document discusses the evolution of approaches to software quality, from initial product inspection to modern quality systems. It describes key stages including quality control, quality assurance, total quality management, and business process reengineering. The goal has shifted from assuring quality of final products to assuring quality through continuous improvement and optimization of the development process.

Uploaded by

krishnapmurali2000
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 31

Software Quality

1
Organization of this Lecture:

• Introduction Quality Engineering.


• Quality control and Quality Assurance

2
Introduction

• Traditional definition of quality:


–fitness of purpose,
• a quality product does exactly what
the users want it to do.

3
Fitness of purpose

• For software products,


–fitness of purpose:
• satisfaction of the requirements
specified in SRS document.

4
Fitness of purpose

• A satisfactory definition of quality


for many products:
–a car, a table fan, a food mixer,
microwave oven, etc.
• But, not satisfactory for software
products.
5
Introduction
• Consider a software product:
–functionally correct,
• i.e. performs all functions as
specified in the SRS document,
–but has an almost unusable user
interface.
• cannot be considered as a quality
product. 6
Introduction

• Another example:
–a product which does everything
that users want.
–but has an almost
incomprehensible and
unmaintainable code.
7
Modern view of quality

• Associates several quality factors with a


software product :
– Correctness
– Reliability
– Efficiency (includes efficiency of resource utilization)
– Portability
– Usability
– Reusability
– Maintainability
8
Correctness

• A software product is correct,


–if different requirements as
specified in the SRS document
have been correctly
implemented.
–Accuracy of results.
9
Portability

• A software product is said to be


portable,
–if it can be easily made to work in
different operating systems,
–in different machines,
–with other software products, etc.

10
Reusability

• A software product has good


reusability,
–if different modules of the
product can easily be reused to
develop new products.

11
Usability

• A software product has good


usability,
–if different categories of users (i.e.
both expert and novice users) can
easily invoke the functions of the
product.

12
Maintainability

• A software product is maintainable,


– if errors can be easily corrected as and
when they show up,
– new functions can be easily added to the
product,
– functionalities of the product can be
easily modified, etc.

13
Software Quality Management
System

• Quality management system (or


quality system):
–principal methodology used by
organizations to ensure that the
products have desired quality.

14
Quality system

• A quality system consists of the


following:
–Managerial Structure
–Individual Responsibilities.
• Responsibility of the organization
as a whole.
15
Quality system

• Every quality conscious organization has an


independent quality department:
– performs several quality system activities.
– needs support of top management.
– Without support at a high level in a company,
• many employees may not take the quality system
seriously.

16
Quality System Activities:
• Auditing of projects
• Development of:
– standards, procedures, and guidelines,
etc.
• Production of reports for the top
management
– summarizing the effectiveness of the
quality system in the organization.
• Review of the quality system itself.
17
Quality system

• A good quality system must be well


documented.
– Without a properly documented quality
system,
• application of quality procedures become ad
hoc,
• results in large variations in the quality of the
products delivered.

18
Quality system

• An undocumented quality system:


– sends clear messages to the staff about the
attitude of the organization towards quality
assurance.
• International standards such as ISO 9000
provide:
– guidance on how to organize a quality system.

19
Evolution of Quality Systems

• Quality systems have evolved:


–over the last five decades.
• Prior to World War II,
–way to produce quality products:
• inspect the finished products
• eliminate defective products.

20
Evolution of Quality Systems

• Since that time,


–quality systems of organizations
have undergone
• four stages of evolution.

21
Evolution of Quality Systems

22
Evolution of Quality Systems

• Initial product inspection method :


– gave way to quality control (QC).
• Quality control:
– not only detect the defective products
and eliminate them
– but also determine the causes behind the
defects.

23
Quality control (QC)

• Quality control aims at correcting the


causes of errors:
– not just rejecting defective products.
• Statistical quality control
– quality of the output of the process is
inferred using statistical methods
– in stead of inspection or testing of all
products
24
Quality control (QC)
• The next breakthrough,
–development of quality assurance
principles

25
Quality assurance

• Basic premise of modern quality


assurance:
–if an organization's processes are
good and are followed rigorously,
• the products are bound to be of good
quality.

26
Quality assurance

• All modern quality paradigms


include:
–guidance for recognizing, defining,
analyzing, and improving the
production process.

27
Total quality management (TQM)

• Advocates:
–continuous process
improvements through process
measurements.

28
Business Process reengineering

• A term related to TQM.


• Process reengineering goes a
step further than quality
assurance:
–aims at continuous process
improvement.
29
Business Process reengineering
 Our focus is reengineering of
the software process.
 Whereas BPR aims at reengineering
the way business is carried out in
any organization
 not just software development
organizations.
30
Total quality management (TQM)

• TQM goes beyond documenting


processes
– optimizes them through redesign.
• Over the years the quality paradigm
has shifted:
– from product assurance to process
assurance.
31

You might also like