Scenario-based requirements analysis

A method for scenario-based requirements engineering is described. The method uses two types of scenario: structure models of the system context and scripts of system usage. A modelling language is reported for describing scenarios, and heuristics are given to cross-check dependencies between scenario models and the requirements specification. Heuristics are grouped into several analytic treatments that investigate correspondences between users’ goals and system functions; input events and system processes to deal with them; system output and its destination in the scenario model, and acceptability analysis of system output for different stakeholders. The method is illustrated with a case study taken from the London Ambulance Service report. The prospects for scenario-based requirements engineering and related work are discussed.

[1]  John M. Carroll,et al.  Scenario-based design: envisioning work and technology in system development: john wiley & sons , 1995 .

[2]  Shailey Minocha,et al.  A co-operative scenario based approach to acquisition and validation of system requirements: How exceptions can help! , 1999, Interact. Comput..

[3]  Alistair G. Sutcliffe,et al.  Requirements rationales: integrating approaches to requirement analysis , 1995, Symposium on Designing Interactive Systems.

[4]  Jeffrey D. Smith,et al.  An evaluation of inquiry-based requirements analysis for an Internet service , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[5]  Geoff P. Mullery,et al.  CORE : A Method for Controlled Requirement Expression , 1979, ICSE.

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

[7]  MSc Mbcs CEng Michael Bronzite BSc.  System Development , 2000, Springer London.

[8]  Alistair Sutcliffe,et al.  Human-Computer Interface Design , 1988, Macmillan Computer Science Series.

[9]  Erik Hollnagel,et al.  Human Reliability Analysis: Context and Control , 1994 .

[10]  Geary A. Rummler,et al.  Improving Performance: How to Manage the White Space on the Organization Chart , 1990 .

[11]  Philippe Massonet,et al.  Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[12]  S.D.P. Harker,et al.  The change and evolution of requirements as a challenge to the practice of software engineering , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

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

[14]  Alistair Sutcliffe,et al.  Jackson System Development , 1988 .

[15]  Alistair G. Sutcliffe,et al.  Task-related information analysis , 1997, Int. J. Hum. Comput. Stud..

[16]  A. Finkelstein.  Report of the Inquiry into the London Ambulance Service , 1993 .

[17]  K. Eason,et al.  Representing socio-technical systems options in the development of new forms of work organization , 1996 .

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

[19]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

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

[21]  Howard C. Nusbaum,et al.  of the User/System Interface , 1983 .

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

[23]  Peter Neumann,et al.  Safeware: System Safety and Computers , 1995, SOEN.

[24]  Edward Yourdon,et al.  Modern structured analysis , 1989 .

[25]  Patrick J. Hayes,et al.  A Common-Sense Theory of Time , 1985, IJCAI.

[26]  A. Berztiss,et al.  Requirements Engineering , 2002, J. Object Technol..

[27]  Ian M. Graham,et al.  Task scripts, use cases and scenarios in object oriented analysis , 1996, Object Oriented Syst..

[28]  I. A N G R A H A M.  Task scripts , use cases and scenarios in object oriented analysis , 2022 .

[29]  Neil A. M. Maiden,et al.  Requirements critiquing using domain abstractions , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

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

[31]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..

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

[33]  Michael Jackson,et al.  Domain descriptions , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[34]  Victor R. Basili,et al.  The TAME Project: Towards Improvement-Oriented Software Environments , 1988, IEEE Trans. Software Eng..

[35]  J. Shaoul.  Human Error , 1973, Nature.

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

[37]  Julio Cesar Sampaio do Prado Leite,et al.  Requirements Validation Through Viewpoint Resolution , 1991, IEEE Trans. Software Eng..