This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
A Case Study of Software Process Improvement During Development
December 1993 (vol. 19 no. 12)
pp. 1157-1170

We present a case study of the use of a software process improvement method which is based on the analysis of defect data. The first step of the method is the classification of software defects using attributes which relate defects to specific process activities. Such classification captures the semantics of the defects in a fashion which is useful for process correction. The second step utilizes a machine-assisted approach to data exploration which allows a project team to discover such knowledge from defect data as is useful for process correction. We show that such analysis of defect data can readily lead a project team to improve their process during development.

[1] W. S. Humphrey,Managing the Software Process. Reading, MA: Addison-Wesley, 1989.
[2] V.R. Basili and H.D. Rombach, "The Tame Project: Towards Improvement-Oriented Software Environments,"IEEE Trans. Software Eng., Vol. SE-14, No. 6, June 1988, pp. 758-773.
[3] H. Rombach, G. Ulery, and J. Valett, "Toward full life cycle control: Adding maintenance measurement to the SEL,"J. Syst. Software, vol. 18, pp. 125-138, 1992.
[4] N. H. Madhavji, "The Process cycle,"Software Eng. J.Special Issue on "Software Process and Its Support," to be published.
[5] V. R. Basili and H. D. Rombach, "Tailoring the software process to project goals and environments, " inProc. 9th Int. Conf. on Software Eng.Los Alamitos, CA: IEEE Computer Soc. Press, 1987, pp. 345-357.
[6] R. Mays, C. Jones, G. Holloway, and D. Stidinski, "Experiences with defect prevention,"IBM Syst. J., vol. 29, no. 1, 1990.
[7] V.R. Basili, "Software Development: A Paradigm for the Future,"Proc. Compsac 89, IEEE Computer Soc. Press, Los Alamitos, Calif., Order No. 1964, pp. 471-485.
[8] V. R. Basili and R. W. Selby, "Paradigms for experimentation and empirical studies in software engineering,"Rel. Eng. Syst. Safety, vol. 32, pp. 171-191, 1991.
[9] R. Chillarege, I. Bhandari, J. Chaar, M. Halliday, D. Moebus, B. Ray, and M. Y. Wong, "Orthogonal defect classification--A concept for in-process measurement,"IEEE Trans. Software Eng., vol. 18, pp. 943-956, Nov. 1992.
[10] J. Chaar, M. Halliday, I. Bhandari, and R. Chillarege, "In-process metrics for software inspection and test evaluations,"IEEE Trans. Software Eng., accepted for publication, 1993; also available as IBM Res. Rep. RC (log 80725), 1992.
[11] I. Bhandari, "Attribute focusing: Machine-assisted knowledge discovery applied to software production process control," inProc. Workshop Knowledge Discovery in Databases, AAAI Tech. Rep. Series, Rep. No. WF-93-02, July 1993; also inKnowledge Acquisition, accepted for publication.
[12] I. Bhandari and N. Roth, "Post-process feedback with and without attribute focusing: A comparative evaluation," inProc. Int. Conf. Software Engineering, May 1993, pp. 89-98.
[13] G. Piatetsky-Shapiro and W. Frawley,Knowledge Discovery in Databases. Menlo Park, CA: AAAI Press/MIT Press, 1991.
[14] A. Ram, "Knowledge goals: A theory of interestingness," inProc. 12th Annu. Conf. Cognitive Science Soc., Aug. 1990.
[15] J. Mingers, "Empirical comparison of selection measures for decision tree induction,"Machine Learning, vol. 3, pp. 319-342, 1989.
[16] W. Frawley, G. Piatetsky-Shapiro, and C. Matheus, "Knowledge discovery in databases: An overview," inKnowledge Discovery in Databases, G. Piatetsky-Shapiro and W. Frawley, Eds. Menlo Park, CA: AAAI Press/MIT Press, 1991.
[17] G. Miller, "The magical number seven, plus or minus two: Some limits on our capacity for processing information,"Psychol. Rev., vol. 63, 1956.
[18] M. Fagan, "Design and code inspections to reduce errors in program development,"IBM Syst. J., vol. 15, no. 3, 1976.
[19] T. Glib and S. Finzi,Principles of Software Engineering Management. Reading, MA: Addison-Wesley, 1988.
[20] A. von Mayrhauser,Software Eng.: Methods and Management, Academic Press, Boston, 1990, pp. 723-725.
[21] J. D. Musaet al., Software Reliability Measurement, Prediction, Application. New York: McGraw-Hill International, 1987.
[22] A. L. Goel, "Software reliability models: Assumptions, limitations,"IEEE Trans. Software Eng., vol. SE-11, no. 12, pp. 1411-1423, 1985.
[23] B. Ray, I. Bhandari, and R. Chillarege, "Reliability growth for typed defects," inProc. IEEE Reliability and Maintainability Symp., 1991.

Index Terms:
case study; software process improvement; defect data analysis; software defects; attributes; process activities; semantics; process correction; machine-assisted approach; data exploration; project team; software engineering; defect-based process improvement; in-process metrics; knowledge discovery; data handling; project management; software engineering; software metrics
Citation:
I. Bhandari, M. Halliday, E. Tarver, D. Brown, J. Chaar, R. Chillarege, "A Case Study of Software Process Improvement During Development," IEEE Transactions on Software Engineering, vol. 19, no. 12, pp. 1157-1170, Dec. 1993, doi:10.1109/32.249661
Usage of this product signifies your acceptance of the Terms of Use.