Conversation about software requirements with prototypes and scenarios

David Bahn, J. David Naumann, Shawn Curley

Research output: Chapter in Book/Report/Conference proceedingConference contribution

1 Scopus citations


Determining the functional requirements for new software is a significant problem because it is dependent upon effective conversation between software designers and users. Prototypes and scenarios are two key techniques that have been advocated to improve the specification and communication of software requirements. This paper describes experimental research examining the utilization of prototypes and scenarios during designer-user conversation to determine and validate software requirements. This study is among the first to empirically test the effectiveness of employing scenarios in requirements determination. The results indicate that scenarios can affect user feedback in conversation about software requirements. The results also suggest that software designers should present users with a combination of software prototypes alongside abstract, diagrammatic models when discussing software requirements.

Original languageEnglish (US)
Title of host publicationNext Generation Information Technologies and Systems - 5th International Workshop, NGITS 2002, Proceedings
EditorsAvigdor Gal, Alon Halevy
PublisherSpringer Verlag
Number of pages11
ISBN (Electronic)354043819X, 9783540438199
StatePublished - Jan 1 2002
Event5th International Workshop on Next Generation Information Technologies and Systems, NGITS 2002 - Caesarea, Israel
Duration: Jun 24 2002Jun 25 2002

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349


Other5th International Workshop on Next Generation Information Technologies and Systems, NGITS 2002


Dive into the research topics of 'Conversation about software requirements with prototypes and scenarios'. Together they form a unique fingerprint.

Cite this