Skip to main content

Use Cases versus Task Descriptions

  • Conference paper
Requirements Engineering: Foundation for Software Quality (REFSQ 2011)

Part of the book series: Lecture Notes in Computer Science ((LNPSE,volume 6606))

Abstract

[Context and motivation] Use cases are widely used as a substantial part of requirements, also when little programming is expected (COTS-based systems). [Question/problem] Are use cases effective as requirements? To answer this question, we invited professionals and researchers to specify requirements for the same project: Acquire a new system to support a hotline. [Principal ideas/results] Among the 15 replies, eight used traditional use cases that specified a dialog between users and system. Seven used a related technique, task description, which specified the customer’s needs without specifying a dialog. [Contribution] It turned out that the traditional use cases covered the customer’s needs poorly in areas where improvement was important but difficult. Use cases also restricted the solution space severely. Tasks didn’t have these problems and allowed an easy comparison of solutions.

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

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Achour, C.B., Rolland, C., Maiden, N.A.M., Souveyet, C.: Guiding Use Case Authoring: Results of an Empirical Study. In: Proceedings of the 4th IEEE International Symposium (1999)

    Google Scholar 

  2. Armour, F., Miller, G.: Advanced Use Case Modeling. Addison-Wesley, Reading (2001)

    Google Scholar 

  3. Cockburn, A.: Writing Effective Use Cases. Addison-Wesley, Reading (2000)

    Google Scholar 

  4. Constantine, L.L., Lockwood, L.A.D.: Software for Use: A practical guide to the Models and Methods of Usage-Centered Design. Addison-Wesley, New York (1999)

    Google Scholar 

  5. Cox, K., Phalp, K.: Replicating the CREWS Use Case Authoring Guidelines. Empirical Software Engineering Journal 5(3), 245–268 (2000)

    Article  MATH  Google Scholar 

  6. IEEE Recommended Practice for Software Requirements Specification, ANSI/IEEE Std. 830 (1998)

    Google Scholar 

  7. Jacobson, I., Christerson, M., Johnsson, P., Övergaard, G.: Object-Oriented Software Engineering - a use case driven approach. Addison-Wesley, Reading (1992)

    MATH  Google Scholar 

  8. Jacobson, I.: Use Cases: Yesterday, Today, and Tomorrow. IBM Technical Library (2003)

    Google Scholar 

  9. Kulak, D., Guiney, E.: Use Cases: Requirements in Context. Addison-Wesley, Reading (2000)

    Google Scholar 

  10. Lauesen, S.: Software requirements - styles and techniques. Addison-Wesley, Reading (2002)

    Google Scholar 

  11. Lauesen, S.: Task Descriptions as Functional Requirements. IEEE Software, 58–65 (March/April 2003)

    Google Scholar 

  12. Lauesen, S.: User interface design - a software engineering perspective. Addison-Wesley, Reading (2005)

    Google Scholar 

  13. Lauesen, S.: Guide to Requirements SL-07 -Template with Examples (2007) ISBN: 978-87-992344-0-0, www.itu.dk/people/slauesen/SorenReqs.html#SL-07

  14. Lauesen, S., Kuhail, M.A.: The use case experiment and the replies (2009), http://www.itu.dk/people/slauesen/

  15. Lilly, S.: Use Case Pitfalls: Top 10 Problems from Real Projects Using Use Cases. IEEE Computer Society, Washington, DC, US (1999)

    Google Scholar 

  16. Maiden, N.A., Ncube, C.: Acquiring COTS software selection requirements. IEEE Software, 46–56 (March/April 1998)

    Google Scholar 

  17. Rosenberg, D., Scott, K.: Top Ten Use Case Mistakes, Software Development (2001), http://www.drdobbs.com/184414701

  18. Sigurðardóttir, Hrönn Kold: Project manager for the Electronic Health Record system at the Capital Hospital Association (H:S): Draft of PhD thesis (2010)

    Google Scholar 

  19. Wirfs-Brock, R.: Designing Scenarios: Making the Case for a Use Case Framework, Smalltalk Report (November/December 1993), http://www.wirfs-brock.com/PDFs/Designing%20Scenarios.pdf

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2011 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Lauesen, S., Kuhail, M.A. (2011). Use Cases versus Task Descriptions. In: Berry, D., Franch, X. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2011. Lecture Notes in Computer Science, vol 6606. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-19858-8_13

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-19858-8_13

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-19857-1

  • Online ISBN: 978-3-642-19858-8

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics