Analyzing CASE impact

In large-scale software development, tools are frequently adopted at high cost, to increase quality and productivity. A method for quantitative analysis of the impact of such tool insertions would allow an organization to plan and assess tool insertions. However, currently, there are no practical methods available to accomplish such an analysis. The "Tool Insertion Impact Analysis Method" (TIM/Impact) has been developed to address this deficiency. TIM/ Impact uses quantitative process modeling to analyze tool insertion impact throughout a range of alternative scenarios of processes and project sizes. The method has been validated through a case study in the context of large-scale industrial software development. In this paper, TIM/Impact is introduced, and the data gathered in the study is described and analyzed. In the context of the study, it was found that the process used in the project and the size of the project play a significant role in determining whether the insertion of a tool is an improvement or rather a waste of resources. It was also found that it is always necessary to increase the allocated resources in order to improve quality, even if a tool is introduced, but through the insertion of a tool, quality improvement can be considerably cheaper than without inserting a tool. It is concluded that TIM/Impact can be a valuable aid for making decisions on how a process should be carried out. By providing resource requirement estimates, TIM/Impact can guide the selection of an appropriate technology and process.

[1]  C. P. Hollocker Finding the cost of software quality , 1986, IEEE Transactions on Engineering Management.

[2]  Elliot J. Chikofsky,et al.  Assessing the State of Tools Assessment , 1992 .

[3]  Mark C. Paulk,et al.  Capability Maturity Model , 1991 .

[4]  Barbara A. Kitchenham,et al.  A Methodology for Evaluating Software Engineering Methods and Tools , 1992, Experimental Software Engineering Issues.

[5]  Watts S. Humphrey,et al.  The state of software engineering practice , 1989, ICSE '89.

[6]  Thomas P. Moran,et al.  The evaluation of text editors: methodology and empirical results. , 1983, CACM.

[7]  Nazim H. Madhavji,et al.  The IBM-McGill project on software process , 1991, CASCON.

[8]  Dines Bjørner,et al.  Formal Methods in Software Development: Requirements for a CASE , 1991, Software Development Environments and CASE Technology.

[9]  David N. Card,et al.  Evaluating Software Engineering Technologies , 1987, IEEE Transactions on Software Engineering.

[10]  Harvey P. Siy,et al.  An experiment to assess the cost-benefits of code inspections in large scale software development , 1995, SIGSOFT '95.

[11]  David Bellin Information commodities and the production process: how the introduction of case tools affects the software development life cycle , 1992 .

[12]  Watts S. Humphrey,et al.  The State Of Software Engineering Practice: A Preliminary Report , 1989, 11th International Conference on Software Engineering.

[13]  Roger Alan Pick,et al.  Computer-aided software engineering's impact on the software development process: an experiment , 1991, Proceedings of the Twenty-Fourth Annual Hawaii International Conference on System Sciences.

[14]  Tilmann F. W. Bruckhaus The impact of inserting a tool into a software process , 1993, CASCON.

[15]  Michio Tsuda,et al.  Productivity Analysis Of Software Development With An Integrated CASE Tool , 1992, International Conference on Software Engineering.

[16]  N.H. Madhavji,et al.  Elicit: a method for eliciting process models , 1994, Proceedings of the Third International Conference on the Software Process. Applying the Software Process.

[17]  Tilmann F. W. Bruckhaus,et al.  TIM: a tool insertion method , 1994, CASCON.