CREWS Report Series 97 – 05 Modelling Contextual Information about Scenarios

Scenario-based approaches have proven useful for requirements elicitation, validation and negotiation. Besides the direct and indirect stated requirements current scenario-based approaches capture also contextual information about the existing or future system, but lack in a systematic support for representing and reasoning about this information. Based on a literature survey we define a comprehensive set of concepts needed to represent contextual usage knowledge of scenarios. In contrast to existing approaches, we propose to relate contextual knowledge not only to the whole scenario, but also to the scenario components, e.g. single or sets of interactions between the system and the user of the system. Consequently, we propose two contextual models, a scenario context model (SCM) and an interaction context model (ICM).

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

[2]  Matthias Jarke.  DAIDA : conceptual modeling and knowledge-based support of information systems development processes , 1990 .

[3]  Klaus Pohl,et al.  The three dimensions of requirements engineering: a framework and its applications , 1994, Inf. Syst..

[4]  John Mylopoulos,et al.  From E-R to "A-R" - Modelling Strategic Actor Relationships for Business Process Reengineering , 1994, Int. J. Cooperative Inf. Syst..

[5]  Matthias Jarke,et al.  Establishing Visions in Context: Towards a Model of Requirements Processes , 1994, EMISA Forum.

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

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

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

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

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

[11]  Heinz Züllighoven,et al.  Large Scale Object-Oriented Software-Development in a Banking Environment: An Experience Report , 1996, ECOOP.

[12]  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).

[13]  T.M. Duffy,et al.  Scenario-Based Design: Envisioning Work and Technology in System Development [Book Review] , 1996, IEEE Transactions on Professional Communication.

[14]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[15]  Martin S. Feather,et al.  Utilizing Scenarios in the Software Development Process , 1993, Information System Development Process.

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

[17]  Klaus Pohl,et al.  HYDRA: A Hypertext Model for Structuring Informal Requirements Representations 1 , 1995 .

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

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

[20]  Gustavo Rossi,et al.  Enhancing a requirements baseline with scenarios , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[21]  A. Sutcliffe,et al.  A technique combination approach to requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

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

[23]  James E. Rumbaugh,et al.  Modeling Models and Viewing Views: A Look at the Model-View-Controller Framework , 1994, J. Object Oriented Program..

[24]  Björn Regnell,et al.  A hierarchical use case model with graphical representation , 1996, Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems.