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.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
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)
Armour, F., Miller, G.: Advanced Use Case Modeling. Addison-Wesley, Reading (2001)
Cockburn, A.: Writing Effective Use Cases. Addison-Wesley, Reading (2000)
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)
Cox, K., Phalp, K.: Replicating the CREWS Use Case Authoring Guidelines. Empirical Software Engineering Journal 5(3), 245–268 (2000)
IEEE Recommended Practice for Software Requirements Specification, ANSI/IEEE Std. 830 (1998)
Jacobson, I., Christerson, M., Johnsson, P., Övergaard, G.: Object-Oriented Software Engineering - a use case driven approach. Addison-Wesley, Reading (1992)
Jacobson, I.: Use Cases: Yesterday, Today, and Tomorrow. IBM Technical Library (2003)
Kulak, D., Guiney, E.: Use Cases: Requirements in Context. Addison-Wesley, Reading (2000)
Lauesen, S.: Software requirements - styles and techniques. Addison-Wesley, Reading (2002)
Lauesen, S.: Task Descriptions as Functional Requirements. IEEE Software, 58–65 (March/April 2003)
Lauesen, S.: User interface design - a software engineering perspective. Addison-Wesley, Reading (2005)
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
Lauesen, S., Kuhail, M.A.: The use case experiment and the replies (2009), http://www.itu.dk/people/slauesen/
Lilly, S.: Use Case Pitfalls: Top 10 Problems from Real Projects Using Use Cases. IEEE Computer Society, Washington, DC, US (1999)
Maiden, N.A., Ncube, C.: Acquiring COTS software selection requirements. IEEE Software, 46–56 (March/April 1998)
Rosenberg, D., Scott, K.: Top Ten Use Case Mistakes, Software Development (2001), http://www.drdobbs.com/184414701
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)
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
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights 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)