Requirements development in scenario-based design

Research output: Contribution to journalArticle

66 Citations (Scopus)

Abstract

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 kinds 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.

Original languageEnglish (US)
Pages (from-to)1156-1170
Number of pages15
JournalIEEE Transactions on Software Engineering
Volume24
Issue number12
DOIs
StatePublished - Dec 1 1998

Fingerprint

Physics

All Science Journal Classification (ASJC) codes

  • Software

Cite this

@article{805eb1683fbe46cb83f59cc4b487c094,
title = "Requirements development in scenario-based design",
abstract = "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 kinds 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.",
author = "John Carroll",
year = "1998",
month = "12",
day = "1",
doi = "10.1109/32.738344",
language = "English (US)",
volume = "24",
pages = "1156--1170",
journal = "IEEE Transactions on Software Engineering",
issn = "0098-5589",
publisher = "Institute of Electrical and Electronics Engineers Inc.",
number = "12",

}

Requirements development in scenario-based design. / Carroll, John.

In: IEEE Transactions on Software Engineering, Vol. 24, No. 12, 01.12.1998, p. 1156-1170.

Research output: Contribution to journalArticle

TY - JOUR

T1 - Requirements development in scenario-based design

AU - Carroll, John

PY - 1998/12/1

Y1 - 1998/12/1

N2 - 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 kinds 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.

AB - 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 kinds 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.

UR - http://www.scopus.com/inward/record.url?scp=0032305518&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=0032305518&partnerID=8YFLogxK

U2 - 10.1109/32.738344

DO - 10.1109/32.738344

M3 - Article

AN - SCOPUS:0032305518

VL - 24

SP - 1156

EP - 1170

JO - IEEE Transactions on Software Engineering

JF - IEEE Transactions on Software Engineering

SN - 0098-5589

IS - 12

ER -