Analyzing CASE impact
Abstract
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.
References
[1]
{1} David Bellin. Information Commodities and the Production Process: How the Introduction of CASE Tools Affects the Software Development Life Cycle. Ph.D. thesis, Ph.D. Dissertation, The City University of New York, 1991.
[2]
{2} D. Bjørner and S. Prehn. Formal methods in software development requirements for case. In Software Development Environments and CASE Technology. European Symposium Proceedings, pages 178-210, Berlin, Germany, 17-19 June 1991. Springer-Verlag.
[3]
{3} Tilmann Bruckhaus. The impact of inserting a tool into a software process. In Ann Gawman, W. Morven Gentleman, Evelyn Kidd, Per-Ake Larson, and Jacob Slonim, editors, Proceedings of the 1993 CAS Conference, pages 250-264, Toronto, Ontario, Canada, October 1993. IBM Canada Ltd. and National Research Council of Canada.
[4]
{4} Tilmann Bruckhaus. Case study measurements program. Process Reuse Study (PRS) / Tool Insertion Method (TIM) internal document, January 1994.
[5]
{5} Tilmann Bruckhaus. CMVC/Req User Manual. IBM Canada Ltd., Toronto, Ontario, Canada, 1.3 edition, November 1994.
[6]
{6} Tilmann Bruckhaus. TIM: A tool insertion method. Ph.D. proposal, McGill University, Montreal, Quebec, Canada, July 1994.
[7]
{7} Tilmann Bruckhaus. TIM: A tool insertion method. In Proceedings of the 1994 CAS Conference, pages on CD-ROM, Toronto, Ontario, Canada, November 1994. IBM Canada Ltd. and National Research Council of Canada.
[8]
{8} Elliot Chikofsky, David A. Martin, and Hugh Chang. Assessing the state of tools assessment. IEEE Software, 3(9):18-21, May 1992.
[9]
{9} D. Card, F. McGarry, and G. Page. Evaluating software engineering technologies. IEEE Transactions on Software Engineering, SE-13(7):845-851, July 1987.
[10]
{10} Robert Fichman and Chris Kemerer. Adoption of software engineering process innovations: The case of object orientation. Sloan Management Review, Winter 1993.
[11]
{11} M. Granger and R. Pick. Computer-aided software engineering impact on the software development process: An experiment. In J. F. Nunamaker, editor, Proc. 24th Annual International Conference on System Sciences, volume 3, pages 28-35. IEEE Computer Society Press, 1991.
[12]
{12} W.S. Humphrey, D.H. Kitson, and T.C. Kasse. The state of software engineering practice: A preliminary report. In Proceeding of the 11th International Conference on Software Engineering, pages 277-288, Pittsburgh, Pennsylvania, May 1989. IEEE Computer Society Press.
[13]
{13} C. Hollocker. Finding the cost of software quality. IEEE Transactions on Engineering Management, EM-33(4):223-228, November 86.
[14]
{14} B. Kitchenham. A methodology for evaluating software engineering methods and tools. In Proc. Int. Workshop on Experimental Software Engineering Issues, Dagstuhl Castle, Germany, September 1992. Springer Verlag.
[15]
{15} N. H. Madhavji, D. Höltje, W. Hong, and T. Bruckhaus. Elicit: An empirically improved method for eliciting process models. Technical Report TR 74.141, IBM Canada Ltd., Toronto, 1994.
[16]
{16} N.H. Madhavji, D. Höltje, W.-K. Hong, and T. Bruckhaus. Elicit: A Method for Eliciting Process Models. In Proc. 3rd Int. Conf. on the Software Process (Held at Reston, VA, USA, October 10-11, 1994), pages 111-122, October 1994. IEEE Computer Society Press.
[17]
{17} N. H. Madhavji, K. Toubache, and E. Lynch. The IBM-McGill project on software process. In Proc. CAS Conference (CASCON), pages 95-109, Toronto, Ontario, October 1991. IBM Canada Ltd. and National Research Council of Canada.
[18]
{18} M. Paulk, B. Curtis, M. Chrissis, and C. Weber. Capability maturity model, version 1.1. IEEE Software, pages 18-27, July 1993.
[19]
{19} G. Perez. A tool for the evaluation of software process model congruence. Master's thesis, School of Computer Science, McGill University, 1993.
[20]
{20} A. Porter, H. Siy, C.A. Toman, and L.G. Votta. An experiment to assess the cost-benefits of code inspections in large-scale software development. In Proc. 17th Int. Conf. on Software Engineering, Seattle, April 1995, submitted. IEEE Computer Society.
[21]
{21} T. L. Roberts and T. P. Moran. The evaluation of text editors: Methodology and empirical results. Communications of the ACM, 26(4):265-283, April 1983.
[22]
{22} M. Tsuda, Y. Morioka, M. Takadachi, and M. Takahashi. Productivity analysis of software development with an integrated case tool. In Proceedings of 14th International Conference on Software Engineering, pages 49-58, Melbourne, Australia, May 1992. IEEE Computer Society Press.
[23]
{23} Robert K. Yin. Applied Social Research Methods Series: Case Study Research - Design and Methods, volume 5 of Applied Social Research Methods Series. SAGE Publications Inc., Thousand Oaks (CA), London, New Delhi, 2 edition, 1994.
[24]
{24} R. Zultner. The Deming approach to software quality engineering. Quality Progress, 21(11):58-64, Nov. 1988.
Index Terms
- Analyzing CASE impact
Recommendations
TIM: a tool insertion method
CASCON '94: Proceedings of the 1994 conference of the Centre for Advanced Studies on Collaborative researchSoftware tools play an important role in the software development process. Some tools are used by users taking on one specific role, in very specific activities and to process documents of a specific type (e.g., a compiler). Other tools are used by ...
The impact of agile principles on market-driven software product development
Agile development methods such as extreme programming (XP), SCRUM, Lean Software Development (Lean SD) and others have gained much popularity during the last years. Agile methodologies promise faster time-to-market, satisfied customers and high quality ...
Comments
Information & Contributors
Information
Published In
November 1995
722 pages
- Conference Chair:
- Dennis Bockus,
- Editors:
- Karen Bennet,
- Morven Gentleman,
- Howard Johnson,
- Evelyn Kidd
Sponsors
- IBM Canada: IBM Canada
- NRC: National Research Council - Canada
Publisher
IBM Press
Publication History
Published: 07 November 1995
Author Tags
Qualifiers
- Article
Acceptance Rates
Overall Acceptance Rate 24 of 90 submissions, 27%
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- 0Total Citations
- 527Total Downloads
- Downloads (Last 12 months)17
- Downloads (Last 6 weeks)3
Reflects downloads up to 05 Mar 2025
Other Metrics
Citations
View Options
Login options
Check if you have access through your login credentials or your institution to get full access on this article.
Sign in