Guiding Goal Modeling Using Scenarios

Even though goal modeling is an effective approach to requirements engineering, it is known to present a number of difficulties in practice. The paper discusses these difficulties and proposes to couple goal modeling and scenario authoring to overcome them. Whereas existing techniques use scenarios to concretize goals, we use them to discover goals. Our proposal is to define enactable rules which form the basis of a software environment called L'Ecritoire to guide the requirements elicitation process through interleaved goal modeling and scenario authoring. The focus of the paper is on the discovery of goals from scenarios. The discovery process is centered around the notion of a requirement chunk (RC) which is a pair . The paper presents the notion of RC, the rules to support the discovery of RCs and illustrates the application of the approach within L'Ecritoire using the ATM example. It also evaluates the potential practical benefits expected from the use of the approach.

[1]  Matthias Jarke,et al.  Scenario usage in system development: a report on current practice , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[2]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[3]  Camille Salinesi,et al.  Guiding Scenario Authoring , 1998, EJC.

[4]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[5]  Janis A. Bubenko,et al.  Facilitating "fuzzy to formal" requirements modelling , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[6]  H. Holbrook,et al.  A scenario-based methodology for conducting requirements elicitation , 1990, SOEN.

[7]  Colette Rolland,et al.  Using the EKD Approach: The Modelling Component , 1997 .

[8]  Klaus Pohl,et al.  Modelling Contextual Information about Scenarios , 1999 .

[9]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[10]  Colette Rolland,et al.  Guidance for Requirements Engineering Processes , 1997, DEXA.

[11]  Colette Rolland,et al.  Guiding the Participative Design Process , 1997 .

[12]  Annie I. Antón,et al.  Goal Decomposition and Scenario Analysis in Business Process Reengineering , 1994, CAiSE.

[13]  Matthias Jarke,et al.  Scenarios in System Development: Current Practice , 1998, IEEE Softw..

[14]  Ivar Jacobson,et al.  The use-case construct in object-oriented software engineering , 1995 .

[15]  Ian M. Graham,et al.  Migrating to object technology , 1994 .

[16]  Colette Rolland,et al.  Guiding the Construction of Textual Use Case Specifications , 1998, Data Knowl. Eng..

[17]  Ivar Jacobson,et al.  Object-Oriented Software Engineering , 1991, TOOLS.

[18]  Pericles Loucopoulos,et al.  Aligning Legacy Information Systems to Business Processes , 1998, CAiSE.

[19]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[20]  James E. Rumbaugh,et al.  Object-Oriented Modelling and Design , 1991 .

[21]  Pericles Loucopoulos,et al.  Using Scenarios to Validate Requirements in a Plausibility Centred Approach , 1997, CAiSE.

[22]  Alistair Cockburn,et al.  Structuring Use Cases with Goals , 2000 .

[23]  Selmin Nurcan,et al.  Describing Business Processes with a Guided Use Case Approach , 1998, CAiSE.

[24]  Eric Yu,et al.  Using Goals, Rules and Methods to Support Reasoning in Business Process Reengineering , 1996 .

[25]  Patrick Heymans,et al.  A reuse-Oriented Approach for the Construction of Scenario Bases Methods , 1997 .

[26]  Nicolas Prat,et al.  Goal Formalisation and Classification for Requirements Engineering , 1996 .

[27]  Annie I. Antón,et al.  Goal-based requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.