How to measure quality of software product

Objectives
Provide status on a new Software Product Quality
Measurement standard and its connection to CMMI
Provide ideas on how to get started with Software Product
Quality Measurement today

Outline
Background and Overview
Concepts and Models
Software Product Quality Measurement
Summary

Achieving Quality Software
Requires planning and intentional design
More than achieving the desired functionality
Must explicitly attend to both functional and non-functional
requirements
Need to verify all requirements are being met throughout
the life cycle

CMMI Definition for Quality Requirements
The phrase “quality and process-performance
objectives” covers objectives and requirements for
product quality, service quality, and process
performance. Process performance objectives include
product quality.

Requirements Development
This process area describes three types of requirements:
• customer requirements (quality in use)
• product requirements (external quality attributes)
• product-component requirements (internal quality
attributes)
Taken together, these requirements address the needs of
relevant stakeholders, including those pertinent to various
product life-cycle phases (e.g., acceptance testing criteria)
and product attributes (e.g., safety, reliability,
maintainability).
Requirements also address constraints caused by the
selection of design solutions (e.g., integration of
commercial off-the-shelf products).

Requirements Development Goals
SG 1 Develop Customer Requirements
Stakeholder needs, expectations, constraints,
and interfaces are collected and translated into
customer requirements.
SG 2 Develop Product Requirements
Customer requirements are refined and
elaborated to develop product and productcomponent
requirements.
SG 3 Analyze and Validate Requirements
The requirements are analyzed and validated,
and a definition of required functionality is
developed.

Process Management and Performance
The organization’s process needs and objectives
cover aspects that include the following:
• characteristics of the processes
• process performance objectives, such as time to
market and product quality
• process effectiveness
A quantitatively managed process is institutionalized
by doing the following:
• controlling the process using statistical and other
quantitative techniques such that product quality,
service quality, and process performance attributes

Key Points in Relationship of CMMI
and ISO 9126/25000
CMMI takes a total life cycle view and is inclusive in its
approach to requirements development.
Requirements development explicitly seeks to have
the developer consider quality requirements.
Project and Process Management processes explicitly
consider product quality as process performance
objectives.
Neither the standard nor CMMI endorses a unidimensional
view of quality.

Product Quality Requirements are transformed into
designs and implemented via the Technical Solution
and Product Integration process areas.
The implementation of Product Quality Requirements
are monitored and confirmed via the Project
Management, Verification, and Validation process
areas.
CMMI acknowledges the need for interaction and
perhaps iteration among the related process areas to
satisfactorily identify, specify, and address Product
Quality Requirements.
are measurable and controlled throughout the
project (internal and external quality measures and
criteria)

Relating Requirements, Evaluation,
and Measurement


Reference: http://www.sei.cmu.edu/sema/presentations/esepg.pdf