METRICS FOR PROCESS AND PRODUCTS

Presented By: Sanjay Poudel

11
SOFTWARE QUALITY ASSURANCE
Software requirement forms a foundation for quality being measured. Lack of
conformance to requirements is lack of quality.
If specified standards, that define a set of development criteria, is not followed; lack
of quality will almost surely result.
If software conforms to its explicit requirements but fails to meet implicit
requirements (ease of use and maintainability), software quality is suspect.

11
SOFTWARE QUALITY MANAGEMENT
Concerned with ensuring that the required level of quality is achieved in a software
product
Involves defining appropriate quality standards and procedures and ensuring that
these are followed
Should aim to develop a ‘quality culture’ where quality is seen as everyone’s
responsibility

11
QUALITY MANAGEMENT ACTIVITIES
Quality assurance
Establish a framework of organizational procedures and standards for high-quality
Software.
Consists of the auditing and reporting procedures used to provide management with
data needed to make proactive decisions.
If data provided through QA identifies problems, management is responsible to
address the problems and apply the necessary resources to resolve quality issues.

11
QUALITY PLANNING
Selection of appropriate procedures and standards from this framework and
adaptation of these for specific software projects and modify these as required. A
quality plan sets out the desired product qualities and how these are assessed
and define the most significant quality attributes .
It should define the quality assessment process.
It should set out which organizational standards should be applied and, if necessary,
define new standards.

11
QUALITY CONTROL
Definition and enactment of processes which ensure that the project quality
procedures and standards are followed by the software development team.
Variation control is the heart of quality control (software engineers strive to control
the process applied, resources expended, and end product quality attributes).
QC involves the series of inspection, reviews, and test used throughout the software
process to ensure conformance of a work product to its specifications.
Feedback loop to the process that created the work product, minimize the defects
produced.
Key concept of QC- all work products have been defined, measurable specifications
to compare the output of each process.

11
COST OF QUALITY
Quality costs may be divided into costs associated with prevention, appraisal, and failure
as mentioned below:
Prevention costs - quality planning, formal technical reviews (FTR), test equipment, training.
Appraisal costs includes activities to gain insight into product condition the "first time
through" each process. Example include - in-process and inter-process inspection,
equipment
calibration and maintenance, testing.
Failure costs
Internal failure costs are incurred when a defect in a product is detected prior to
shipment and include - rework, repair, failure mode analysis
External failure costs are associated with defects found after the product has been
shipped to the customer which include- complaint resolution, product return and
replacement, help line support, warranty work

11
ISO QUALITY STANDARDS
International set of standards for quality management
Applicable to a range of organizations from manufacturing to service industries
Quality assurance systems are defined as the organizational structure, responsibilities,
procedures, processes, and resources for implementing quality management.
ISO 9000 describes the quality elements that must be present for a quality assurance
system
to be compliant with the standard, but it does not describe how an organization should
implement these elements.
ISO 9001 is the quality standard that contains 20 requirements that must be present in an
effective software quality assurance system.
ISO 9001 applicable to organizations which design, develop and maintain products
ISO 9001 is a generic model of the quality process Must be instantiated for each
organization

11
SOFTWARE RELIABILITY
Defined as the probability of failure free operation of a computer program in a
specified
environment for a specified time period
Can be measured directly and estimated using historical and developmental data
(unlike
many other software quality factors)
Software reliability problems can usually be traced back to errors in design or
implementation

11
METRICS FOR SOFTWARE PRODUCT SIZE
ESTIMATION
Line of code(LOC):
LOC as delivered Source instruction.
LOC as kilo delivered Source instruction.
Function point metrics:
Size of software product is directly dependent on the number of different functions or
features it support.

11
SOFTWARE QUALITY ATTRIBUTES
Portability:
A software is claimed to be transportable, if it may be simply created to
figure in several package environments, in several machines, with
alternative code merchandise, etc.
Usability:
A software has smart usability if completely different classes of users (i.e.
each knowledgeable and novice users) will simply invoke the functions of
the merchandise.
Correctness:
A software is correct if completely different needs as laid out in the SRS
document are properly enforced.

11