Task descriptions versus use cases

Requirements Engineering

Volumn 17, Issue 1, 2012, Pages 3-18

  Lauesen, Soren ^a   Kuhail, Mohammad A ^a  

^a IT UNIVERSITY OF COPENHAGEN   (Denmark)

Author keywords

Agile requirements; COTS; Diffusion of innovation; Interaction design; Software requirements; Task description; Use case; Verification

Indexed keywords

AGILE REQUIREMENTS; COTS; DIFFUSION OF INNOVATION; INTERACTION DESIGN; SOFTWARE REQUIREMENTS; TASK DESCRIPTION;

REQUIREMENTS ENGINEERING; VERIFICATION;

SOFTWARE ENGINEERING;

EID: 84857369483     PISSN: 09473602     EISSN: 1432010X     Source Type: Journal    
DOI: 10.1007/s00766-011-0140-1     Document Type: Article

References (30)

1. Achour CB, Rolland C, Maiden NAM, Souveyet C (1999) Guiding use case authoring: results of an empirical study. In: Proceedings of the 4th IEEE international symposium.
2. Alexander I, Beus-Dukic L (2009) Discovering requirements. Wiley, New York.
3. Armour F, Miller G (2001) Advanced use case modeling. Addison-Wesley, Reading.
4. Checkland PB (1981) Systems thinking, systems practice. Wiley, Chichester.
5. Cockburn A (1997, 2000) Writing effective use cases. Addison-Wesley.
6. Constantine LL, Lockwood LAD (1999) Software for use: a practical guide to the models and methods of usage-centered design. Addison-Wesley, New York.
7. Cox K, Phalp K (2000) Replicating the CREWS use case authoring guidelines. Empir Softw Eng J 5(3): 245-268.
8. IEEE Recommended Practice for Software Requirements Specification, ANSI/IEEE Std. 830 (1998).
9. Jacobson I, Christerson M, Johnsson P, Övergaard G (1992) Object-oriented software engineering-a use case driven approach. Addison-Wesley, Reading.
10. Jacobson I (2003) Use cases: yesterday, today, and tomorrow. IBM Technical Library.
11. Kulak D, Guiney E (2000) Use cases: requirements in context. Addison-Wesley, Reading.
12. Lauesen S (2002) Software requirements-styles and techniques. Addison-Wesley, Reading.
13. Lauesen S (2003) Task descriptions as functional requirements. IEEE Softw 20(2): 58-65.
14. Lauesen S (2005) User interface design-a software engineering perspective. Addison-Wesley, Reading.
15. Lauesen S (2011) Guide to requirements SL-07-Template with examples. ISBN: 978-87-992344-1-7, also on: http://www. itu. dk/people/slauesen/SorenReqs. html#SL-07.
16. Lauesen S, Kuhail MA (2009) The use case experiment and the replies, http://www. itu. dk/people/slauesen/.
17. Lauesen S, Kuhail M (2011) Use cases versus task descriptions. In: Berry D, Franch X (eds) REFSQ 2011, LNCS 6606. Springer, Berlin, pp 106-120.
18. Lauesen S, Soren Lauesen's website: http://www. itu. dk/people/slauesen/ Contains examples of requirements and user interfaces developed with tasks.
19. Lilly S (1999) Use case pitfalls: top 10 problems from real projects using use cases. IEEE Computer Society, Washington.
20. Lim KY (1996) Structured task analysis: an instantiation of the MUSE method for usability engineering. Interact Comput 8(1): 31-50.
21. Maiden NA, Ncube C (1998) Acquiring COTS software selection requirements. IEEE Softw 15(2): 46-56.
22. Polson PG, Lewis CH (1990) Theory-based design for easily learned user interfaces. Hum Comput Interact 5: 191-220.
23. Preece J, Rogers Y, Sharp H (2002) Interaction design-beyond human-computer interaction. Wiley, New York.
24. Robertson S, Robertson J (1999) Mastering the requirements process. Addison-Wesley, Reading.
25. Rogers EM (1962, 1983) Diffusion of innovations. Free Press, New York.
26. Rosenberg D, Scott K (2001) Top ten use case mistakes. Softw Dev. http://www. drdobbs. com/184414701.
27. Sigurardóttir, Hrönn Kold (2010) Project manager for the electronic health record system at the Capital Hospital Association (H: S): draft of PhD thesis.
28. Wiegers KE (2003) Software requirements. Microsoft Press, US.
29. Wirfs-Brock R (1993) Designing scenarios: making the case for a use case framework, Smalltalk report, Nov/Dec, also: http://www. wirfs-brock. com/PDFs/Designing%20Scenarios. pdf.
30. Yourdon E (1989) Modern structured analysis. Prentice Hall, New Jersey.