A scenario-based methodology for conducting requirements elicitation

Published on Jan 1, 1990in ACM Sigsoft Software Engineering Notes
· DOI :10.1145/382294.382725
H. Holbrook1
Estimated H-index: 1
(USAFA: United States Air Force Academy)
Requirements analysis is the process of identifying a user's needs and determining what to build in an a system. Within requirements analysis is the process of requirements elicitation in which tacit information about "what to build" is obtained from the user and his environment. Here, we will describe a methodology, dubbed Scenario Based Requirements Elicitation (SBRE), which structures the early interaction between users and designers in order to quickly develop a set of initial requirements. The methodology features the parallel development of requirements and a high-level design, the use of scenarios to communicate the behavior of a design, an evaluation function to assess the suitability of the design, and an issue base with which to maintain the issues that arise during the elicitation process.
  • References (13)
  • Citations (92)
📖 Papers frequently viewed together
6 Authors (Pei Hsia, ..., C. Chen)
243 Citations
3 Authors (Colin Potts, ..., Annie I. Antón)
483 Citations
3 Authors (Anne Dardenne, ..., Stephen Fickas)
1,706 Citations
78% of Scinapse members use related papers. After signing in, all features are FREE.
#1David CrowleyH-Index: 1
Introduction Part 1: The Foundations - Feedback and Reflexion 1. The Idea of Feedback 2. Interdependency and Human Needs 3. Reflexion and the Social Order 4. Modes of Human Communication Part 2: The Empirical Enclosures 5. The Classical Models of Information 6. Instrumental Information 7. Social Information 8. Information and Codification Part 3: Intersubjectivity - Modes of Symbolic Interaction 9. Language 10. Story Systems 11. Symbols and Symbolization 12. Symbol Internalization Part 4: Bias -...
7 Citations
Apr 1, 1987 in CHI (Human Factors in Computing Systems)
#1Richard M. YoungH-Index: 20
#2Phil BarnardH-Index: 6
A scenario is an idealised but detailed description of a specific instance of human-computer interaction (HCI). A set of scenarios can be used as a “filter bank” to weed out theories whose scope is too narrow for them to apply to many real HCI situations. By helping redress the balance between generality and accuracy in theories derived from cognitive psychology, this use of scenarios (1) allows the researcher to build on empirical findings already established while avoiding the tar-pits associa...
55 CitationsSource
#1Brooks (UNC: University of North Carolina at Chapel Hill)H-Index: 1
All software construction involves essential tasks, the fashioning of the complex conceptual structures that compose the abstract software entity, and accidental tasks, the representation of these abstract entities in programming languages and the mapping of these onto machine languages within space and speed constraints. Most of the big past gains in software productivity have come from removing artificial barriers that have made the accidental tasks inordinately hard, such as severe hardware c...
2,719 CitationsSource
19 Citations
#1J. ConklinH-Index: 1
#2C. RichterH-Index: 1
5 CitationsSource
#1Maryam Alavi (UH: University of Houston)H-Index: 30
A two-phased research project comparing the prototyping approach with the more traditional life cycle approach finds that prototyping facilitates communication between users and designers during the design process. However, the findings also indicate that designers who used prototyping experienced difficulties in managing and controlling the design process.
316 CitationsSource
#1Barry Boehm (UCLA: University of California, Los Angeles)H-Index: 59
#2Terence E. Gray (UCLA: University of California, Los Angeles)H-Index: 3
Last. Thomas Seewaldt (UCLA: University of California, Los Angeles)H-Index: 2
view all 3 authors...
In this experiment, seven software teams developed versions of the same small-size (2000-4000 source instruction) application software product. Four teams used the Specifying approach. Three teams used the Prototyping approach. The main results of the experiment were the following. 1) Prototyping yielded products with roughly equivalent performance, but with about 40 percent less code and 45 percent less effort. 2) The prototyped products rated somewhat lower on functionality and robustness, but...
246 CitationsSource
#1Anne C. SteeleH-Index: 1
#2Barbara J. NowellH-Index: 1
Requirements engineering involves three processes: (1) problem recognition; (2) problem understanding; (3) solution space specification. [5] This paper focuses on problem recognition and problem understanding—the needs determination component of requirements engineering. During needs determination effective communication between information system users and information system designers is critical—creative exploration of the problem environment is imperative.
2 CitationsSource
#1James W. Hooper (UAH: University of Alabama in Huntsville)H-Index: 4
#2Pei Hsia (UAH: University of Alabama in Huntsville)H-Index: 1
The three major facets of software requirements engineering are: (1) requirements identification, (2) requirements analysis, and (3) requirements communication. Much research addresses the latter two aspects, but few practical approaches exist for addressing the first one. Hence, system requirements remains the most critical and problemprone area of system development. There is thus an urgent need for a methodology which helps a user identify requirements and realize potential impacts, in a time...
38 CitationsSource
#1G. B. Davis (UMN: University of Minnesota)H-Index: 1
Correct and complete information requirements are key ingredients in planning organizational information systems and in implementing information systems applications. Yet, there has been relatively little research on information requirements determination, and there are relatively few practical, well-formulated procedures for obtaining complete, correct information requirements. Methods for obtaining and documenting information requirements are proposed, but they tend to be presented as general ...
575 CitationsSource
Cited By92
#1Alessandra Reyes-Flores (Universidad Veracruzana)
#2Carmen Mezura-Godoy (Universidad Veracruzana)H-Index: 4
Last. Edgard Benítez-Guerrero (Universidad Veracruzana)H-Index: 5
view all 3 authors...
On a requirements analysis process, software designers identify and collect information about users needs, requirements of the system and its user interface. In order to design user interfaces for collaborative use it is important to know what are functional requirements, individual and social users needs. This paper presents a process of requirements analysis for Tangible User Interfaces design, specifically for software that are used by a group of people working to achieve a common goal. The p...
#1Abdullah Wahbeh (SRU: Slippery Rock University of Pennsylvania)H-Index: 5
#2Surendra Sarnikar (CSU: California State University)
Last. Omar F. El-Gayar (Dakota State University)H-Index: 14
view all 3 authors...
Software development is the process of building systems that solve users’ need and satisfy stakeholders’ objectives. Such needs are determined through requirements elicitation, which is considered an intensive, complex, and multi-disciplinary process. Traditional methods of elicitation often fail to uncover requirements that are critical for successful and wide-scale user adoption because these methods primarily focus on the technical aspects and constraints of the systems rather than considerin...
#1Stefan Oppl (Johannes Kepler University of Linz)H-Index: 10
#2Christian Stary (Johannes Kepler University of Linz)H-Index: 17
This chapter introduces methods to enable to act on the results of articulation and alignment processes. As such, it outlines paths towards sharing and anchoring new work practices in organizations. The proposed methodologically grounded interventions allow to qualitatively validate novel work practices and to agree on strategies for their organization-wide roll-out. Drawing from current practice-oriented research in organizational development, Computer Supported Collaborative Work (CSCW), and k...
#1Naveen PrakashH-Index: 13
#2Deepika Prakash (Central University of Rajasthan)H-Index: 5
The book starts with failure statistics of transactional systems and the technological responses for failure mitigation. We discuss the evolution of development processes for transactional systems and highlight the emerging role of agile development. This mitigates failure through iterative and incremental development. The second response is to focus on system requirements. Here we first define the term requirements and consider the requirements engineering process. The approaches to requirement...
#1Garm Lucassen (UU: Utrecht University)H-Index: 10
#2Marcel Robeer (UU: Utrecht University)H-Index: 4
Last. Sjaak Brinkkemper (UU: Utrecht University)H-Index: 36
view all 5 authors...
Extracting conceptual models from natural language requirements can help identify dependencies, redundancies, and conflicts between requirements via a holistic and easy-to-understand view that is generated from lengthy textual specifications. Unfortunately, existing approaches never gained traction in practice, because they either require substantial human involvement or they deliver too low accuracy. In this paper, we propose an automated approach called Visual Narrator based on natural languag...
21 CitationsSource
Mar 30, 2017 in BPM (Business Process Management)
#1Stefan Oppl (Radboud University Nijmegen)H-Index: 10
Validation of business process models under involvement of stakeholders is usually performed by moderated model walkthroughs. We explore the potential of combining these established practices with interactive enactment of executable prototypes that is widely used in UI prototyping and model-based interactive system design. Based on these fields, we develop the concept of process elaboration through scaffolded virtual enactment. The proposed concepts are instantiated in a web-based tool that enab...
4 CitationsSource
#1Corentin Burnay (Université de Namur)H-Index: 4
Requirements elicitation consists in collecting and documenting information about the requirements from a system-to-be and about the environment of that system. Elicitation forms a critical step in the design of any information system, subject to many challenges like information incompleteness, variability, or ambiguity. To deal with these challenges, requirements engineers heavily rely on stakeholders, who turn out to be one of the most significant provider of information during elicitation. So...
2 CitationsSource
#1David RinehartH-Index: 1
#2Philip J. Smith (OSU: Ohio State University)H-Index: 15
Last. Amy SpencerH-Index: 5
view all 4 authors...
For the past several years, our team has developed and experimented with a novel method to support the verification and validation (V&V) of autonomous systems. This method, entitled Expert-Guided Scenarios for Autonomy Validation (EGS-AV), combines an extensible, database-oriented information model for operational scenarios with a systematic process for eliciting validation information from subject matter experts (SMEs). EGS-AV fills a critical V&V need, providing a standard information model fo...
#1Garm Lucassen (UU: Utrecht University)H-Index: 10
#2Fabiano Dalpiaz (UU: Utrecht University)H-Index: 23
Last. Sjaak Brinkkemper (UU: Utrecht University)H-Index: 36
view all 4 authors...
User stories are a widely adopted requirements notation in agile development. Yet, user stories are too often poorly written in practice and exhibit inherent quality defects. Triggered by this observation, we propose the Quality User Story (QUS) framework, a set of 13 quality criteria that user story writers should strive to conform to. Based on QUS, we present the Automatic Quality User Story Artisan (AQUSA) software tool. Relying on natural language processing (NLP) techniques, AQUSA detects q...
43 CitationsSource