Rationale-based use case specification

Requirements Engineering

Volumn 7, Issue 1, 2002, Pages 3-19

  Dutoit, Allen H ^a   Paech, Barbara ^b  

^a TECHNICAL UNIVERSITY OF MUNICH   (Germany)

^b FRAUNHOFER IESE   (Germany)

Author keywords

QOC; Qualitative case studies; Rationale management; Requirements specification; Use cases

Indexed keywords

EID: 33645390993     PISSN: 09473602     EISSN: 1432010X     Source Type: Journal    
DOI: 10.1007/s007660200001     Document Type: Article

References (35)

1. Seminar 'Steuergeräte-Design im Automobilbau und in der Industrieautomation'. Haus der Technik, Essen, 24-25 May 2000
2. van Lamsweerde A, Darimont R, Massonet P. Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt. In: International symposium on requirements engineering, 1995, pp 194-203
3. Jacobson I, Christerson M, Jonsson P, Overgaard G. Object-oriented Software engineering - a use case driven approach. Addison-Wesley, Reading, MA, 1992
4. Jacobson I, Booch G, Rumbaugh J. The unified software development process. Addison-Wesley, Reading, MA, 1999
5. Constantine LL, Lockwood LAD. Structure and style in use cases for user interface design. In: van Harmelen M (ed.), Object-oriented user interface design, 2001. Addison Wesley, Harlow, England
6. Buckingham Shum S, Hammond N. Argumentation-based design rationale: what use at what cost? Int J Human-Computer Studies 1994;40:603-652
7. Dutoit AH, Paech B. Rationale management in software engineering. In: Chung X (ed.), Handbook of software engineering and knowledge engineering. World Scientific Publishing, Singapore, 2001
8. Dutoit AH, Paech B. Supporting evolution: rationale in use case driven software development. In: International workshop on requirements engineering: foundations of software quality (REFSQ'2000), Stockholm, June 2000
9. Cockburn A. Writing effective use cases. Addison Wesley, Reading, MA, 2001
10. Diaper D (ed.). Task analysis for human-computer interaction. Ellis Horwood, Chichester, UK, 1989
11. Benutzer-orientierte Gestaltung interaktiver Systeme. Normentwurf, DIN EN ISO 13407, 1998
12. Chung L, Nixon BA, Yu E, Mylopoulos J. Non-functional requirements in software engineering. Kluwer Academic, Boston, MA, 1999
13. Jackson M. Software requirements and specifications. Addison-Wesley, Reading, MA, 1995
14. Kunz W, Rittel H. Issues as elements of information systems. Working paper no. 131, Institut für Grundlagen der Plannung, Universität Stuttgart, Germany, 1970
15. MacLean A, Young RM, Bellotti V, Moran T. Questions, options, and criteria: elements of design space analysis. Human-Computer Interaction 1991;6:201-250.
16. Lee J. Design rationale systems: understanding the issues. IEEE Expert 1997(May-June);78-85
17. Conklin J, Burgess-Yakemovic KC. A process-oriented approach to design rationale. Human-Computer Interaction 1991;6:357-391
18. Lee J. A qualitative decision management system. In: Winston PH, Shellard S (eds), Artificial intelligence at MIT: expanding frontiers, Vol 1. MIT Press, Cambridge, MA, 1990, pp 104-133
19. The Softbicycle Company. QuestMap: the wicked problem solver, http://www.softbicycle.com/
20. Javasoft. Java servlet specification. Javasoft, http://www.javasoft.com/
21. Object Management Group (OMG). XML Meta Interchange (XMI). OMG, November 2000. http://www.omg.org/
22. DOORS. Telelogic. http://www.telelogic.com/index.cfm
23. Bruegge B, Dutoit AH, Kobylinski R, Teubner G. Transatlantic project courses in a university environment. In Asian Pacific software engineering conference, Singapore, December 2000
24. Lilly S. Use case pitfalls: top 10 problems from real projects using use cases. Tools 30 Proceedings, Technol Object-Oriented Language System 1999;174-183
25. Ramesh B, Dhar V. Representing and maintaining process knowledge for large-scale systems development. IEEE Expert 1994;April:54-59
26. Ramesh B, Sengupta K. Multimedia in a design rationale decision support system. Decision Support Systems 1995, pp 181-196
27. Ramesh B, Tiwana A. Supporting collaborative process knowledge management in new product development teams. Decision Support Systems 1999;27:213-235
28. Potts C, Takahashi K, Anton AI. Inquiry-based requirements analysis. IEEE Software 1994;11(2):21-32
29. Potts C. ScenIC: a strategy for inquiry-driven requirements determination. In: International symposium on requirements engineering, RE'99, 1999, pp 58-65
30. Sutcliffe A. Requirements rationales: integrating approaches to requirement analysis. In: Olson GM, Schuon S (eds), Proceedings of designing interactive systems, DIS'95. ACM Press, New York, 1995, pp 33-42
31. Sutcliffe A, Ryan M. Experience with SCRAM, a scenario requirements analysis method. In: Proceedings of the third international conference on requirements engineering, April 1998, pp 164-171
32. Boehm B, Egyed A, Kwan J, Port D, Shah A, Madachy R. Using the winwin spiral model: a case study. IEEE Computer 1998;July:33-44
33. Nguyen L, Swatman PA, Shanks G. Using design explanation within the formal object-oriented method. Requirements Eng 1999;4:152-164
34. Nguyen L, Swatman PA. Managing the requirements engineering process. In: Seventh international workshop on requirements engineering: foundation for software quality, Interlaken, Switzerland. 2001
35. Anton A, Potts C. The use of goals to surface requirements for evolving systems. In: International conference on software engineering, Kyoto, 1998, pp 157-166