Control of software prototyping process: change classification approach
Information and Software Technology
Organization and management of systems prototyping
Information and Software Technology - New directions in software development
Executive information requirements: getting it right
MIS Quarterly
Prototyping in Industrial Software Projects-Bridging the Gap Between Theory and Practice
IEEE Transactions on Software Engineering
Making use: a design representation
Communications of the ACM
Work processes: scenarios as a preliminary vocabulary
Scenario-based design
Scenarios in discount usability engineering
Scenario-based design
Communications of the ACM
Systems Analysis and Design Methods
Systems Analysis and Design Methods
Systems Analysis and Design Methods
Systems Analysis and Design Methods
Computers in Context: The Philosophy and Practice of Systems Design
Computers in Context: The Philosophy and Practice of Systems Design
Scenarios in System Development: Current Practice
IEEE Software
Phased System Design, Development, and Implementation: Process and Technology
Proceedings of the IFIP WG8.2 Working Conference on The Impact of Computer Supported Technologies in Information Systems Development
Using Communication Theory for Systems Design: A Model for Eliciting Information Requirements
Proceedings of the IFIP WG8.2 Working Group on Information Systems Development: Human, Social, and Organizational Aspects: Human, Organizational, and Social Dimensions of Information Systems Development
| Hi-index | 0.00 |
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.