Scribd
Upload
2 views

SEPM Module 5

Uploaded by

Geetha Shetty
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
2 views

SEPM Module 5

Uploaded by

Geetha Shetty
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/ 10

Software Quality

Module 5
• 13.1 Introduction
• While quality is generally agreed to be ‘a good thing’, in practice what
is meant by the ‘quality’ of a system can be vague. We need to define
precisely what qualities we require of a system.
• However, we need to go further - we need to judge objectively
whether a system meets our quality requirements and this needs
measurements.

• 13.2 The Place of Software Quality in Project Planning


• Quality will be of concerns at all stages of project planning (13.1).
• 13.3 Importance of Software Quality
1. Increasing criticality of software: The final customer or user is naturally anxious
about the general quality of software, especially its reliability. This is increasingly
so as organizations rely more on their computer system and software is used in
more safety-critical application, for example to control aircraft.
2. The intangibility of software: It can make it difficult to know that a project task
was completed satisfactorily. Task outcomes can be made tangible by demanding
that the developer procedure ‘deliverables’ that can be examined for quality.
3. Accumulation error during software development: As computer system
development comprises steps where the output from one step is the input to the
next, the error in the later deliverables will be added to those in the earlier steps,
leading to an accumulating detrimental effect. In general, the later in a project
that an error is found the more expensive it will be to fix.
• For these reasons quality management is an essential part of project management.
• 13.4 Defining Software Quality
• A system will have functional, quality and resource requirements. Functional
requirements define what system is to do., the resource requirements specify
allowable costs and quality requirements state how well this system is to operate.
• Some qualities of a software product reflect the external view of the software held
by users, as in case of usability. These external qualities have to be mapped to
internal factors of which the developers would be aware.
• Defining quality is not enough. If we are to judge whether system meets our
requirements we need to be able to measure its quality.
• When there is concern about the need for a specific quality characteristic in a
software product then a quality specification with following minimum details
should be drafted: Definition/description, Scale, Test, Minimally acceptable, Target
range, and Now.
• Several measurements applicable to a quality characteristic like reliability:
Availability, Mean time between failures, Failure on demand, and Support activity.
• 13.5 Software Quality Models
• It is hard to directly measure the quality of the software. However, it can be
expressed in terms of several attributes of a software that can be directly measure.
• The quality models give a characterization of software quality in terms of a set of
characteristics of the software. The bottom level of the hierarchy can be directly
measured, thereby, enabling a quantitative assessment of quality of the software.
• Several established quality models includes, McCall’s, Dromey’s and Boehm’s.
• One standard which was developed was ISO 9126.
• Garvin’s quality dimensions: Performance, Features, Reliability, Conformance,
Durability, Serviceability, Aesthetics, and Perceived quality.
• 13.5 Software Quality Models
• McCall’s model: Three parameters: Operational characteristics, how easy is to fix
defects and how easy it is to fix defects, and how easy it to port it to different
platform.
• Eleven Attributes: Correctness, Reliability, Efficiency, Integrity, Usability,
Maintainability, Flexibility, Testability, Portability, Reusability, Interoperability.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy