This Article 
 Bibliographic References 
 Add to: 
Guiding Goal Modeling Using Scenarios
December 1998 (vol. 24 no. 12)
pp. 1055-1071

Abstract—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] A.I. Anton, W.M. McCracken, and C. Potts, "Goal Decomposition and Scenario Analysis in Business Process Reengineering," Proc. CAISE'94, Sixth Conf. Advanced Information Systems Eng., pp. 94-104, Lecture Notes in Computer Science 811, Springer-Verlag, 1994.
[2] A.I. Anton, "Goal-based Requirements Analysis," Proc. 2nd IEEE Int'l Conf. Requirements Engineering, CS Press, Los Alamitos, Calif., Apr. 1996, pp. 136-144.
[3] C. Ben Achour, "Guiding Scenario Authoring," Proc. Eighth European Japanese Conf. Information Modeling and Knowledge Bases, pp. 181-200,Ellivuori, Finland, May 1998.
[4] J. Bubenko, C. Rolland, P. Loucopoulos, and V. De Antonellis, "Facilitating 'Fuzzy to Formal' Requirements Modeling," IEEE First Conf. Requirements Eng., ICRE '94, pp. 154-158, 1994.
[5] A. Cockburn, "Structuring Use Cases with Goals," technical report, Human and Technology, HaT.TR.95.1, 84121, Salt Lake City, Utah, 1995.
[6] B. Dano, H. Briand, and F. Barbier, "A Use Case Driven Requirements Eng. Process," Proc. Third IEEE Int'l Symp. Requirements Eng. RE '97,Annapolis, Md., IEEE CS Press, 1997.
[7] A. Dardenne, A. van Lamsweerde, and S. Fickas, "Goal-Directed Requirements Acquisition," Science of Computer Programming, pp. 3-50, vol. 20, Apr. 1993.
[8] A. Davis, Software Requirements: Objects, Functions, and States, Prentice Hall, Old Tappan, NJ, 1993.
[9] ELEKTRA consortium, "Electrical Enterprise Knowledge for Transforming Applications—Athena Deliverable: Initial Requirements for PPC," ELEKTRA Project Internal Report, http:/www.singular.grelektra, 1997.
[10] ELEKTRA consortium, "Esprit Program 7.1, Technologies for Business Processes, Best Business Practice Pilots," Elektra: Electrical Enterprise Knowledge for Transforming Applications. (Proj. no. 22927)http://www.singular.grelektra, Jan. 1997- June 1999.
[11] D. Filippidou and P. Loucopoulos, "Using Scenarios to Validate Requirements in a Plausibility-Centred Approach," Proc. Ninth Int'l Conf. Advanced Information Systems Eng. CaiSE '97, A. Olive, ed., Barcelona, Springer-Verlag, June 1997.
[12] I.M. Graham, Migrating to Object Technology, Addison-Wesley, Reading, Mass., 1995.
[13] G. Grosz, C. Rolland, S. Schwer, C. Souveyet, V. Plihon, S. Si-Said, C. Ben Achour, and C. Gnaho, "Modeling and Engineering the Requirements Engineering Process: An Overview of the NATURE Approach," Requirements Eng. J., vol. 2, pp. 115-131, 1997.
[14] H. Holbrook III, "A Scenario-Based Methodology for Conducting Requirements Elicitation," ACM SIGSOFT Software Eng. Notes, vol. 15, no. 1, pp. 95-104, Jan. 1990.
[15] I. Jacobson, "The Use-Case Construct in Object-Oriented Software Engineering," Scenario-Based Design: Envisioning Work and Technology in System Development, J. Carroll, ed., John Wiley&Sons, New York, 1995, pp. 309-336.
[16] I. Jacobson, Object-Oriented Software Engineering, Addison-Wesley/ACM Press, New York, 1991.
[17] P. Kardasis and P. Loucopoulos, "Aligning Legacy Information System to Business Processes," Proc. 10th Conf. Advanced Information Systems Eng., CaiSE '98, pp. 8-12,Pisa Italy, June, 1998.
[18] J.C. Leite, G. Rossi, F. Balaguer, V. Maiorana, G. Kaplan, G. Hadad, and A. Oliveros, "Enhancing a Requirements Baseline with Scenarios," Proc. RE'97—Third Int'l Symp. Requirements Eng., pp. 44-53,Anapolis, IEEE, 1997.
[19] P. Loucopoulos, "The F3 (From Fuzzy to Formal) View on Requirements Engineering," Ingénierie des Systèmes d'Information, vol. 2, no. 6, pp. 639-655, 1994.
[20] P. Loucopoulos, V. Kavakli, and N. Prekas, "Using the EKD Approach, the Modeling Component," ELEKTRA project internal report, 1997.
[21] S. Nurcan, G. Grosz, and C. Souveyet, "Describing Business Processes with a Use Case Driven Approach," Proc. 10th Int'l Conf. CaiSE '98, Lecture Notes in Computer Science 1413, B. Pernici and C. Thanos, eds., Pisa Italy, Springer, June 1998.
[22] V. Plihon, J. Ralyté, A. Benjamen, N.A.M. Maiden, A. Sutcliffe, E. Dubois, and P. Heymans, "A Reuse-Oriented Approach for the Construction of Scenario Based Methods," Proc. Int'l Software Process Assoc. Fifth Int'l Conf. Software Process (ICSP '98),Chicago, pp. 14-17, June 1998.
[23] K. Pohl and P. Haumer, "Modeling Contextual Information about Scenarios," Proc. Third Int'l Workshop Requirements Eng.: Foundations of Software Quality REFSQ '97, pp. 187-204,Barcelona, June 1997.
[24] C. Potts, K. Takahashi, and A. Anton, "Inquiry-Based Requirements Analysis," IEEE Software, Mar. 1994, pp. 21-32.
[25] C. Potts, "Fitness for Use: the System Quality that Matters Most," Proc. Third Int'l Workshop Requirements Eng.: Foundations of Software Quality REFSQ '97, pp. 15-28,Barcelona, June 1997.
[26] N. Prat, "Goal Formalisation and Classification for Requirements Engineering," Proc. Third Int'l Workshop Requirements Eng.: Foundations of Software Quality REFSQ '97, pp. 145-156,Barcelona, June 1997.
[27] Rational Software Corp. Unified Modelling Language Version 1.1., available at , 1998.
[28] C. Rolland and C. Ben Achour, "Guiding the Construction of Textual Use Case Specifications," Data and Knowledge Eng. J., vol. 25, nos. 1-2, pp. 125-160, Mar. 1998.
[29] C. Rolland, C. Ben Achour, C. Cauvet, J. Ralyte, A. Sutcliffe, N.A.M. Maiden, M. Jarke, P. Haumer, K. Pohl, E. Dubois, and P. Heymans, "A Proposal for a Scenario Classification Framework," Requirements Engineering J., vol. 3, no.1, 1998.
[30] C. Rolland, S. Nurcan, and G. Grosz, "Guiding the Participative Design Process,. Assoc. for Information Systems Americas Conf.,Indianapolis, Ind., pp. 922-924, Aug. 1997.
[31] C.L. Chang, R.A. Stachowitz, and J.B. Combs, “Validation of Nonmonotonic Knowledge-Based Systems,” Proc. IEEE Int'l Conf. Tools for Artificial Intelligence, Nov. 1990.
[32] S. Si-Said, "Guidance for Requirements Eng. Processes," Proc. Eighth Int'l Conf. and Workshop Database and Experts System Application, DEXA '97,Toulouse, France, Sept. 1997.
[33] K. Weidenhaupt, K. Pohl, M. Jarke, and P. Haumer, "Scenario Usage in System Development: A Report on Current Practice," IEEE Software, Mar. 1998.
[34] E. Yu and J. Mylopoulos, "Using Goals, Rules and Methods to Support Reasoning in Business Process Reengineering," Proc. 27th Hawaii Int'l Conf. System Sciences,Maui, Hawaii, vol. 4, pp. 234-243, Jan. 1994.

Index Terms:
Goal modeling, scenario authoring, goal discovery.
Colette Rolland, Carine Souveyet, Camille Ben Achour, "Guiding Goal Modeling Using Scenarios," IEEE Transactions on Software Engineering, vol. 24, no. 12, pp. 1055-1071, Dec. 1998, doi:10.1109/32.738339
Usage of this product signifies your acceptance of the Terms of Use.