The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.12 - December (1998 vol.24)
pp: 1156-1170
ABSTRACT
<p><b>Abstract</b>—We describe and analyze the process of requirements development in scenario-based design through consideration of a case study. In our project, a group of teachers and system developers initially set out to create a virtual physics laboratory. Our design work centered on the collaborative development of a series of scenarios describing current and future classroom activities. We observed classroom scenarios to assess needs and opportunities, and envisioned future scenarios to specify and analyze possible design moves. We employed claims analysis to evaluate design trade-offs implicit in these scenarios, to codify the specific advantages and disadvantages in achieving requirements. Through the course of this process, the nature of our project requirements has evolved, providing more information but also more <it>kinds</it> of information. We discuss the utility of managing requirements development through an evolving set of scenarios, and the generality of the scenario stages from this case study.</p>
INDEX TERMS
Participatory design, scenario-based design, requirements engineering, requirements development.
CITATION
Mary Beth Rosson, George Chin, John M. Carroll, "Requirements Development in Scenario-Based Design", IEEE Transactions on Software Engineering, vol.24, no. 12, pp. 1156-1170, December 1998, doi:10.1109/32.738344
21 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool