Subject Software Metrics Class 5th Semester Report Title:

Subject               

Software Metrics

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

Class

5th
Semester

 

Report Title:

   

Uses of software metrics in the area of Software Testing

 

 

Report Prepared By:

 

Mohsin-Mustafa

 

Report Submitted To:

 

Ma’am Momina

 

Registration No.

 

BSSE-10153005

 

Submitted date:

 

8-1-2018

 

                  
ACKNOWLDGEMENT

I express my thanks to Ma’am Momina
of University of Lahore Pakpattan Campus for having
provided me the facilities to do the Software Testing report successfully.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

TABLE OF CONTENTS

 

Title

Page No.

Executive Summary

 

Introduction
       Background
       Purpose
       Scope
       Report Organization

 

Discussion/Analysis
       Methodology
       Findings

 

Conclusions & Recommendations

 

References

 

Appendices

 
 
 

 

 

 

 

 

 

 

 

 

 

Executive Summary

In the current trend most of the
software is required to be evaluated for two reasons. One the customer wants to
get satisfied from the quality of the product which he will be going to use
because he has invested a lot of amount to get the product. Two the developers
want to quantify the quality so that his effort in further stages and in
maintenance must not increased due to low quality. The testing is required to
be fast and with less effort that is through the automated testing tools. The
setback is confusion of way of selection of tool. The positive side of the
paper is that it helps the developer in deciding the best testing tool as per
his project by calculating the metrics value for the available tools in hand.
The weakness of the proposed work is that it required a bit of time and effort
in doing calculations for evaluating the tools and some data may also be needed
in calculation of metrics.

As per the experience we have
during the work, we would like to mention our view for the further extension of
this work. The upper and lower bound of the tools metrics must be investigated.
The more number of tools must be exposed to metrics to have the further
empirical analysis. The categorization of the tools on the basis of
functionality is required and the specification of particular metric for that
type may be suggested. An algorithmic approach may be generated to have the
fast automated evaluation of metrics which may reduce the effort to calculate
the metrics and automated suggestion for the better tools may also be a work
piece.

 

 

 

 

 

 

 

 

 

 

Ø     Introduction

Software Metrics is a measurement
based technique which is applied to processes, products and services to supply engineering
and management information and working on the information supplied to improve
processes, products and services, if required. Software Testing Metrics are experimental
measures that could be used to measure different characteristics of a software
system or the software development process. In recent years software testing technologies
have appeared as a leading software engineering practice which helps in
effective cost control, quality improvements, time and risk reduction etc.

We need metrics because it helps us
in understanding the type of improvement required and helps in taking decisions
on process or technology change. The importance of metrics
is to improve the quality and productivity of products and services through
customer satisfaction. Metrics provides enhancement for current processes.

Importance
of Metrics

Metrics is used to improve the
quality and productivity of products and services thus achieving Customer
Satisfaction.

Easy for management to digest one
number and drill down, if required.

Different Metric(s) trend act as
monitor when the process is going out-of-control.

Metrics provides improvement for
current process.

 

 

 

 

 

 

 

 

 

 

 

 

·       
Background

What is Software
Testing Metric?

In software
testing, Metric is a quantitative measure of the degree to which
a system, system component, or process possesses a given attribute.

In other words, metrics helps
estimating the progress, quality and health of a software testing effort. The
ideal example to understand metrics would be a weekly mileage of a car compared
to its ideal mileage recommended by the manufacturer.

There is a need to establish a
software testing process that is cost effective and efficient to
meet the market pressures of delivering low cost and quality software.
Measurement is a key element of an effective and efficient software testing
process as it evaluates the quality and
effectiveness of the process. Moreover, it assesses the productivity of the
personnel involved
in testing activities and helps improving the software testing procedures,
methods, tools and
activities 21. Gathering of software testing related measurement data and
proper analysis
provides an opportunity for the organizations to learn from their past history
and grow in
software testing process maturity.
Measurement is a tool through which the management identifies important events
and
trends, thus enabling them to make informed decisions. Moreover, measurements
help in
predicting outcomes and evaluation of risks, which in turn decreases the
probability of
unanticipated surprises in different processes. In order to face the challenges
posed by the
rapidly changing and innovative software industry, the organizations that can
control their
software testing processes are able to predict costs and schedules and increase
the
effectiveness, efficiency and profitability of their business 22.Therefore,
knowing and
measuring what is being done is important for an effective testing effort 9.

 

 

 

Metrics LifeCycle

Type of Software Testing Metrics

Based on the types of testing performed,
following are the types of software testing metrics: –

1.     
Manual Testing Metrics

2.     
Performance Testing Metrics

3.     
Automation Testing Metrics

Manual Testing Metrics

Test Case Productivity (TCP)

This metric gives the test case writing productivity based
on which one can have a conclusive remark.

 

 

Example

Test Case
Name

Raw Steps

XYZ_1

30

XYZ_2

32

XYZ_3

40

XYZ_4

36

XYZ_5

45

Total Raw
Steps

183

 

 

 

 

 

 

 

 

Efforts took for writing 183 steps
is 8 hours.

TCP=183/8=22.8

Test case productivity = 23
steps/hour

 

Defect Acceptance (DA)

