Skip to main content
Springer Nature Link
Log in

Supporting scenario evolution

  • Original Article
  • Published:
Requirements Engineering Aims and scope Submit manuscript

Abstract

Scenarios have been shown to be very helpful in identifying and communicating requirements for computer-based systems (CBSs). However, they appear not to be applicable to the rest of the CBS development process. Making scenarios more useful for the entire software development lifecycle requires integrating scenarios to other representations used during CBS development. This integration is achieved with tracing technology. Having integrated scenarios into the entire software development lifecycle creates the necessity to maintain scenarios through the inevitable changes that they and other documents undergo and to subject them to configuration management. We have prototyped automated support for full-lifecycle scenario management and have applied it to some non-trivial systems.

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

Access this article

Log in via an institution

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

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

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8
Fig. 9
Fig. 10
Fig. 11
Fig. 12
Fig. 13
Fig. 14
Fig. 15

Similar content being viewed by others

Notes

  1. We use the correct term for the process, “tracing” [32], rather than the more popular, but incorrect term “traceability”, which means only “the ability to trace”.

  2. CaliberRM is a trade mark of Borland Corporation.

References

  1. Alexander I (2001) Capturing use cases with DOORS. In: Proceedings of the 5th IEEE international symposium on requirements engineering (RE 2001), Toronto, Canada, August 2001, p 264

  2. Antón A, Potts CA (1998) Representational framework for scenarios of system use. Requirements Eng 3(3–4):219–241

    Google Scholar 

  3. Armour F, Miller G (2001) Advanced use case modeling. Addison Wesley, Reading, Massachusetts

    Google Scholar 

  4. Bersoff E, Henderson V, Siegel S (1980) Software configuration management. Prentice-Hall, Englewood Cliffs, New Jersey

    Google Scholar 

  5. Rumbaugh J, Jacobson I, Booch G (1999) The unified modeling language reference manual. Addison-Wesley, Reading, Massachusetts

    Google Scholar 

  6. CaliberRM (2003) Collaborative requirements management system. Borland Corporation, available at http://www.borland.com/caliber/

  7. Breitman KK (2000) Evolução de Cenários. PhD dissertation, Departamento de Informática, PUC-Rio, Brazil

  8. Breitman KK, Leite JCSP (2000) Scenario evolution: a closer view on relationships. In: Proceedings of the 4th international conference on requirements engineering (ICRE 2000), Schaumburg, Illinois, June 2000, pp 102–111

  9. Breitman KK, Leite JCSP (1998) Suporte Automatizado à Gerência da Evolução de Cenários. In: I Workshop de Engenharia de Requisitos (WER’98), Maringá, Paraná, Brasil, October 1998, pp 49–56

  10. Breitman KK, Leite JCSP (1998) A framework for scenario evolution. In: Proceedings of the 3rd international conference on requirements engineering (ICRE’98), Colorado Springs, Colorado, April 1998, pp 214–221

  11. Breitman KK, Leite JCSP (1999) Processo de Software Baseado em Cenários. In: II (Ibero-American) workshop on requirements engineering (WER’99), Buenos Aires, Argentina, September 1999, pp 95–105

  12. Bullock G (1998) Rational product integration focus: Rose and Requisite Pro. Rational Software Corporation, available at http://www-106.ibm.com/developerworks/rational/library/content/RationalEdge/rosearchitect/ra_fall1998.pdf

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

    Google Scholar 

  14. Carroll JM (2000) Making use: scenario-based design of human–computer interactions. MIT Press, Cambridge, Massachusetts

    Google Scholar 

  15. Cockburn A (2001) Writing effective use cases. Addison-Wesley, Reading, Massachusetts

    Google Scholar 

  16. Conklin J, Begemann M (1988) gIBIS: a hypertext tool for exploratory policy discussion. ACM Trans Office Inf Syst 6:303–331

    Article  Google Scholar 

  17. Conradi R, Westfechtel B (1998) Version models for software configuration management. ACM Comput Surv 30(2):232–282

    Article  Google Scholar 

  18. Date CJ (2000) An introduction to database systems, 7th edn. Addison-Wesley, Reading, Massachusetts

    Google Scholar 

  19. Dömges R, Pohl K (1998) Adapting traceability environments to project-specific needs. Commun ACM 41(12):54–63

    Article  Google Scholar 

  20. Börger E, Hörger B, Parnas D, Rombach D (1999) Requirements capture, documentation and validation. Schloss Dagstuhl seminar report no. 99241, 13–16 June 1999, report no. 242

  21. Filippidou D (1998) Designing with scenarios: a critical view of current research and practice. Requirements Eng 3(1):1–22

    Google Scholar 

  22. Ghezzi C, Jazayeri M, Mandrioli D (1991) Fundamentals of software engineering. Prentice-Hall, Englewood Cliffs, New Jersey

    Google Scholar 

  23. Gotel O, Finkelstein A (1993) An analysis of the requirements traceability problem. Department of Computing, Imperial College of Science, Technology and Medicine, London, technical report TR-93-41

  24. Haumer P, Pohl K, Weidenhaupt K (1998) Requirements elicitation and validation with real world scenes. Trans Softw Eng 24(12):1036–1054

    Article  Google Scholar 

  25. Haumer P, Heymans P, Jarke M, Pohl K (1999) Bridging the gap between past and future in RE: a scenario-based approach. In: Proceedings of the 4th international symposium on requirements engineering (RE’99), Limerick, Ireland, June 1999, pp 66–73

  26. Hicks D, Leggett J, Nürnberg P, Schnanse JA (1998) A hypermedia version control framework. ACM Trans Inf Syst 16(2):127–160

    Article  Google Scholar 

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

    Article  Google Scholar 

  28. Humphrey WA (1995) A discipline for software engineering. SEI series in software engineering. Addison-Wesley, Reading, Massachusetts

    Google Scholar 

  29. Jacobson I, Christerson M, Jonsson P, Overgaard G (1992) Object-oriented software engineering: a use case driven approach. Addison-Wesley, Reading, Massachusetts

    Google Scholar 

  30. Jarke M, Pohl K, Dömges R, Jacobs S, Nissen HW (1994) Requirements information management: the NATURE approach. Ingenerie des Systemes d’Informations (special issue on requirements engineering) 2:6

    Google Scholar 

  31. Jarke M, Tung Bui X, Carroll JM (1998) Scenario management: an interdisciplinary approach. Requirements Eng 3(3–4):155–173

    Article  Google Scholar 

  32. Jarke M (1998) Requirements tracing. Commun ACM 41(12):32–36

    Article  Google Scholar 

  33. Kulak D, Guiney E (2000) Use cases: requirements in context. Addison-Wesley, Reading, Massachusetts

    Google Scholar 

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

    Google Scholar 

  35. Leffingwell D, Widrig D (2000) Managing software requirements: a unified approach. Addison-Wesley, Reading, Massachusetts

    Google Scholar 

  36. Leite JCSP, Franco APM (1993) A strategy for conceptual model acquisition. In: Proceedings of the IEEE international symposium on requirements engineering (RE’93), San Diego, California, January 2003, pp 243–246

  37. Leite JCSP, Oliveira AP (1995) A client-oriented requirements baseline. In: Proceedings of the 2nd IEEE international symposium on requirements engineering (RE’95), York, England, March 1995, pp 108–115

  38. Leite JCSP, Rossi G, Maiorana V, Balaguer F, Kaplan G, Hadad G, Oliversos A (1997) Enhancing a requirements baseline with scenarios. Requirements Eng 2(4):185–198

    Google Scholar 

  39. Leite JCSP, Hadad GDS, Doorn JH, Kaplan GN (2000) A scenario construction process. Requirements Eng 5(1):38–61

    Google Scholar 

  40. Leonardi-Maiorana V, Balaguer F (1997) Una Estrategia de Analisis Orientada a Objetos Baseada em Escenarios. Anais da II Jornadas de Ingernieria de Software JIS’97, Donostia, San Sebastian, Spain

  41. Maiden NAM, Minocha S, Manning K, Ryan M (1998) CREWS-SAVRE: systematic scenario generation and use. In: Proceedings of the international conference on requirements engineering (ICRE’98), Colorado Springs, Colorado, April 1998, pp 148–155

  42. McGraw K, Harbison K (1997) User-centered requirements: the scenario-based engineering process. Laurence Erlbaum, Mahwah, New Jersey

    Google Scholar 

  43. Mikkelsen T, Pherigo S (1997) Practical software configuration management: the latenight developer’s handbook Hewlett-Packard Professional Books, Prentice-Hall, Englewood Cliffs, New Jersey

    Google Scholar 

  44. Pohl K (1996) Enabling requirements pre-traceability. In: Proceedings of the 2nd international conference on requirements engineering (ICRE’96), Colorado Springs, Colorado, April 1996, pp 76–85

  45. Potts C, Takahashi K, Antón A (1994) Inquiry-based requirements analysis. IEEE Softw 11(2):21–32

    Google Scholar 

  46. Pressman R (1992) Software engineering: a practitioner’s approach, 3rd edn. McGraw-Hill, New York

    Google Scholar 

  47. Ramesh B, Stubbs C, Edwards M (1995) Implementing requirements traceability: a case study. In: Proceedings of the 2nd IEEE international symposium on requirements engineering (RE’95), York, England, March 1995, pp 89–95

  48. Ramesh B, Jarke M (2001) Toward reference models of requirements traceability. IEEE Trans Softw Eng 27(1):58–93

    Article  Google Scholar 

  49. Ridao M, Doorn J, Leite JCSP (2001) Domain independent regularities in scenarios. In: Proceedings of the 5th IEEE international symposium on requirements engineering (RE 2001), Toronto, Canada, August 2001, pp 120–127

  50. Rolland C, Achour B, Cauvet C, Ralyté J, Sutcliffe A, Maiden N, Jarke M, Haumer P, Pohl K, Dubois E, Heymans PA (1998) Proposal for a scenario classification framework. Requirements Eng 3:23–47

    Google Scholar 

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

    Google Scholar 

  52. Schneider G, Winters J (1998) Applying use cases: a practical guide. Addison-Wesley, Reading, Massachusetts

    Google Scholar 

  53. Scenario evolution example: light control system. Web site of the Departamento de Informática, PUC–Rio, available at http://www.stones.les.inf.puc-rio.br/Karin/exemplo/index.html

  54. Sutcliffe A (1995) Requirements rationales: integrating approaches to requirement analysis. In: Proceedings of the symposium on designing interactive systems: processes, practices, methods, and techniques (DIS’95), Ann Arbor, Michigan, August 1995, pp 33–42

  55. Sutcliffe A (1998) Scenario-based requirements analysis. Requirements Eng 3:48–65

    Google Scholar 

  56. Sutcliffe A, Maiden NAM (1998) Supporting scenario-based requirements engineering. IEEE Trans Softw Eng 24(12):1072–1088

    Google Scholar 

  57. Tichy WF (1982) Design, implementation, and evaluation of a revision control system. In: Proceedings of the 6th international conference on software engineering, Tokyo, Japan, September 1882, pp 58–67

  58. van Lamsweerde A, Darimont R, Letier E (1998) Managing conflicts in goal-driven requirements engineering. IEEE Tran Softw Eng 24(11):908–926

    Google Scholar 

  59. Wasserman AI (1982) Automated tools in the information system development environment. In: Schneider HJ, Wasserman AI (eds) Automated tools for information systems design. Elsevier, Amsterdam, The Netherlands, pp 1–9

    Google Scholar 

  60. Weidenhaupt K, Pohl K, Jarke M, Haumer P (1998) Scenario usage in system development: current practice. IEEE Softw 15(2):34–45

    Article  Google Scholar 

  61. Whirfs-Brock R, Wilkerson B, Wiener L (1990) Designing object-oriented software. Prentice-Hall, Englewood Cliffs, New Jersey

    Google Scholar 

  62. Yeh R, Ng P (1990) Software requirements: a management perspective. In: Dorfman M, Thayer R (eds) System and software requirements engineering. IEEE Computer Society Press, California, pp 450–461

    Google Scholar 

  63. Zorman L (1995) Requirements envisaging through utilizing scenarios: REBUS. PhD dissertation, University of Southern California, Los Angeles, California

    Google Scholar 

