Scenario-based requirements analysis
Requirements EngineeringPublished 1 March 1998
Alistair Sutcliffe
Citations134
SJR quartileQ2
SJR score0.52
SNIP1.51
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
A method for scenario-based requirements engineering is described, which uses two types of scenario: structure models of the system context and scripts of system usage.
Abstract
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.
Keywords
Computer Science
Object Oriented Software Engineering: A Use Case Driven Approach
2,943 Citations1992Ivar Jacobson
This book discusses object-oriented software engineering as a process of change, management of object-oriented software engineering, and other object-oriented methods.
Safeware: System Safety and Computers
1,665 Citations1995Nancy G. Leveson
Information and Software TechnologyObject-oriented software engineering: a use case driven approach
1,494 Citations1992LF Marshall
IEEE Transactions on Software EngineeringThe TAME project: towards improvement-oriented software environments
1,379 Citations1988Victor R. Basili, H. Dieter Rombach
The TAME system is an instantiation of the TAME software engineering process model as an ISEE (integrated software engineering environment) and the first in a series of Tame system prototypes has been developed.
Clinical neurosurgeryRequirements Engineering: A Good Practice Guide
1,217 Citations1997Ian Sommerville, Pete Sawyer
This book presents a set of guidelines which reflect the best practice in requirements engineering, and explains in an easy-to-understand way how you can improve your requirements engineering processes.
Virtual Defense Library (Ministerio de Defensa)Modern structured analysis
1,074 Citations1989Edward Yourdon
From the Publisher: Yourdon provides a fresh perspective on structured systems analysis, integrating traditional methodologies with modern technology.
Improving Performance: How to Manage the White Space on the Organization Chart
1,060 Citations1990Alan P. Brache, Geary A. Rummler
IEEE Transactions on Software EngineeringRepresenting and using nonfunctional requirements: a process-oriented approach
1,018 Citations1992John Mylopoulos, Lawrence Chung +1 more
A comprehensive framework for representing and using nonfunctional requirements during the development process is proposed and evidence for the power of the framework is provided through the study of accuracy and performance requirements for information systems.
John Wiley & Sons, Inc. eBooksScenario-based design: envisioning work and technology in system development
940 Citations1995John M. Carroll
Partial table of contents: Work Processes: Scenarios as a Preliminary Vocabulary, creating Contexts for Design, and Generating Object-Oriented Design Representations via Scenario Queries.
Medical Entomology and ZoologyHuman Reliability Analysis: Context and Control
738 Citations1994Erik Hollnagel
Performance, Reliability, And Unwanted Consequences, and the Need for Models of the Reliability of Cognition.
ACM SIGSOFT Software Engineering NotesSafeware: System Safety and Computers
656 Citations1995Peter G. Neumann
Goal-based requirements analysis
522 Citations2002Annie I. Antón
Some of the issues that practitioners face when using a goal-based approach to specify the requirements for a system are illustrated and some of the needs for needed future research are discussed.
IEEE SoftwareInquiry-based requirements analysis
520 Citations1994Colin Potts, Kenji Takahashi +1 more
The authors use a case study to describe the model's conversation metaphor, which follows analysis activities from requirements elicitation and documentation through refinement, and at its core is the inquiry cycle model.
Structuring Use Cases with Goals
282 Citations2000Alistair Cockburn
A theory based on a small model of communication, distinguishing "goals" as a key element of use cases is introduced, resulting in an easily used, scaleable, recursive model that provides benefits outside requirements gathering.
Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt
268 Citations2002Axel van Lamsweerde, Robert Darimont +1 more
The objective of the paper is to assess the strengths and weaknesses of one of these methodologies on a nontrivial benchmark; and to illustrate and discuss a number of challenging issues that need to be addressed for such methodologies to become effective in supporting real, complex requirements engineering tasks.
International Joint Conference on Artificial IntelligenceA common-sense theory of time
260 Citations1985James F. Allen, Patrick J. Hayes
This paper proposes an axiomatic a theory of time in terms of intervals and the single relation MEET and shows that this axiomatization subsumes Allen's interval-based theory.
IEEE Transactions on Software EngineeringRequirements validation through viewpoint resolution
241 Citations1991Julio César Sampaio do Prado Leite, Peter A. Freeman
A language for expressing views from different viewpoints and a set of analogy heuristics for performing a syntactically oriented analysis of views are proposed, capable of differentiating between missing information and conflicting information, thus providing support for viewpoint resolution.
The change and evolution of requirements as a challenge to the practice of software engineering
178 Citations2002Susan Harker, Ken Eason +1 more
The author identifies a number of ways in which different approaches to design may help to deal with change as well as mechanisms which should underpin effective communication between users and designers.
Applied computingRequirements Engineering
154 Citations1996Linda A. Macaulay
A chronology of key events and concepts leading to and after the establishment of Requirements Engineering in the field of computer science and its applications in the areas of education, training, and research and development.
Improving performance how to manage the white space on the organization chart
117 Citations1995Rummler, Geary A., Brache, Alan P.
Domain descriptions
109 Citations2002Michael Jackson, Pamela Zave
It is argued that current formal specification techniques are inadequate in this respect, and therefore cannot offer a satisfactory foundation for automated support of software development.
Scenario usage in system development: a report on current practice
106 Citations2002K. Weidenhaupt, Klaus Pohl +2 more
The authors consider the two-pronged strategy being followed to gain a deeper understanding of the diversity of scenarios, in order to help improve methodological and tool support for scenario-based requirements engineering.
A hierarchical use case model with graphical representation
99 Citations2002Björn Regnell, Mats Andersson +1 more
A conceptual framework for use case modelling and a new use case model with graphical representation are presented, including support for different abstraction levels and mechanisms for managing large use case models.
A technique combination approach to requirements engineering
74 Citations2002Alistair Sutcliffe
An approach to requirements engineering based on a combination of early prototyping, scenario-based analysis and design rationale, which proved very effective in eliciting requirements but differences in analyst style were an important variable.
International Journal of Human-Computer StudiesTask-related information analysis
46 Citations1997Alistair Sutcliffe
A method is described for analysing task-related information needs linked to design of information displays by defining users' requirements with information types and selecting appropriate means of information delivery according to the users' needs.
Human-Computer Interface Design
44 Citations1995Alistair Sutcliffe
Task scripts, use cases and scenarios in object oriented analysis.
43 Citations1996Ian M. Graham
European Journal of Work and Organizational PsychologyRepresenting socio-technical systems options in the development of new forms of work organization
42 Citations1996Ken Eason, Susan Harker +1 more
Requirements critiquing using domain abstractions
39 Citations2002Neil Maiden, Alistair Sutcliffe
Domain abstractions are proposed to aid requirements critiquing as well as specification, thus maximising the payoff from retrieving domain abstractions, and Intelligent, mixed initiative dialogue between the critic and requirements engineer permits requirementscritiquing at the right time and level of abstraction.
An evaluation of inquiry-based requirements analysis for an Internet service
21 Citations2002Colin Potts, Kenji Takahashi +2 more
An evaluation of the inquiry cycle model and a support tool, Tuiqiao, in the requirements analysis phase of a real project, a proposed commercial consumer information service based on Internet, and some recommendations for tool support are concluded.
Interacting with ComputersA co-operative scenario based approach to acquisition and validation of system requirements: How exceptions can help!
14 Citations1999Neil Maiden, Shaíley Minocha +3 more
A prototype software tool called CREWS–SAVRE for systematic scenario generation and use is presented, which has identified three kinds of exceptions: generic, permutation and problem exceptions, and has derived complex taxonomies of problem exceptions.
OSTI OAI (U.S. Department of Energy Office of Scientific and Technical Information)Designing a user-system interface
1 Citations1989H.A. Pfuderer, Kyle Miller
The essence of the ORNL methodology is to provide users at all levels in the organization many opportunities to participate in systems development, and user involvement included incorporating their own critical success factors into the planning process.