Skip to main content

Advertisement

Log in

Goal and scenario validation: a fluent combination

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

Abstract

Scenarios and goals are effective techniques for requirements definition. Goals are objectives that a system has to meet. They are elaborated into a structure that decomposes declarative goals into goals that can be formulated in terms of events and can be controlled or monitored by the system. Scenarios are operational examples of system usage. Validation of goals and scenarios is essential in order to ensure that they represent what stakeholders actually want. Rather than validating scenarios and goals separately, possibly driving the elaboration of one through the validation of another, this paper exploits the relationship between goals and scenarios. The aim is to provide effective graphical animations as a means of supporting such a validation. The relation between scenarios and goals is established by means of fluents that describe how events of the operational description change the state of the basic propositions from which goals are expressed. Graphical animations are specified in terms of fluents and driven by a behaviour model synthesised from the operational scenarios. In addition, goal model checking over operational scenarios is provided to guide animations through goal violation traces.

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

Access this article

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.

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

References

  1. ITU (2000) Message sequence charts. International Telecommunications Union. Telecommunication Standardisation Sector Recommendation Z.120

  2. Object Management Group (2004) Unified modeling language (UML). http://www.omg.org/technology/documents/modeling_spec_catalog.htm#UML

  3. Lamsweerde AV (2001) Goal-oriented requirements engineering: a guided tour. In: 5th IEEE international symposium on requirements engineering (RE’01), Toronto

  4. Dardenne A, van Lamsweerde A, Fickas S (1993) Goal-directed requirements acquisition. Sci Comput Program 20:3–50

    Article  MATH  Google Scholar 

  5. Feather M (1987) Language support for the specification and development of composite systems. ACM Trans Program Lang Syst 9(2):198–234

    Article  Google Scholar 

  6. Lamsweerde AV (1998) Willemet L inferring declarative requirements specifications from operational scenarios. IEEE Trans Softw Eng 24(12):1089–1114

    Article  Google Scholar 

  7. Nuseibeh B, Easterbrook S (2000) Requirements engineering: a roadmap. In: International conference on software engineering (ICSE-2000), Limerick

  8. Giannakopoulou D, Magee J (2003) Fluent model checking for event-based systems. In: 4th joint meeting of the European software engineering conference and ACM SIGSOFT symposium on the foundations of software engineering (ESEC/FSE 2003), Helsinki

  9. Miller R, Shanahan M (1999) The event calculus in classical logic—alternative axiomatisations. Linkoping Electron Art Comput Inform Sci 4(16):1–27

    Google Scholar 

  10. Uchitel S (2003) Elaboration of behaviour models and scenario based specifications using implied scenarios. Ph.D. Thesis in Department of Computing, Imperial College London, London

  11. Keller R (1976) Formal verification of parallel programs, Commun ACM 19(7):371–384

    Article  MATH  Google Scholar 

  12. Hoare CAR (1985) Communicating sequential processes. Prentice Hall, Englewood Cliffs

    MATH  Google Scholar 

  13. Magee J, Kramer J (1999) Concurrency: state models and Java programs. Wiley, New York

    MATH  Google Scholar 

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

    Article  Google Scholar 

  15. Jackson M (2004) Seeing more of the world. IEEE Softw 21(6):83–85

    Article  Google Scholar 

  16. Jackson M (1995) Software requirements and specifications—a lexicon of practice, principles and prejudices. ACM Press, Addison-Wesley, New York, Reading

    Google Scholar 

  17. Magee et al (2003) The LTSA site, www.doc.ic.ac.uk/ltsa

  18. Heitmeyer C, Kirby C, Labaw B (1997) The SCR method for formally specifying, verifying and validating requirements: tool support. In: 19th International conference on software engineering (ICSE’97), Boston

  19. Halbwachs N Caspi P, Raymond P, Pilaud D (1991) The synchronous data-flow programming language LUSTRE. Proc IEEE, 79:1305–1320

    Article  Google Scholar 

  20. Berry G, Gonthier G (1992) The Esterel synchronous programming language: design, semantics, implementation. Sci Comput Program 19(2):87–152

    Article  MATH  Google Scholar 

  21. Darimont R, Lamsweerde AV (1996) Formal refinement patterns for goal-driven requirements elaboration. In: 4th ACM symposium on the foundations of software engineering, San Fransisco

  22. Holzmann GJ, Peled D (1996) The state of spin. In: CAV’96

  23. Harel D, Lachover H, Naamad A, Pnueli A, Politi M, Sheman R, Shtul-Trauring A, Trakhtenbrot M (1990) STATEMATE: a working environment for the development of complex reactive systems. IEEE Trans Softw Eng 16:403–414

    Article  Google Scholar 

  24. Harel D, Marelly R (2003) Come, let’s play: scenario-based programming using LSCs and the play-engine. Springer, Berlin, Heidelberg, New York

    Google Scholar 

  25. Magee J, Kramer J, Giannakopoulou D, Pryce N (2000) Graphical animation of behavior models. In: 22nd International conference on software engineering (ICSE’00), Limerick

  26. Magee J, Uchitel S, Chatley R, Kramer J (2003) Visual methods for Web application design. In: Tech note at the symposium on visual and multimedia software engineering, IEEE symposia on human-centric computing languages and environments (HCC), Auckland

  27. CREWS (1999) Cooperative requirements engineering with scenarios, http://Sunsite.Informatik.RWTH-Aachen.DE/CREWS

  28. Sutcliffe A (1997) A technique combination approach to requirements engineering. In: 3rd IEEE international symposium on requirements engineering, Los Alamitos

  29. Potts C, Takahashi K, Anton AI (1994) Inquiry-based requirements analysis. IEEE Softw 11(2):21–32

    Article  Google Scholar 

  30. Leite J, Freeman PA (1991) Requirements validation through viewpoint resolution. IEEE Trans Softw Eng 12(12):1253–1269

    Article  Google Scholar 

  31. Nuseibeh B, Kramer J, Finkelstein A (1994) A framework for expressing the relationships between multiple views in requirements specification. Trans Softw Eng 20(10):760–773

    Article  Google Scholar 

  32. Nuseibeh B (2001) Weaving together requirements and architecture. IEEE Comput 34(3):115–117

    Google Scholar 

  33. Letier E (2001) Reasoning about agents in goal-oriented requirements engineering. PhD Thesis, Université Catholique de Louvain

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Sebastian Uchitel.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Uchitel, S., Chatley, R., Kramer, J. et al. Goal and scenario validation: a fluent combination. Requirements Eng 11, 123–137 (2006). https://doi.org/10.1007/s00766-005-0024-3

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-005-0024-3

Keywords