Software Quality Assurance

Noman Hafeez

1
 Software Quality Models

 Mc Call’s Model
 Boehm’s Model
 Dromey’s Quality Model
 FURPS Model
 SATC’s Model
 ISO 9126 Quality Model
 Capability Maturity Model
2
 Why Quality Models?

 With the growing number of customer's

demand for software systems, the
expectations for quality has also grown
in terms of how reliable a software
product will be.
 A good quality product leads to
customer satisfaction and signifies an
overall success of a project.
3
 Why Quality Models?

 Lotof effort is invested in the

process quality improvement. When
a project is undertaken, the aim is
to deliver the right product at the
right time with the right
functionalities.

4
 Goal of Quality Model

 The overall goal of any software

management is
 "Quality built-in with cost and
performance as prime
consideration".
 The software should be built with
certain quality aspects that fulfill the
needs of the user. Its performance is
kept on the top priority.
5
 McCall’s Model (1977)

 JimMcCall produced the McCall

software quality model for the US Air
Force in 1977. This is used to maintain
harmony between the users and the
developers. Successful software is
developed that fulfills the user needs
in consideration with the developer's
point of view.
6
 Perspectives of Quality
Attributes

A perspective is required for every

approach. Be it, software niche or
any other niche.
Product Revision.
Product Transition.
Product Operations.
7
 Product Revision

 Itencompasses the revision

perspective identifiers quality
factors that changes or enhances
the ability to change the software
product in the future according
to the needs and requirements of
the user.
8
 Product Revision

 Itencompasses the revision

perspective identifiers quality
factors that changes or enhances
the ability to change the software
product in the future according
to the needs and requirements of
the user.
9
 Product Revision

 Quality
Factors involved in
Product Revision
 Maintainability
Flexibility
Testability

10
 Product Revision

 Maintainability
 If there are defects in the software that
are found in the later stage, this feature
allows finding and fixing the defects.
 Flexibility
 The ability to make changes in the software
product according to the business demands.
 Testability
 This enables the software product to
validate the
11
 Product Transition

 Transitionperspective enables
the software to adapt itself in
new environments.
 The identification of the quality
factor which enables the ability
of adaption of the software in the
new environment is known as
product transition.
12
 Product Transition

 Quality
Factors involved in
Product transition:
Portability
Reusability
Interoperability Quality Factors
involved in
13
 Product Transition

 Portability
 This is the ability to transfer a software from
one environment to another environment.
 Re-usability
 The software components can be used in
different contexts.
 Interoperability
 The ease or the comfort zone in which all the
components of the software works together.

14
 Product Operations

 The software can run successfully

in the market if it according to the
specifications of the user and also
it should run smoothly without any
defects. The product operation
perspective influences the extent
to which the software fulfills its
specifications
15
 Product Operations

 Quality
Factors involved in Product
Operations are:
 Correctness
 Reliability
 Efficiency
 Usability

16
 Product Operations

 Correctness
 The functionality should match the specification.
 Reliability
 The extent to which the system fails.
 Efficiency
 It enhances the usage of system resource.
 Usability
 The software should be easy to use. Difficult
software is tedious to work upon and difficulty
irks the user.

17
 McCall Model

 Thisis all about McCall software

quality model. This created a
revolution in the software industry
with its quality to provide the
required ability to the software.

18
 Boehm’s Model (1978)

 Boehm software quality model was

introduced in the year of 1978.
 The model is used to represent a
hierarchical model that structures
around high level characteristics,
intermediate level characteristics,
and primitive characteristics.
 All of these together results in to
establishment of a high quality
software model.
19
 Boehm’s Model (1978)

 Themodel defines the quality of

software on the basis of a set of
credentials and measurements.

20
 Boehm’s Model (1978)

 Hierarchy of Boehm Model:

 High Level Characteristics
 Intermediate Level Characteristics
 Primitive Characteristics

21
 High Level Characteristics

 As-Is Utility
 It defines the way a utility signifies the as-is
utility. It creates a question of how easily,
reliably and efficiently an as can be utilized.
 Maintainability
 This aspect decides how convenient it is to
understand, change or re-evaluate a process.
 Portability
 This aspect helps in deciding an effective way
to change an environment.

22
 Intermediate Level
Characteristics

 These include:
 Flexibility
 Reliability
 Portability
 Efficiency
 Testability
 Understandability
 Usability
23
 Intermediate Level
Characteristics

 Flexibility: It is very easy to amend the

software as per the requirement.
Parameters of the software should be so
flexible that they can react on numerous
situations.
 Reliability: Software performance should
