Method Enhancement with Scenario Based Techniques

  • Jolita Ralyté
  • Colette Rolland
  • Véronique Plihon
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1626)


Scenarios have proven useful to elicit, validate and document requirements but cannot be used in isolation. Our concern in this paper is to integrate scenario-based techniques in existing methods. We propose a set of operators to support such an integration. This set is classified in two sub-sets: the one dealing with the integration of the product models of the two initial methods and the one concerned with the integration of their process models. The operators are used to integrate the CREWS-L’Ecritoire approach with the OOSE method. This leads to enhance the use case model construction of the OOSE method with on one hand, the linguistic techniques for scenario authoring and formalisation and on the other hand, the discovery strategies to elicit requirements by scenario analysis of the CREWS-L’Ecritoire approach.


Product Model Case Model Requirement Engineer Method Enhancement Discovery Strategy 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. 1.
    I. Jacobson, M. Christerson, P. Jonsson and G. Oevergaard, Object Oriented Software Engineering: a Use Case Driven Approach. Addison-Wesley, 1992.Google Scholar
  2. 2.
    Rational Software Corporation, "Unified Modelling Language version 1.1". Available at, 1998.
  3. 3.
    J. Rumbaugh, M. Blaha, W. Premerlani, F. Eddy, and W. Lorensen, Object-Oriented Modeling and Design. Prentice Hall, 1991.Google Scholar
  4. 4.
    P. Haumer, K. Pohl, K. Weidenhaupt, Requirements Elicitation and Validation with real world scenes. IEEE Transactions on Software Engineering, Vol. 24,N°. 12, Special Issue on Scenario Management, December. 1998.Google Scholar
  5. 5.
    C. Rolland, C. Ben Achour, Guiding the construction of textual use case specifications. Data & Knowledge Engineering Journal Vol. 25N° 1, pp. 125–160, (ed. P. Chen, R.P. van de Riet) North Holland, Elsevier Science Publishers. March 1997.Google Scholar
  6. 6.
    C. Rolland, C. Souveyet, C. Ben Achour, Guiding Goal Modelling Using Scenarios. IEEE Transactions on Software Engineering, special issue on Scenario Management, 1998.Google Scholar
  7. 7.
    A. G. Sutcliffe, Scenario-based Requirements Analysis. Requirements Engineering Journal, Vol (3)N° 1, (ed. P. Loucopoulos, C. Potts), Springer Verlag. 1998.Google Scholar
  8. 8.
    E. Dubois, P. Heymans, Scenario-Based Techniques for supporting the Elaboration and the Validation of Formal Requirements, Submitted to RE Journal, 1998.Google Scholar
  9. 9.
    M. Saeki, K. Wen-yin, Specifying Software Specification and Design Methods. Proceedings of Conference on Advanced Information Systems Engineering, CAISE'94, Lecture Notes in Computer Science 811, Springer Verlag, pp. 353–366, Berlin, 1994.Google Scholar
  10. 10.
    C. Rolland, N. Prakash, A proposal for Context-Specific Method Engineering, IFIP TC8 Working Conference on Method Engineering, Atlanta, Gerorgie, USA, 1996.Google Scholar
  11. 11.
    S. Brinkkemper, M. Saeki, F. Harmsen, Assembly Techniques for Method Engineering. Proceedings of the 10th Conference on Advanced Information Systems Engineering, CAiSE'98. Pisa Italy, 8–12 June, 1998.Google Scholar
  12. 12.
    X. Song, A Framework for Understanding the Integration of Design Methodologies. In: ACM SIGSOFT Software Engineering Notes, Vol. 20,N°1, pp. 46–54, 1995.CrossRefGoogle Scholar
  13. 13.
    M. Bouzeghoub, I. Comyn, View Integration by Semantic Unification and Transformation of Data Structures, Proceedings of the Conference on Requirements Engineering, RE'90, Lausanne, 1990.Google Scholar
  14. 14.
    C. Rolland, N. Prakash, A. Benjamen, A multi-model view of process modelling. To appear in the RE journal, 1999.Google Scholar
  15. 15.
    N. Prat, Goal formalisation and classification for requirements engineering. Proceedings of the Third International Workshop on Requirements Engineering: Foundations of Software Quality REFSQ'97, Barcelona, pp. 145–156, June 1997.Google Scholar
  16. 16.
    I. Jacobson, The use case construct in object-oriented software Engineering. In ‘Scenario-based design: envisioning work and technology in system development’, John M. Carroll (ed.), John Wiley and Sons, 309–336, 1995.Google Scholar
  17. 17.
    G. Grosz, C. Rolland, S. Schwer, C. Souveyet, V. Plihon, S. Si-Said, C. Ben Achour, C. Gnaho, Modelling and Engineering the Requirements Engineering Process: an overview of the NATURE approach. Requirements Engineering Journal 2, pp. 115–131, 1997.CrossRefGoogle Scholar
  18. 18.
    S. Si-Said, C. Rolland, G. Grosz, MENTOR:A Computer Aided Requirements Engineering Environment. Proceedings of CAiSE'96, Crete, GREECE, May 1996.Google Scholar
  19. 19.
    C. Rolland, V. Plihon, J. Ralyté, Specifying the reuse context of scenario method chunks. Proceedings of the 10th Conference on Advanced Information Systems Engineering, CAiSE'98. Pisa Italy, 8–12 June, 1998.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1999

Authors and Affiliations

  • Jolita Ralyté
    • 1
  • Colette Rolland
    • 1
  • Véronique Plihon
    • 2
  1. 1.CRIUniversité de Paris1Paris
  2. 2.PRISMUniversité de Versailles Saint-Quentin 45Versailles

Personalised recommendations