A PROPOSAL FOR A SCENARIO CLASSIFICATION FRAMEWORK 1

The Requirement Engineering, Information Systems and Software Engineering communities recently advocated scenario-based approaches which emphasise the user/system interaction perspective in developing computer systems. Use of examples, scenes, narrative descriptions of contexts, mock-ups and prototypes, all these ideas can be called scenario based approaches, although exact definitions are not easy beyond saying these approaches emphasise some description of the real world. Experience seems to tell us that people react to 'real things' and that this helps clarifying requirements. Indeed the widespread acceptance of prototyping in system development points to the effectiveness of scenario based approaches. However, we have little understanding about how scenarios should be constructed, little hard evidence about their effectiveness and even less idea about why they work. The paper is an attempt to explore some of the issues underlying scenario based approaches in Requirements Engineering (RE) and to propose a framework for their classification. The framework is a 4-dimensional framework which advocates that a scenario-based approach can be well-defined by its form, contents, purpose, and life cycle. Every dimension is itself multi-faceted and a metric is associated to each facet. Motivations for developing the framework are threefold : (a) to help understanding and clarifying existing scenario based approaches, (b) to situate the industrial practice of scenarios and (c) to assist researchers develop more innovative scenario based approaches.

[1]  R. M. Young,et al.  The use of scenarios in human-computer interaction research: turbocharging the tortoise of cumulative science , 1987, CHI '87.

[2]  David Harel,et al.  Statecharts: A Visual Formalism for Complex Systems , 1987, Sci. Comput. Program..

[3]  John D. Gould,et al.  How to design usable systems , 1995 .

[4]  Michael L. Begeman,et al.  gIBIS: a hypertext tool for exploratory policy discussion , 1988, CSCW '88.

[5]  Juhani Iivari,et al.  Levels of Abstraction as a Conceptual Framework for an Information System , 1989, ISCO.

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

[7]  William E. Lorensen,et al.  Object-Oriented Modeling and Design , 1991, TOOLS.

[8]  E. Jeffrey Conklin,et al.  A process-oriented approach to design rationale , 1991 .

[9]  Mary Beth Rosson,et al.  Getting around the task-artifact cycle: how to make claims and design by scenario , 1992, TOIS.

[10]  Robert L. Campbell,et al.  WILL THE REAL SCENARIO PLEASE STAND UP? , 1992, ACM SIGCHI Bull..

[11]  Peter Wright,et al.  What's in a scenario? , 1992, SGCH.

[12]  Bonnie A. Nardi,et al.  The use of scenarios in design , 1992, SGCH.

[13]  John S. Anderson,et al.  Using scenarios in deficiency-driven requirements engineering , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

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

[15]  Doug Kimelman,et al.  Visualizing the behavior of object-oriented systems , 1993, OOPSLA '93.

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

[17]  David Chenho Kung,et al.  Formal approach to scenario analysis , 1994, IEEE Software.

[18]  Michael G. Christel,et al.  A multimedia approach to requirements capture and modeling , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[19]  Colette Rolland,et al.  A general framework for describing the requirements engineering process , 1994, Proceedings of IEEE International Conference on Systems, Man and Cybernetics.

[20]  Eric Dubois,et al.  AGENT-ORIENTED REQUIREMENTS ENGINEERING A CASE STUDY USING THE ALBERT LANGUAGE , 1994 .

[21]  John Mylopoulos,et al.  Using Goals, Rules and Methods to Support Reasoning in Business Process Reengineering , 1994, Intell. Syst. Account. Finance Manag..

[22]  Juhani Iivari,et al.  Object-oriented information systems analysis: Comparative analysis of six object oriented analysis methods , 1994, Methods and Associated Tools for the Information Systems Life Cycle.

[23]  Ivar Jacobson,et al.  The object advantage - business process reengineering with object technology , 1994 .

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

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

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

[27]  Thomas Erickson,et al.  Notes on design practice: stories and prototypes as catalysts for communication , 1995 .

[28]  Kari Kuutti,et al.  Work processes: scenarios as a preliminary vocabulary , 1995 .

[29]  Scott P. Robertson Generating object-oriented design representations via scenario queries , 1995 .

[30]  Morten Kyng,et al.  Creating contexts for design , 1995 .

[31]  Martin Glinz,et al.  An Integrated Formal Model of Scenarios Based on Statecharts , 1995, ESEC.

[32]  Björn Regnell,et al.  Improving the use case driven approach to requirements engineering , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[33]  Peter Johnson,et al.  Rapid prototyping of user interfaces driven by task models , 1995 .

[34]  Stewart A. Higgins,et al.  Scenarios-an industrial case study and hypermedia enhancements , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[35]  Mary Beth Rosson,et al.  Narrowing the specification-implementation gap in scenario-based design , 1995 .

[36]  Hanspeter Mössenböck,et al.  Scene: using scenario diagrams and active text for illustrating object-oriented programs , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[37]  Jeffrey D. Smith,et al.  Hypermedia support for collaboration in requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[38]  K. Koskimies,et al.  On the Role of Scenarios in Object-oriented Software Design on the Role of Scenarios in Object-oriented Software Design on the Role of Scenarios in Object-oriented Software Design , 1996 .

[39]  Stéphane S. Somé,et al.  Toward an Automation of Requirements Engineering using Scenarios , 1996 .

[40]  Klaus Pohl,et al.  Process-Centered Requirements Engineering , 1996 .

[41]  Daniel A. Rawsthorne Capturing functional requirements through object interactions , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[42]  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.

[43]  Monique Snoeck,et al.  Enterprise Modelling , 1998, ECOOP Workshops.

[44]  V. Lalioti Use of Scenarios for Validation of Conceptual Specifications , 2000 .

[45]  Said Ghoul,et al.  CLASSIFYING SOFTWARE FOR REUSABILITY , 2001 .