be reliable with zero defects. Result
should be accurate.
 Portability: Software can run on different
computer' program example DOS,
windows.
24
 Intermediate Level
Characteristics

 Efficiency: Practical & efficient use of

resources or data collected. Optimum
utilization of resources should be made.
 Testability: Software should be tested
easily and as a result users can easily
check that the results are correct, so
that they can rely on result blindly.

25
 Intermediate Level
Characteristics

 Understandability: Software should be

simple to understand for users so that
they can use it properly and efficiently.
 Usability: Users can apply it easily and
comfortably.

26
 Primitive Characteristics

 The factors can result into creation of other measurable

properties. These are as follows:
 Accuracy.
 Completeness.
 Robustness.
 Consistency
 Device efficiency
 Accessibility
 Communicativeness
 Self-descriptiveness
 Legibility
27
 Boehm Model

 The Boehm Model is based on McCall

model and was created after doing
improvements in McCall software
quality model encountered few errors
in it. This new model of Boehm was
found to be more interesting as it is
placed in hierarchical order.

28
Comparative study of McCall
and Boehm

29
Comparative study of McCall
and Boehm

30
 Dromey’s Model (1995)

 Dromey proposed a quality evaluation framework that

analyzes the quality of software component through the
measurement of tangible quality properties.

31
 Dromey’s Model

 Key Points:
 This model emphasis on evaluating one software's quality
with another.
 It helps to find out defects if any, and also to point out the
factors that caused such defects.
 This model is designed on the basis of the relationship that
exist between software properties and its quality
attributes.

32
 Dromey’s Model

 All above software possess properties can be classified

into four categories:
 Correctness:
 Evaluates software whether some basic principles are
violated.
 Internal:
 Measure how well software has been deployed according
to its intended use.

33
 Dromey’s Model

 Contextual:
 Deals with the external influences by and on the use of
software.
 Descriptive:
 Measures the descriptiveness of software. These properties
are used to evaluate the quality of the software. It is
difficult to see how it could be used at the beginning of
the lifecycle to determine user quality needs.

34
 FURPS Model

 FURPS is a technique to validate the

prioritized requirements after an
understanding with client's needs and
necessities. FURPS model originally
presented by Robert Grady.

35
 FURPS Model

 FURPS stands for :

 Functionality

 Usability
 Reliability
 Performance
 Supportability.

36
 FURPS Model

 Functionality
 The capability of the software product
to provide functions which meet stated
and implied needs when the software is
used under specified conditions.

37
 FURPS Model - Functionality

 Functionality contains the following sub

quality factors:
 Suitability
 Accuracy
 Security
 Interoperability
 Functionality Compliances

38
 FURPS Model - Functionality

Suitability

“The capability of the software product

to provide an appropriate set of functions
for specified tasks and user objectives”.

39
 FURPS Model - Functionality

Accuracy:
 The capability of the software product to
provide the right or agreed results or effects
with the needed degree of precision”.

Security:
 The capability of the software product to
protect information and data so that
unauthorized persons or systems cannot read
or modify them and authorized persons or
systems are not denied access to them”.
40
 FURPS Model - Functionality

Interoperability:
 The capability of the software product to
interact with one or more specified
systems.

Functionality Compliance:
 The capability of the software product to
adhere to standards, conventions or
regulations in laws and similar
prescriptions relating to functionality.
41
 FURPS Model - Usability

Usability:

 The capability of the software product

to be understood, learned, used, and
attractive to the user, when used under
specified conditions.

42
 FURPS Model - Usability

Usability includes:
 Understandability
 Learnability
 Operability
 Attractiveness
 Usability Compliance

43
 FURPS Model - Usability

Understandability:
 The capability of the software product to
enable the user to understand whether the
software is suitable, and how it can be
used for particular tasks and conditions of
use.

Learnability:
 The capability of the software product to
enable the user to learn its application.
44
 FURPS Model - Usability

Operability:
 The capability of the software product
to enable the user to operate and
control it

Attractiveness:
 The capability of the software product
to be attractive to the user.

45
 FURPS Model - Usability

Usability Compliance:
 The capability of the software product
to adhere to standards, conventions,
style guides or regulations relating to
usability.

46
 FURPS Model - Performance

Performance:
 It imposes conditions on functional
requirements such as speed, efficiency,
availability, accuracy, throughput,
response time, recovery time, and
resource usage.

47
 FURPS Model - Supportability

Supportability:
 It may include testability, extensibility,
adaptability, maintainability,
compatibility, configurability,
serviceability, installability,
localizability (internationalization).

48