Application Development Using Fault Data

Production and Operations Management, Vol. 17, No. 2, pp. 162-174, March-April 2008

13 Pages Posted: 22 Feb 2008 Last revised: 28 Apr 2014

See all articles by Qi Feng

Qi Feng

Purdue University - Krannert School of Management

Vijay Mookerjee

University of Texas at Dallas - Naveen Jindal School of Management

Suresh Sethi

University of Texas at Dallas - Naveen Jindal School of Management

Abstract

We develop a general model for software development process and propose a policy to manage system coordination using system fault reports (e.g., interface inconsistencies, parameter mismatches, etc.). These reports are used to determine the timing of coordination activities that remove faults. We show that under an optimal policy, coordination should be performed only if a "threshold" fault count has been exceeded. We apply the policy to software development processes and compare the management of those projects under different development conditions. A series of numerical experiments are conducted to demonstrate how the fault threshold policy needs to be adjusted to changes in system complexity, team skill, development environment, and project schedule. Moreover, we compare the optimal fault threshold policy to an optimal release-based policy. The release-based policy does not take into account fault data and is easier to administer. The comparisons help to define the range of project parameters for which observing fault data can provide significant benefits for managing a software project. We develop a general model for software development process and propose a policy to manage system coordination using system fault reports (e.g., interface inconsistencies, parameter mismatches, etc.). These reports are used to determine the timing of coordination activities that remove faults. We show that under an optimal policy, coordination should be performed only if a threshold fault count has been exceeded. We apply processes and compare the management of those projects under different development conditions. A series of numerical experiments are conducted to demonstrate how the fault threshold policy needs to be adjusted to environment, and project schedule. Moreover, we compare the optimal fault threshold policy to an optimal release-based policy. The release-based policy does not take into account fault data and is easier to administer. The comparisons help to define the range of project parameters for which observing fault data can provide significant benefits for managing a software project.

Keywords: software development, threshold policy, fault threshold, release-based policy, fault growth model, dynamic programming

JEL Classification: C61, M1

Suggested Citation

Feng, Qi and Mookerjee, Vijay and Sethi, Suresh, Application Development Using Fault Data. Production and Operations Management, Vol. 17, No. 2, pp. 162-174, March-April 2008, Available at SSRN: https://ssrn.com/abstract=1096051

Qi Feng

Purdue University - Krannert School of Management ( email )

1310 Krannert Building
West Lafayette, IN 47907-1310
United States

Vijay Mookerjee

University of Texas at Dallas - Naveen Jindal School of Management ( email )

P.O. Box 830688
Richardson, TX 75083-0688
United States

Suresh Sethi (Contact Author)

University of Texas at Dallas - Naveen Jindal School of Management ( email )

800 W. Campbell Road, SM30
Richardson, TX 75080-3021
United States

Do you have a job opening that you would like to promote on SSRN?

Paper statistics

Downloads
122
Abstract Views
1,161
rank
267,993
PlumX Metrics