Download - SQE(Lecture 5)
-
8/6/2019 SQE(Lecture 5)
1/16
Metrics
Q: What is metric?
A quantitative measure of the degree to which a
system, component, or process possesses a given
attributes.
-
8/6/2019 SQE(Lecture 5)
2/16
Software Metrics
Software metrics provide a quantitative measure for
the development and validation of software.
It relates the individual measures in a software
development process.
ex: Average number oferror found per review or
the average number oferror found per unit test.
USES:It can be used to improve software productivity and
quality
-
8/6/2019 SQE(Lecture 5)
3/16
Indicator
An indicator is a metric or combination of metrics that
provides insight into the software development
process, a software project or the product itself.
A software engineer collects measure and develops
metrics so that indicator will be obtained.
-
8/6/2019 SQE(Lecture 5)
4/16
Continue.
Software metrics can be classified into three
categories:
1) Product metrics.
2) Process metrics.
3) Project metrics.
-
8/6/2019 SQE(Lecture 5)
5/16
Product metrics
Product metrics describe the characteristic of thefollowing.
1) Product size.
2) Complexity.
3) Design features.
4) Performance.
5) Quality Level.
-
8/6/2019 SQE(Lecture 5)
6/16
Process Metrics
It can be used to improve software development
and maintenance.
Example:: 1) Defect removal during software
development.
2) The pattern of testing defect arrival, their response
and the time required to fix them.
-
8/6/2019 SQE(Lecture 5)
7/16
Project Metrics
It describes the project characteristics and
execution.
Example:: 1) The number of software developer
needed.
2) Their skill levels.
2) Cost of the project.
3) Schedule and productivity.
-
8/6/2019 SQE(Lecture 5)
8/16
Software Quality Metrics.
Software Quality metrics are a subset of software
metrics that focuses on the quality aspects of the
product, process and project.
Software Quality metrics are more closely associated
with process and product metrics.
-
8/6/2019 SQE(Lecture 5)
9/16
Continue
Software quality metrics can be divided further into
1) End-product quality metrics
2) In-process quality metrics.
-
8/6/2019 SQE(Lecture 5)
10/16
Continue.
End Product Quality Metrics:
End-product quality is usually measured by the number
of "bugs" (functional defects) in the software or by
how long the software can run before a critical failure
(a "crash.").
-
8/6/2019 SQE(Lecture 5)
11/16
Continue
In-Process quality metrics used to measure duringdevelopment process.
Ex: In-Process Quality during Development (derived
by linking bugs to application objects)
1) Defect Density: Number of defects / Size
of application
2) Source of Defects: Number of Defects
originating in each phase3) Requirements Quality: Number of Defects
originating in Requirements phase
-
8/6/2019 SQE(Lecture 5)
12/16
Software Documents
A written document to develop a software product
produced in response to a request for tenders by an
external client.
The documents associated with a software project
being developed have a number of associated
requirements:
-
8/6/2019 SQE(Lecture 5)
13/16
Continue
They should act as a communication medium
between members of the development team.
They should provide information for management to
help them plan, budget and schedule the software
development process.
Some of the documents should tell users how to use
and administer the system.
-
8/6/2019 SQE(Lecture 5)
14/16
Continue
Documentation produced falls into two classes.
1) Process documentation.
2) Product documentation
-
8/6/2019 SQE(Lecture 5)
15/16
Continue
Process documentation:
These documents record the process of
development and maintenance.
Example of Process documentation are
1) Planning
2) scheduling.
-
8/6/2019 SQE(Lecture 5)
16/16
Continue
Product documentation:
This documentation describes the product that is
being developed. System documentation describes the product from
the point of view of the engineers developing and
maintaining the system.
User documentation provides a product description
that is oriented towards system users