Skip to main content
Log in

Empirical Evaluation of CASE Tools Usage at Nokia

  • Published:
Empirical Software Engineering Aims and scope Submit manuscript

Abstract

We presentthe results of a research work targeted to understanding thedomains and consequences of CASE tools usage in Nokia. We aimto evaluate the importance of the various CASE tools features,as rated by our developers, and how well such features are implementedin currently available CASE tools. A structured questionnairewas sent to our most experienced developers and CASE users. Fromthis survey, it emerged that CASE tools support is reputed mostuseful for the following functions: graphical drawing, automaticdocumentation generation and storage of diagrams. The resultshint to a mismatch between the features required by the developersand those offered by CASE products. Further research is neededbefore more definite conclusions can be drawn.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  • Basili, V. R., and Rombach, H. D. June 1988. The TAME project: towards improvement-oriented software environments. IEEE Transactions on Software Engineering. 14(6).

  • Basili, V. R., Shull, F., and Lanubile, F. July/August 1999. Building knowledge through families of experiments. IEEE Transactions on Software Engineering. 25(4).

  • Edwards, B. 1972. Statistics for business students. 1st Edition. Collins.

  • Fenton, N., Pfleger, S. Lawrence, and Glass, R. L. July 1994. Science and substance: A challenge to software engineers. IEEE Software. 86-95.

  • Glass, R. L. February 1999. The realities of software technology—Payoffs. Communications of the ACM.

  • Hendrickson, E. January/February 1999. Evaluating CASE tools. Software Testing & Quality Engineering. 38-42.

  • Iivari, J., and Maansaai, J. 1998. The usage of systems development: Why are we stuck to old practices? Information and Software Technology. Elsevier Science, 501-510.

  • ISO/IEC 14102. 15 Nov 1995. Information technology, guideline for the evaluation and selection of CASE tools. First edition.

  • overview.html.

  • Orlikowski, W. J., and Baroudi, J. J. 1991. Studying information technology in organizations, research approaches and assumptions. Information Systems Research. 2:1.

    Google Scholar 

  • Orlikowski, W. J. September 1993. CASE tools as organizational change investigating incremental and radical changes in systems development. Management Information Systems Quarterly. 17(3).

  • Post, G., Kagan, A., and Keim, R. T. 1998. A comparative evaluation of CASE tools. The Journal of Systems and Software. Elsevier Science, 44: 87-96.

    Google Scholar 

  • [Prosa]: http://www.insoft.fi/prmain.html.

  • [QLM]: http://www.qualiware.dk/doc1085.htm.

  • [RationalRose]: http://www.rational.com/products/rose/index.jtmpl.

  • c.htm.

  • Wood, M., Daly, J., Miller, J., and Roper, M. 1999. Multi-method research: An empirical investigation of object-oriented technology. The Journal of Systems and Software. 48: 13-26.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Maccari, A., Riva, C. Empirical Evaluation of CASE Tools Usage at Nokia. Empirical Software Engineering 5, 287–299 (2000). https://doi.org/10.1023/A:1026546800942

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1023/A:1026546800942

Navigation