Skip to main content

Advertisement

Springer Nature Link
Log in

Validating software requirements with enactable use case descriptions

  • Original Article
  • Published:
Requirements Engineering Aims and scope Submit manuscript

Abstract

Use cases have gained wide acceptance since the standardisation of the UML by the Object Management Group in 1997. This paper addresses the inadequacy of use cases for expressing intra-use case and inter-use case dependencies. We present a state-based approach for facilitating explicit consideration of such dependencies in use case descriptions, and a support tool is described, which provides enaction of the state-based use cases to support validation. We outline an industrial study involving the specification of real-time monitoring systems, wherein we demonstrate that enaction of the state-based use cases highlighted important dependency issues that had not been revealed within standard use cases.

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

Access this article

Log in via an institution

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

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

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8
Fig. 9
Fig. 10
Fig. 11
Fig. 12

Similar content being viewed by others

References

  1. Broy M (2006) The ‘grand challenge’ in informatics: engineering software-intensive systems. IEE Comput Soc 39(10)

  2. Maiden N, Robertson S (2005) Developing use cases and scenarios in the requirements process. In: 26th International conference on software engineering. ACM press, New York

  3. Cheng B, Atlee JM (2007) Research directions in requirements engineering. In: Future of software engineering, Minneapolis, MN, USA

  4. Some S (2005) Use cases based requirements validation with scenarios. In: The 13th IEEE international conference on requirements engineering. IEEE Computer Society, Paris

  5. Maiden N, Robertson S (2005) Developing use cases and scenarios in the requirements process. In: IEEE international conference on software engingeering

  6. Subramaniam K et al (2004) UCDA: Use case driven development assistant tool for class model generation. In: The 16th international conference on software engineering and knowledge engineering, Banff, Canada

  7. Rysavy O, Bures F (2004) Formal abstract architecture for use case specifications. In: 11th IEEE international conference and workshop on the engineering of computer-based systems

  8. Cox K, Aurum A, Jeffery R (2003) A use case description inspection experiment. In: 8th Australian workshop on software requirements, Sydney, Australia

  9. Rolland C, Achour B (1998) Guiding the construction of textual use case specifications. CREWS report series

  10. Regnell B (1999) Requirements engineering with use cases—a basis for software development. In: Department of Commnunication Systems, Lund Institute of Technology. Lund University, Sweden

  11. Cockburn A (2001) Writing effective use cases. Addison-Wesley, Reading

  12. Cox K (2002) Heuristics for use case descriptions. In: Design, engineering & computing. Bournemouth University, UK

  13. Sutcliffe A et al (1998) Supporting scenario-based requirements engineering. IEEE Trans Softw Eng 24(12):1072–1088

    Article  Google Scholar 

  14. Sutcliffe A (1998) Scenario-based requirements analysis. Req Eng J 3:48–65

    Article  Google Scholar 

  15. Elkoutbi M, Khriss I, Keller K (2005) Automated prototyping of user interfaces based on UML scenarios. Autom Softw Eng 13(1)

  16. Maiden N (2004) Discovering requirements with scenarios: the ART-SCENE solution. Special theme, Automated Software Enginering

  17. OMG (2002) Unified modelling language specification version 2.0. [cited 2004 March]. Available from: http://www.uml.org/

  18. Glinz M (2002) Statecharts for requirements specification-as simple as possible, as rich as needed. In: Proceedings of ICSE; workshop on scenarios and state machines; models, algorithms and tools

  19. Uchitel S, Kramer J, Magee J (2003) Synthesis of behavioural models from scenarios. IEEE Trans Softw Eng 29(2)

  20. Uchitel S, Robert C, Jeff Kramer JM (2006) Goal and scenario validation: a fluent combination. Req Eng 11(2)

  21. Phalp K, Henderson P, Abeysinghe G, Walters B (1998) RolEnact: role-based enactable models of business processes. Inform Softw Technol J 40(3)

  22. Zimmerman MK, Lundqvist K, Leveson NG (2002) Investigating the readability of state-based formal requirements specification languages. In: International conference in software engineering, Florida, USA

  23. Harel D, Marelly R (2001) Capturing and executing behavioral requirements: the Play-In/Play-Out approach. The Weizmann Institute of Science, Rehovot

    Google Scholar 

  24. Rolland C (2002) L’E-Lyee: coupling L’Ecritoire and LyeeALL. Inform Softw Technol J 44(3)

  25. BetterHealthChannel. Artificial cardiac pacemakers. [Internet site] 2001 [cited 2004; Available from: http://www.betterhealth.vic.gov.au/bhcv2/bhcarticles.nsf/pages/Artificial_cardiac_pacemakers?open

  26. Douglass BP (2000) Real-time UML: developing efficient objects for embedded systems. Addison-Wesley, Reading

  27. Seybold C, Meier S, Glinz M (2004) Evolution of requirements models by simulation. In: International workshop on principles of software evolution, Kyoto, Japan

  28. Eshuis R, Wieringa R (2004) Tool support for verifying UML activity diagrams. IEEE Trans Softw Eng 30(7)

  29. Heymans P, Dubois E (1997) Some thoughts about the animation of formal specifications written in the Albert II language. In: 3rd IEEE international symposium on requirements engineering

  30. Magee J et al (2000) Graphical animation of behavior models. In: Proceedings of the 22nd international conference on software engineering

  31. Jacobson I (1992) Object-oriented software engineering: a use case driven approach. Addison-Wesley, Wokingham

    MATH  Google Scholar 

  32. Jacobson I ed (1995) The use case construct in object-oriented software engineering. In: Carroll JM (ed) Scenario-based design: envisioning work and technology in system development. Wiley, New York

  33. Homrighausen A, Six H, Winter M (2001) Round-trip prototyping for the validation of requirements specifications. In: Requirements engineering: foundations for software quality. Interlaken, Switzerland

    Google Scholar 

  34. Jørgensen JB, Bossen C (2004) Executable use cases as links between application domain requirements and machine specifications. In: 3rd international workshop on scenarios and state machines (at ICSE04), Edinburgh, Scotland

Download references

Author information

Authors and Affiliations

  1. Software Systems Research Centre, Bournemouth University, Bournemouth, UK

    John Mathenge Kanyaru & Keith Phalp

Authors
  1. John Mathenge Kanyaru
    View author publications

    You can also search for this author inPubMed Google Scholar

  2. Keith Phalp
    View author publications

    You can also search for this author inPubMed Google Scholar

Corresponding author

Correspondence to John Mathenge Kanyaru.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Kanyaru, J.M., Phalp, K. Validating software requirements with enactable use case descriptions. Requirements Eng 14, 1–14 (2009). https://doi.org/10.1007/s00766-008-0070-8

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-008-0070-8

Keywords