This metric determine the number of
valid defects that testing team has identified during execution.

The value of this metric can be
compared with previous release for getting bet picture

Defect Rejection (DR)

This metric determine the number of
defects rejected during execution.

Bad Fix Defect (B)

Defect whose resolution give rise
to new defect(s) are bad fix defect.

This metric determine the
effectiveness of defect resolution process.

 

Test Efficiency (TE)

This metric determine the efficiency of the testing team in
identifying the defects.

It also indicated the defects missed out during testing
phase which migrated to the next phase.

Where,

DT = Number of valid defects identified during testing.

DU = Number of valid defects
identified by user

1.2 Purpose
The purpose
of this thesis is to offer visibility in to the software testing process using
measurements. The focus of this thesis is at the possible measurements in the
Test Planning
and Test Design process of the system testing level.

Why do Test Metrics?

“We cannot improve what we
cannot measure” and Test Metrics helps us to do exactly the same.

Take decision for next phase of
activities

Evidence of the claim or prediction

Understand the type of improvement
required

Take decision or process or
technology change

·       
Process
Metrics:

It can be used to improve the
process efficiency of the SDLC ( Software Development Life Cycle)

·       
Product
Metrics

It deals with the quality of the
software product

·       
Project
Metrics

 It can be used to measure the
efficiency of a project team or any testing tools being used by the team
members

 

 

 

 

 

 

Discussion/Analysis

A detailed and comprehensive
literature study will be carried out to gather material related to
software testing lifecycle in general and for software test planning, test
design and metrics in
particular. The literature study will encompass the material as written down in
articles, books
and web references.
The literature study is conducted with the purpose of finding key areas of
interest related
to software testing and metrics support for test planning and test design processes.
The
literature study is divided into two steps. The first step creates a relevant
context by

analyzing key phases in the
software testing lifecycle, inputs required for starting the
software test planning and test design processes and metrics indicating the end
of these two
processes. The second step identifies the attributes of software test planning
and test design
processes along with metric support for each of the identified attributes.
While performing the literature study, it is important to define a search
strategy. The
main search engines used in the study were IEEE Xplore and ACM digital library.
The
search was performed with combination of various key terms that we were
interested in. By
using of the above mentioned search engines and using combination of terms for
searching,
we expect to have minimized the chances of overlooking papers and literature.
In addition,
manual search was performed on the relevant conference proceedings. The most
notable of
these is the International Software Metrics Symposium proceedings. In addition
to IEEE
Xplore and ACM digital library, web search engines Google and Yahoo were used
occasionally with the purpose of having a diverse set of literature sources.
For each paper of interest, relevant material was extracted and compared
against the
other relevant literature. Specifically; the abstract, introduction and the
conclusion of each of
the articles were studied to assess the degree of relevance of each article.
The references at
the end of each research paper were also quickly scanned to find more relevant
articles. Then
a summary of the different views of authors was written to give reader
different perspectives
and commonalities on the topic.
It is also worth mentioning the use of books written by well-known authors in
the field
of software metrics and software testing. It is to complement the
summarizations done from
the research articles found from above mentioned search strategy. A total of
twenty five
books were referred. The reference lists given at the end of relevant chapters
in these books
also proved a valuable source of information

 

 

Conclusion

Today, the majority of the metrics
in software testing are based on test execution phase and
on the basis of number of faults found in test execution. There is an apparent
gap when we
are interested in metrics for test planning and test design processes.
Therefore, by focusing
on the metric support in the test planning and test design processes, this
thesis has
contributed in filling part of this gap.

The measurable attributes of
software test planning and test design are not mentioned in
literature in a consolidated form. By identifying seventeen attributes for
software test
planning and thirty one attributes for software test design processes, the
thesis serves to
consolidate the attributes that are useful for measurement. The thesis
partitioned the
attributes in different categories, for software test planning there are four
categories while
there are five for software test design process. Such a categorization is a
contribution
towards assigning classes to the identified attributes, which may entice
further research
within each category.
The thesis discussed metric support for the identified attributes for the test
planning and
test design processes. Again, there were different studies contributing to the
measurement of
each attribute. The thesis presented the different ways to measure each of the
attributes with
the intention to provide a variety of methods for the reader to think of and
choose according
to the context of the situation at hand.
An interesting aspect resulting from this thesis is that although measurements
help
informed decision making, but a degree of subjectivity, expert judgment and
analogy still
plays an important role in the final decision relating to software test
planning and test design.
Therefore, reaching a decision must interplay between knowledgeable judgment
and metric
results.
An organization can build a metrics program for its software test planning and
test
design processes on the foundations of attributes identified in the thesis. It
is expected that
such an effort will lead to informed decision making about different software
testing
activities, in addition to the formulation of a baseline for measuring
improvement.

Metric is the cornerstone in
assessment and foundation for any business improvement. It is a Measurement
Based Technique which is applied to processes, products and services to supply
engineering and management information and working on the information supplied
to improve processes, products and services, if required. It indicates level of
Customer satisfaction, easy for management to digest number and drill down,
whenever required and act as monitor when the process is going out-of-control.

 

x

Hi!
I'm Gerard!

Would you like to get a custom essay? How about receiving a customized one?

Check it out