The document discusses various software quality assurance plans, emphasizing the importance of measurement in managing software processes, projects, and products. It outlines different types of metrics, such as process metrics, project metrics, and product metrics, which help assess quality, productivity, and cost estimation throughout the software development lifecycle. The document also highlights the reasons for measuring software quality, including improving processes, evaluating staff performance, and justifying resources for software engineering tools and training.

1. Software Engineering: 11
Software Quality Assurance Plans
Prof Neeraj Bhargava
Vaibhav Khanna
Department of Computer Science
School of Engineering and Systems Sciences
Maharshi Dayanand Saraswati University Ajmer

2. • If you can’t measure it, you can’t manage it
 Measurement
◦ is the act of obtaining a measure
 Measure
◦ provides a quantitative indication of the size of some
product or process attribute, E.g., Number of errors
 Metric
◦ is a quantitative measure of the degree to which a system,
component, or process possesses a given attribute (IEEE
Software Engineering Standards 1993) : Software Quality -
E.g., Number of errors found per person hours expended

3. What to measure
•Process
Measure the efficacy of processes. What
works, what doesn't.
•Project
Assess the status of projects. Track risk.
Identify problem areas. Adjust work flow.
•Product
Measure predefined product attributes

4. What to measure
• Process
Measure the efficacy of processes. What
works, what doesn't.
• Code quality
• Programmer productivity
• Software engineer productivity
– Requirements,
– design,
– testing
– and all other tasks done by software engineers

5. What to measure
• Software
– Maintainability
– Usability
– And all other quality factors
• Management
– Cost estimation
– Schedule estimation, Duration, time
– Staffing

6. Process Metrics
• Process metrics are measures of the software
development process, such as
– Overall development time
– Type of methodology used
• Process metrics are collected across all
projects and over long periods of time.
• Their intent is to provide indicators that lead
to long-term software process improvement

7. Project Metrics
• Project Metrics are the measures of Software Project and are
used to monitor and control the project. Project metrics
usually show how project manager is able to estimate
schedule and cost
• They enable a software project manager to:
 Minimize the development time by making the adjustments
necessary to avoid delays and potential problems and risks.
 Assess product cost on an ongoing basis & modify the technical
approach to improve cost estimation.

8. Product metrics
• Product metrics are measures of the software
product at any stage of its development, from
requirements to installed system. Product
metrics may measure:
– How easy is the software to use
– How easy is the user to maintain
– The quality of software documentation
– And more ..

9. Why do we measure?
• Determine quality of piece of software or
documentation
• Determine the quality work of people such software
engineers, programmers, database admin, and most
importantly MANAGERS
• Improve quality of a product/project/ process
• To assess the benefits derived from new software
engineering methods and tools
• To close the gap of any problems (E.g training)
• To help justify requests for new tools or additional
training

10. Examples of Metrics Usage
• Measure estimation skills of project managers
(Schedule/ Budget)
• Measure software engineers
requirements/analysis/design skills
• Measure Programmers work quality
• Measure testing quality
And much more …

11. A quantitative measure of the degree to which
an item possesses a given quality attribute.
A function whose inputs are software data and
whose output is a single numerical value that
can be interpreted as the degree to which the
software possesses a given quality attribute.

12. Assignment
• What do You understand by software Quality
Matrix.
• Thank You