Skip to main content
SpringerLink
Log in

Replicating the CREWS Use Case Authoring Guidelines Experiment

  • Published:
Empirical Software Engineering Aims and scope Submit manuscript

Abstract

Use cases have become an important toolin software engineering. There has been much focus on the diagramnotation but relatively little on use-case descriptions. As partof a welcome and important research project into the use of scenariosin requirements engineering, the CREWS (Co-operative RequirementsEngineering With Scenarios, an EU funded ESPRIT project 21903)team has proposed a set of guidelines for writing use-case descriptions.This paper describes the replication of a CREWS project experimentthat suggests CREWS use-case authoring guidelines improve thecompleteness of use-case descriptions. Our results show thatthe CREWS guidelines do not necessarily improve the use-casedescriptions, only that the subjects implemented varying numbersof guidelines in their use-case descriptions. Subjects in thecontrol group implemented a significant percentage of the guidelinesby `chance.' To further justify our results, we also apply adifferent marking scheme to compare with the CREWS approach.The results from the alternative marking approach show that therewas no significant difference between the qualities of the use-casedescriptions across the various groups.

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

Access this article

Log in via an institution

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

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

References

  • Ben Achour, C. 1998. Guiding scenario authoring. Proc. 8th European-Japanese Conference on Information Modeling and Knowledge Bases. Finland, 181-200.

  • Ben Achour, C., Rolland, C., Maiden, N., and Souveyet, C. 1998. Guiding use case authoring: Results of an empirical study. Proc. Fourth IEEE Int. Symposium on Requirements Engineering University of Limerick, Ireland. Version taken from the CREWS web site: http://sunsite.informatik.rwth-aachen.de/CREWS/reports.htm. Report Number: 93-31.

    Google Scholar 

  • Ben Achour, C., and Maiden, N. 1999. Empirical study of use case authoring: Experimental material. Internal Report. Centre de Recherche en Informatique, Universite de Paris 1-Sorbonne. http://panoramix.univparis1.fr/CRINFO/users/benachour/ESEM/.

  • Booch, G., Rumbaugh, J., and Jacobson, I. 1999. The Unified Modelling Language User Guide. Reading, MA: Addison-Wesley.

    Google Scholar 

  • Cockburn, A. 1997. Using goal-based use cases. Journal of Object-Oriented Programming Nov–Dec.

  • Cockburn, A. 2000. Writing Effective Use Cases: Part One. In Print. Addison-Wesley.

  • Cox, K., and Phalp, K. T. 2000. A case study implementing the unified modeling language use-case notation version 1.3. Proc. Sixth Int. Workshop on Requirements Engineering: Foundation for Software Quality. Stockholm, Sweden.

  • Ericksson, H., and Penker, M. 1993. UML Toolkit. Wiley.

  • Fowler, M., and Scott, K. 2000. UML Distilled Second Edition: A Brief Guide to the Standard Object Modelling Language. Reading, MA: Addison-Wesley.

    Google Scholar 

  • Greene, J., and D'Oliveira, M. 1982. Learning to Use Statistical Tests in Psychology: A Student's Guide. Bury St Edmunds, Suffolk: Open University Press.

    Google Scholar 

  • Harwood, R. 1997. Use case formats: Requirements, analysis and design. Journal of Object-Oriented Programming January: 54-66.

  • Jacobson, I. 1987. Object-oriented development in an industrial environment. Proc. OOPSLA'87. Special Issue of SIGPPLAN NOTICES 22(12): 183-197.

    Google Scholar 

  • Jacobson, I., Christerson, M., Jonsson, P., and Oevergaard, G. 1992. Object-Oriented Software Engineering: A Use Case Driven Approach. Addison Wesley.

  • Jarke, M., Pohl, K., Haumer, P., Weidenhaupt, K., Dubois, E., Heymans, P., Rolland, C., Ben Achour, C., Cauvet, C., Ralyte, J., Sutcliffe, A., Maiden, N., and Minocha, S. 1997. Scenario use in European software organisations—Results from the site visits and questionnaires. Taken from the CREWS web site: http://sunsite.informatik.rwth-aachen.de/CREWS/reports.htm. Report Number: 97-10.

  • Nardi, B. 1992. The use of scenarios in design. SIGCHI Bulletin 24(4): 13-14.

    Google Scholar 

  • Pooley, R., and Stevens, P. 1999. Using UML: Software Engineering with Objects and Components. Reading, MA: Addison-Wesley.

    Google Scholar 

  • Rational Software Corporation. 1997. UML notation version 1.1. http://www.rational.com/uml

  • Robson, C. 1993. Real World Research. Blackwell.

  • Rosenberg, G., with Scott, K. 1999 Use Case Driven Object Modeling with UML: A Practical Approach. Reading, MA: Addison Wesley.

    Google Scholar 

  • Swan, M. 1980. Practical English Usage. Oxford University Press.

  • Weidenhaupt, K., Pohl, K., Jarke, M., and Haumer, P. 1998. Scenarios in System Development: Current practice. IEEE Software March/April: 34-45.

Download references

Author information

Authors and Affiliations

  1. Empirical Software Engineering Research Group, School of Design, Engineering & Computing, Bournemouth University, Dorset, UK

    Karl Cox & Keith Phalp

Authors
  1. Karl Cox
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Keith Phalp
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

About this article

Cite this article

Cox, K., Phalp, K. Replicating the CREWS Use Case Authoring Guidelines Experiment. Empirical Software Engineering 5, 245–267 (2000). https://doi.org/10.1023/A:1026542700033

Download citation

  • Issue Date:

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

Search

Navigation