Skip to main content
SpringerLink
Log in

Designing with scenarios: A critical review of current research and practice

  • Published:
Requirements Engineering Aims and scope Submit manuscript

Abstract

There is a great deal of requirements engineering specifically, and information systems development research in general, in the area of scenarios as the ‘vocabulary’ for discussing and characterising designs for new artefacts. This is partly due to opening up the design process to a variety of participants in a project, and making explicit their ways of working, thinking and interactions with the design products. Scenarios, being concrete, and easy to understand and use, provide the means to describe the design vocabulary. They are used to focus on episodic cases, exchange ideas and thoughts about them effectively, and generally describe requirements and designs for a new artefact from the user’s perspective. In this paper, we review the effectiveness of the current state-of-practice in scenario-based approaches. The objective of this evaluation exercise is to define the requirements for improved ‘by scenario’ approaches to cope with requirements and designs for developing new artefacts.

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

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

References

  1. Loucopoulos P, Louridas P, Kavakli V, Tzanaki A, Filippidou D. The enterprise requirements analysis (ERA) approach (ISE-96-4). UMIST, Information Systems Group, Manchester, UK, 1996

    Google Scholar 

  2. Filippidou D, Loucopoulos P. Using scenarios to validate requirements in a plausibility centred approach. Paper presented at the CAiSE ’97, Barcelona, Spain, 1997

  3. Holbrook CH. A scenario-based methodology for conducting requirements elicitation. ACM SIGSOFT Software Eng Notes 1990;15(1):95–104

    Article  Google Scholar 

  4. Carroll JM, Rosson MB. Getting around the task-artifact cycle: how to make claims and design by scenarios. ACM Trans Inform Syst 1992;10(2):181–212

    Article  Google Scholar 

  5. Potts C. Requirements completeness, enterprise goals and scenarios. Dagshtull, 1994

  6. Rauterberg M, Strohm O. About the benefits of user-oriented requirements engineering. Paper presented at the 1st international workshop on requirements engineering: foundation of software quality REFSQ ’94, Utrecht, The Netherlands, 1994

  7. Nardi BA. The use of scenarios in design. SIGCHI Bull 1992;24(4):13–14

    Article  Google Scholar 

  8. Anderson JS, Durney B. Using scenarios in deficiency-driven requirements engineering. Paper presented at the IEEE international symposium on requirements engineering (RE ’93). San Diego, CA. 1993

  9. Wright P. What’s in a scenario? SIGCHI Bull 1992;24(4):11

    Article  Google Scholar 

  10. Erickson T. Notes on design practice: stories and proto-types as katalysts for communication. In: Carroll JM (ed). Scenario-based design: envisioning work and technology in system development. Wiley. New York, 1995, pp 37–58

    Google Scholar 

  11. Kyng M. Creating contexts for design. In: Carroll JM (ed.) Scenario-based design: envisioning work and technology in system development. Wiley. New York, 1995, pp 85–107

    Google Scholar 

  12. 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

    Google Scholar 

  13. Kutti K. Work processes: scenarios as a preliminary vocabulary. In: Carroll JM (ed). Scenario-based design: envisioning work and technology in system development. Wiley, New York, 1995, pp 19–36

    Google Scholar 

  14. Rubin KS, Goldberg A. Object behaviour analysis. Commun ACM 1992;35(9):48–62

    Article  Google Scholar 

  15. Wang W, Hufnagel S, Hsia P, Yang SM. Scenario driven requirement analysis method. Paper presented at ICSI-92, The second international conference on systems integration, Morristown, NJ, COA, 1992

  16. Hsia P, Samuel, J, Gao J, Kung D, Toyoshima Y, Chen C. Formal approach to scenario analysis. IEEE Software 1994;11(2):33–41

    Article  Google Scholar 

  17. Carroll JM. Making use a design representation. Commun ACM 1994;37:29–35

    Article  Google Scholar 

  18. MacLean A, Young RM, Belloti VME, Moran TP. Questions, options, and criteria: elements of design space analysis. Hum-Comput Interact 1991;6(3,4):201–250

    Article  Google Scholar 

  19. Wexelbat A. Report on scenario technology (technical report STP-139-87). MCC, Manchester, UK, 1987

    Google Scholar 

  20. Potts C, Takahashi K, Anton A. Inquiry-based requirements analysis. IEEE Software 1994;11(2):21–32

    Article  Google Scholar 

  21. Carroll JM, Rosson MB. Putting metaphors to work. Paper presented at the Graphics’ Interface ’94, Banff, Canada, 1994

  22. Saxena KBC. Decision scenarios as decision task analysis tools. Paper presented at the 26th international conference on system sciences, Wailea, USA, 1993

  23. Khoo LP, Ho NC, Choa TW. A fuzzy management decision support system for scenario analysis. J Electron Manuf 1994;4(1):1–9

    Article  Google Scholar 

  24. Bunn D, Salo A. Forecasting with scenarios. Eur J Op Res 1993;68:291–303

    Article  Google Scholar 

  25. Young R, Barnard P. The use of scenarios in human-computer interaction research: turbocharging the tortoise of cumulative science. Paper presented at the CHI+GI ’87 human factors in computing systems and graphics interface, Toronto, 1987

  26. Karat J, Bennett JB. Using scenarios in design meetings—a case study example. In: Karat J (ed.) Taking design seriously: practical techniques for human-computer interaction design. Academic Press. Boston, MA, 1991, pp 63–94

    Google Scholar 

  27. Millett SM. How scenarios trigger strategic thinking. Long Range Planning 1988;21(5):61–68

    Article  Google Scholar 

  28. Ogawa R, Harada H, Kaneko A. Scenario-based hypermedia: a model and a system. Paper presented at the European conference on hypertext, ECHT ’90, INRIA, France, November 1990

  29. Ogawa R, Tanaka E, Taguchi D, Harada K. Design strategies for scenario-based hypermedia: description of its structure, dynamics, and style. Paper presented at the ECHT ’92 ACM conference on hypertext. Milan, Italy. 30 November–4 December 1992

  30. Roman G-C. A taxonomy of current issues in requirements engineering. IEEE Comput 1985;18(April):14–23

    Google Scholar 

  31. Hooper JC, Hsia P. Scenario-based prototyping for requirements identification. Software Eng Notes 1982;December:88–93

    Article  Google Scholar 

  32. Glinz M. An integrated formal model of scenarios based on state-charts. Paper presented at the 5th European software engineering conference, Sitges, Spain, 1995

  33. Harel D. Statecharts: a visual formalism for complex systems. Scie. Comput Program 1987;8:231–274

    Article  MATH  MathSciNet  Google Scholar 

  34. Regnell B, Kimbler K, Wesslen A. Improving the use case driven approach to requirements engineering. Paper presented at the RE ’95, York, UK, 1995

  35. Jacobson I. The use-case construct in object-oriented software engineering. In JM Carroll (ed.), Scenario-based design: envisioning work and technology in system development, pp. 309–336. John Wiley & Sons, Inc., 1995

  36. Gough PA, Fodemski FT, Higgins SA, Ray SJ. Scenarios: an industrial case study and hypermedia enhancements. Paper presented at the RE ’95, York, UK, 1995

  37. Rumbaugh J, Blaha M, Premerlani W, Eddy F, Lorensen W. Object-oriented modelling and design. Prentice-Hall, Englewood Cliffs, NJ, 1991

    Google Scholar 

  38. Christel MG, Wood DP, Stevens SM. AMORE: the advanced multimedia organizer for requirements elicitation (Technical report ESC-TR-93-189). Carnegie-Mellon University, Software Engineering Institute, 1993

  39. Wood DP, Christel MG, Stevens SM. A multimedia approach to requirements capture and modeling. Paper presented at the 1st international conference on requirements engineering ICRE, Colorado Springs, CO, 1994

  40. Lalioti V, Loucopoulos P. Visualisation of conceptual specifications. Information Syst 1994;19(3):291–309

    Article  Google Scholar 

  41. Rosson MB, Carroll JM. Narrowing the specification-implementation gap in scenario-based design. In: Carroll JM (ed). Scenario-based design: envisioning work and technology in system development. Wiley, New York, 1995, pp 247–278

    Google Scholar 

  42. Lalioti V. Animation for validation of business system specification. Paper presented at the 30th annual Hawaii international conference on system sciences, Hawaii, 1997

  43. Benner KM, Feather MS, Johnson WL, Zorman LA. Utilizing scenarios in the software development process. Paper presented at the IFIP ’93, Holland, 1993

  44. Johnson WL, Feather M, Harris DR. Representation and presentation of requirements knowledge. IEEE Trans Software Eng 1992;18(10):853–869

    Article  Google Scholar 

  45. Christel MG, Wood DP, Stevens SM. Applying multimedia technology to requirements engineering. Paper presented at the 6th annual software technology conference, Salt Lake City, UT, 1994.

  46. MacLean A, McKerlie D. Design space analysis and use representations. In: Carroll JM (ed). Scenario-based design: envisioning work and technology in system development. Wiley New York, 1995, pp. 183–207

    Google Scholar 

  47. Carroll JM, Rosson MB. Human computer interaction scenarios as a design representation. In HICSS-23: Hawaii International Conference on System Sciences. 1990. Los Alamitos, CA: IEEE Computer Society Press, pp. 555–561.

    Google Scholar 

  48. Peck S. A generic model for scenario analysis and modeling. In: MC Jackson et al (eds). Systems thinking in Europe. Plenum Press, New York, 1991.

    Google Scholar 

  49. Regnell B, Andersson, M, Bergstrand J. A hierarchical use case model with graphical representation. Paper presented at the ECBS ’96, Friedrichshafen, Germany, 1996

  50. Jacobson I. The use-case construct in object-oriented software engineering. In: Carroll JM (ed.) Scenario-based design: envisioning work and technology in system development. Wiley, New York, 1995, pp. 309–336.

    Google Scholar 

  51. Carroll JM (ed). Scenario-based design: envisioning work and technology in system development. Wiley, New York, 1995

    Google Scholar 

  52. Haddock G, Harbison K. From scenarios to domain models: processes and representations (open system architecture). Paper presented at the SPIE-The International Society for Optical Engineering, USA, 1994

  53. Haddock G. The scenario-based engineering process: a lifecycle incorporating formalisms, methodologies and tools into domain specific software architectures. University of Texas at Arlington, TX, 1993

    Google Scholar 

  54. Dardenne A, Lamsweerde A v, Fickas S. Goal-directed requirements acquisition. Sci Comput Program 1993;20:3–50.

    Article  MATH  Google Scholar 

  55. Anton AI, McCracken WM, Potts C. Goal decomposition and scenario analysis in business process reengineering. Paper presented at the 6th international conference on advanced information systems engineering (CAiSE ’94), Utrecht, The Netherlands, 1994

  56. Rolland C, Anchour CB, Cauvet C, Ralyte J, Satcliffe A, Maiden NAM, Jarke M, Hanmer P, Pohl K, Dubois E, Heymans P. A proposal for a scenario classification framework (CREWS Report 96-01)

  57. Finkelstein A. Is application development focused on real problems? IFIP Trans Comput Sci Technol 1994; A53:448–450.

    Google Scholar 

  58. Jones JC. Design methods, 2nd edn. Chapman & Hall, London, 1992.

    Google Scholar 

  59. CAA. Civil Aviation Authority. A report on the supplying by the Authority of navigation and air traffic control services to civil aircraft. HMSO, London, 1983; Special issue on participatory design. Commun ACM 1993;36(4)

    Google Scholar 

  60. Carroll JM. The scenario perspective in system development. In: Carroll JM (ed). Scenario-based design: envisioning work and technology in system development. Wiley, New York, pp 1–17.

  61. Cross N (ed). Developments in design methodology. Wiley, Chichester, 1984

    Google Scholar 

  62. Simon HA. The structure of ill-structured problems. In: Cross N (ed). Developments in design methodology. Wiley, New York, 1984, pp 146–166.

    Google Scholar 

  63. Rittel HW, Webber MM. Planning problems are wicked problems. In Cross N (ed.) Developments in design methodology. Wiley, New York, 1984, pp 135–144

    Google Scholar 

  64. Alexander C, Polymer B. The atoms of environmental structure. In: Cross N (ed). Developments in design methodology, Wiley, New York, 1984, pp. 123–133.

    Google Scholar 

  65. Floyd C. Outline of a paradigm change in software engineering. ACM SIGSOFT Software Eng Notes 1988; 13(2): 25–38.

    Article  MathSciNet  Google Scholar 

  66. Siddiqi J. Challenging universal truths of requirements engineering. IEEE Software 1994; March: 18–19.

    Article  Google Scholar 

  67. Goguen J. Requirements engineering: reconciliation of technical and social issues (technical report). Oxford University Computing Lab, Oxford, 1992

    Google Scholar 

  68. Schön DA. The reflective practitioner: how professionals think in action. Basic Books. New York, 1983

    Google Scholar 

  69. Schön DA. Educating the reflective practitioner. Jossey-Bass, San Francisco, 1987

    Google Scholar 

  70. Polanyi M. Personal knowledge: towards a post-critical philosophy. University of Chicago Press, Chicago, IL, 1958

    Google Scholar 

  71. Polanyi M. The tacit dimension. Doubleday, New York, 1966

    Google Scholar 

  72. Dreyfus HL. Being-in-the-world: a commentary on Heidegger’s being and time, division 1. MIT Press, Cambridge, MA, 1991

    Google Scholar 

  73. Hillier B, Musgrove J, O’Sullivan P. Knowledge and design. In: Cross N (ed). Developments in design methodology. Wiley, New York, 1984, pp 245–264

    Google Scholar 

  74. 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–3600

    Google Scholar 

  75. Coad P, Yourdon E. Object-oriented analysis. Yourdon Press, Englewood Cliffs, NJ, 1991

    Google Scholar 

  76. Hsia P, Young A. Screen-based scenario generator: a tool for scenario-based prototyping. Paper presented at the Hawaii international conference on system sciences, Hawaii, 1988.

  77. Filippidou D. SEED: scenario-based experimentations to evaluating designs. PhD thesis, UMIST, Department of Computation, August 1997

  78. Kavakli E, Loucopoulos P, Filippidou D. Using scenarios to systematically support goal-directed elaboration for information systems requirements. Paper presented at the ECBS ’96, Friedrichshafen, Germany, 1996

Download references

Author information

Authors and Affiliations

  1. Datel Advanced Systems Ltd, Datel House, Caspian Road, Atlantic Street, WA14 5HH, Altrincham, UK

    Despina Filippidou

Authors
  1. Despina Filippidou
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Despina Filippidou.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Filippidou, D. Designing with scenarios: A critical review of current research and practice. Requirements Eng 3, 1–22 (1998). https://doi.org/10.1007/BF02802918

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1007/BF02802918

Keywords

Search

Navigation