Computer-aided software engineering: The determinants of an effective implementation strategy

This report investigates the determinants of a successful Computer-Aided Software Engineering (CASE) tool implementation. Success was defined as a perceived increase in both the quality of software produced and the productivity of the software developers as a result of the introduction of technology. To investigate the effects of certain environmental conditions on the relative success, a survey was mailed to two hundred members of a specific CASE tool user group. Approximately thirty-five percent responded. The findings indicate that an environment which includes the enforcement of a development methodology and use of metrics contribute to perceived improvements in quality when using CASE. Also, use of metrics, use of consultants, and formal training contribute to perceived improvements in developer productivity. Apparently, the presence of each of these environmental conditions significantly contributes to a successful CASE implementation and is, therefore, a 'determinant' of a successful implementation strategy.

[1]  R. J. Norman,et al.  CASE technology transfer: a case study of unsuccessful change , 1989 .

[2]  Watts S. Humphrey,et al.  Software process improvement at Hughes Aircraft , 1991, IEEE Software.

[3]  Watts S. Humphrey,et al.  Characterizing the software process: a maturity framework , 1988, IEEE Software.

[4]  Capers Jones,et al.  Applied software measurement: assuring productivity and quality , 1991 .

[5]  Clifford C. Huff,et al.  Elements of a realistic CASE tool adoption budget , 1992, CACM.

[6]  Ronald J. Norman,et al.  A self-assessment by the software engineering community , 1992, CACM.

[7]  Iris Vessey,et al.  Evaluation of vendor products: CASE tools as methodology companions , 1992, CACM.

[8]  Robert T. Fertig,et al.  The software revolution , 1985 .

[9]  E. Yourdon What ever happened to structured analysis , 1986 .

[10]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[11]  Annette L. du Plessis,et al.  A method for CASE tool evaluation , 1993, Inf. Manag..

[12]  C. Jones CASE's missing elements , 1992, IEEE Spectrum.

[13]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[14]  Gail Corbitt,et al.  Assessing Proximity to Fruition: a Case Study of Phases in Case Technology Transfer , 1991, Int. J. Softw. Eng. Knowl. Eng..

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

[16]  Shari Lawrence Pfleeger,et al.  Software metrics in the process maturity framework , 1990, J. Syst. Softw..

[17]  Jay F. Nunamaker,et al.  CASE productivity perceptions of software engineering professionals , 1989, CACM.

[18]  D. Ross Jeffery,et al.  CASE: a testbed for modeling, measurement and management , 1992, CACM.