A representational framework for scenarios of system use

Requirements Engineering

Volumn 3, Issue 3-4, 1998, Pages 219-241

  Anton, Annie I ^a   Potts, Colin ^b  

^a North Carolina State University   (United States)

^b Georgia Institute of Technology   (United States)

Author keywords

Design representations; Requirements engineering; Scenarios

Indexed keywords

EID: 54649083255     PISSN: 09473602     EISSN: 1432010X     Source Type: Journal    
DOI: 10.1007/s007660050006     Document Type: Article

References (43)

1. Andersen JS, Durney B. Using scenarios in deficiency-driven requirements engineering. In: IEEE International Symposium on Requirements Engineering (RE '93), San Diego, CA, January 1993, pp 134-141
2. Anton AI, McCracken WM, Potts C. Goal decomposition and scenarios analysis in business process reengineering. In: Advanced information systems engineering: 6th international conference, CAiSE '94 Proceedings, Utrecht, The Netherlands, June 1994, pp 94-104
3. Anton AI. Goal-based requirements analysis. In: International conference on requirements engineering (ICRE '96), Colorado Springs, CO, April 1996, pp 136-144
4. Anton AI. Goal identification and refinement in the specification of software-based information systems. PhD dissertation, Georgia Institute of Technology, Atlanta, GA, June 1997
5. Anton AI, Potts C. The use of goals to surface requirements for evolving systems. In: International conference on software engineering (ICSE '98), Kyoto, Japan, 19-25 April 1998, pp 157-166
6. Benner K, Feather MS, Johnson WL, Zorman L. Utilizing scenarios in the software development process. In: IFIP WG 8.1 working conference on information systems development processes, North Holland, 1993, pp 117-314
7. Breitman KK, Sampaio de Prado Leite JC. A framework for scenario evolution. In: International conference on requirements engineering (ICRE '98), Colorado Springs, CO, 6-10 April 1998, pp 214-221
8. Carroll JM, Rosson M. Getting around the task-artifact cycle: how to make claims and design by scenario. ACM Trans Inform Syst 1992;10(2): 181-212
9. Jacobson I, Christerson M, Jonsson P, Övergaard G. Objectoriented software engineering: a use case driven approach. Addison-Wesley, Reading, MA, 1992
10. Potts C. Using schematic scenarios to understand user needs. In: Symposium on designing interactive systems: processes, practices, methods and techniques, University of Michigan, Ann Arbor, MI, August 1995, pp 247-256
11. Rubin KS, Goldberg A. Object behavior analysis. Commun ACM 1992;35(9): 48-62
12. Texel PP, Williams CB. Use cases combined with Booch, OMT, UML: process and products. Prentice-Hall, Englewood Cliffs, NJ, 1997
13. Weidenhaupt K, Pohl K, Jarke M, Haumer P, CREWS team. Scenarios in system development: current practice. IEEE Software 15(2), pp 34-45, March 1998
14. Jackson M. Software requirements and specifications. AddisonWesley, Reading, MA, 1995
15. Ringland G. Scenario planning: managing for the future. Wiley, Chichester, UK, 1998
16. Schwartz P. The art of the long view. Doubleday, Garden City, NY, 1991
17. van der Heijden K. Scenarios: the art of strategic conversation. Wiley, Chichester, 1996
18. Waltre M. Scenario analysis: an approach to organisational learning. Report no 96-027, Department of Computer and System Sciences, Stockholm University/Royal Institute of Technology, November 1996
19. Kazman R, Abowd G, Bass L, Clements P. Scenario-based analysis of software architecture. IEEE Software 1996; November: 47-55
20. Dardenne A. On the use of scenarios in requirements acquisition. Technical report CIS-TR-93-17, University of Oregon, Eugene, OR, 1993
21. Hix D, Hartson HR. Developing user interfaces: ensuring usability through product and process. Wiley, New York, 1993
22. Coad P, Yourdon E. Object-oriented design. Prentice-Hall, Englewood Cliffs, NJ, 1991
23. Rolland C, Achour B, Cauvet C, Ralyté J, Sutcliffe A, Maiden N, Jarke M, Haumer P, Pohl K, Dubois E, Heymans P. A proposal for a scenario classification framework. Requirements Eng 1998;3(1): 23-47
24. Wirfs-Brock R. Designing objects and their interactions: a brief look at responsibility-driven design. In: Carroll JM (ed). Scenario-based design: envisioning work and technology in system development. Wiley, New York, 1995, pp 337-360
25. Booch G. Object-oriented analysis and design with applications (2nd edn). Benjamin/Cummings, Redwood City, CA, 1994
26. Fowler M. UML distilled: applying the standard object modeling notation. Addison-Wesley, Reading, MA, 1997
27. Rumbaugh J, Blaha M, Premerlani W, Eddy F, Lorenzen W. Object-oriented modeling and design. Prentice-Hall, Englewood Cliffs, NJ, 1991
28. Lubars M, Potts C, Richter C. Developing initial OOA Models. In: Proceedings of the 15th international conference on software engineering. ACM/IEEE Computer Society Press, Los Alamitos, CA, 1993, pp 255-264
29. Potts C, Takahashi K, Anton AI. inquiry-based requirements analysis. IEEE Software 1994;1l(2): 21-32
30. Takahashi K, Yamamoto Y. An analysis of traceability in requirements documents. IEICE Trans Inform Syst 1995;E78D(4):393-402
31. Heitmeyer C, Labaw B, Kiskis D. Consistency checking of SCRstyle requirements specifications. In: Proceedings of the 2nd international symposium on requirements engineering (RE '95), York, UK, March 1995, pp 56-63
32. Takahashi K. Hypermedia support for requirements analysis. PhD thesis, University of Tokyo, Japan, 1997
33. Card S, Moran T, Newell A. The psychology of human-computer interaction. Erlbaum, Hillsdale, NJ, 1983
34. Kieras DE. Toward a practical GOMS model methodology for user interface design. In: Helander M (ed). Handbook of human-computer interaction. North-Holland, Amsterdam, 1988, pp 135158
35. Kurke MI. Operational sequence diagrams in system design. Human Factors 1961;3: 66-73
36. Ehn P. Work-oriented design of computer artifacts (2nd edn) Erlbaum, Hillsdale, NJ, 1989
37. Muller M, Tudor LG, Wildman DM, White EA, Root RW, Dayton T, Carr R, Diekmann B, Dykstra-Erickson E. Bifocal tools for scenarios and representations in participatory activities with users. In: Carroll JM (ed). Scenario-based design: envisioning work and technology in system development. Wiley, New York, 1995, pp 135-163
38. Beyer H, Holtzblatt K. Contextual design: defining customercentered systems. Morgan-Kaufmann, San Francisco, CA, 1998
39. Checkland PB, Scholes J. Soft systems methodology in action. Wiley, Chichester, 1990
40. Morgan G. Images of organization (2nd edn). Sage, Newbury Park, CA, 1997
41. Jacobson I, Ericsson M, Jacobson A. The object advantage: business process reengineering with object technology. AddisonWesley, Wokingham, UK, 1995
42. Carroll JM, Rosson MB. Narrowing the specification implementation gap in scenario-based design. In: Carroll JM (ed). Scenariobased design: envisioning work and technology in system development. Wiley, New York, 1995, pp 247-279
43. Hsia P, Samuel J, Gao J, Kung D, Totyshima Y, Chen C. Formal approach to scenario analysis, IEEE Software 1994;11(2):33-41