Download references

Acknowledgements

The authors thank the anonymous referees of a previous submission of this paper. Breitman was supported in part by a CNPq (Brasil) Doctoral Studies Scholarship. Leite was supported in part by CNPq (Brasil) and by a “Cientista do Nosso Estado” award from Faperj (Brasil). Berry was supported in part by NSERC (Canada) grant number NSERC-RGPIN227055-00.

Author information

Authors and Affiliations

  1. Departamento de Informática, Pontifícia Universidade Católica, Rio de Janeiro, RJ, 22453, Brazil

    Karin Koogan Breitman & Julio Cesar Sampaio do Prado Leite

  2. Computer Science Department, University of Waterloo, Waterloo, ON, Canada, N2L 3G1

    Daniel M. Berry

Authors
  1. Karin Koogan Breitman
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Julio Cesar Sampaio do Prado Leite
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Daniel M. Berry
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Daniel M. Berry.

Additional information

This paper is an amalgamation and extension of the conference papers numbered 8, 9, 10, and 11 in the bibliography of this paper.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Breitman, K.K., Leite, J.C.S.d.P. & Berry, D.M. Supporting scenario evolution. Requirements Eng 10, 112–131 (2005). https://doi.org/10.1007/s00766-004-0199-z

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-004-0199-z

Keywords