A scheme to prioritize classes at the early stage for improving observable reliability

Authors:
Mitrabinda Ray;Durga Prasad Mohapatra
Affiliations:
National Institute of Technology, Rourkela, India;National Institute of Technology, Rourkela, India
Venue:
Proceedings of the 3rd India software engineering conference
Year:
2010

Citing 7
Cited 1

Object-oriented software engineering

Object-oriented software engineering
Software engineering: theory and practice

Software engineering: theory and practice
Early reliability assessment of UML based software models

WOSP '02 Proceedings of the 3rd international workshop on Software and performance
Operational Profiles in Software-Reliability Engineering

IEEE Software
Improved sampling of the Pareto-front in multiobjective genetic optimizations by steady-state evolution: a Pareto converging genetic algorithm

Evolutionary Computation
On The Estimation Of Reliability Of A Software System Using Reliabilities Of Its Components

ISSRE '97 Proceedings of the Eighth International Symposium on Software Reliability Engineering
Automatic Test Case Generation from UML Models

ICIT '07 Proceedings of the 10th International Conference on Information Technology

Code-based prioritization: a pre-testing effort to minimize post-release failures

Innovations in Systems and Software Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

While testing a program using a test suite of finite size, testing the frequently used classes more thoroughly within the testing budget would lead to higher observable reliability compared to testing all classes uniformly. To achieve this, we first propose a technique to prioritize classes at the design stage according to their impact on the overall reliability of the system. The priority value for a class is calculated based on UML diagrams (Use Case and Sequence diagrams) and operational profile of the system. Then we propose a genetic algorithm-based technique to select test cases for a test suite out of a large pool of test cases such that the intensity with which each class is tested is proportionate to its priority value and the test suite is optimal under other constraints.