Fast, Cheap Requirements: Prototype, or Else!

Authors:
Stephen J. Andriole
Affiliations:
-
Venue:
IEEE Software
Year:
1994

Citing 0
Cited 7

An Integrated Approach to Designing and Evaluating CollaborativeApplications and Infrastructures

Computer Supported Cooperative Work
A Framework for Requirements Elicitation through Mixed-Initiative Dialogue

ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Collaborative architecture design and evaluation

DIS '06 Proceedings of the 6th conference on Designing Interactive systems
Pseudo software: A mediating instrument for modeling software requirements

Journal of Systems and Software
Interactive Visualization for Elicitation and Validationn of Requirements with Scenario-Based Prototyping

REV '09 Proceedings of the 2009 Fourth International Workshop on Requirements Engineering Visualization
Designing visual analytics systems for organizational environments

Proceedings of the 2011 Visual Information Communication - International Symposium
Systematizing requirements elicitation technique selection

Information and Software Technology

Quantified Score

Hi-index	0.00

Visualization

Abstract

Managing requirements modeling and prototyping is risky. If things go awry, projects can spiral out of control. Over the years, with the help of colleagues from industry and academia, the author has identified a requirements modeling and prototyping process that is fast, powerful, cost-effective, sane, and objective. The main lesson learnt is that throwaway prototyping (sometimes called exploratory prototyping) is always cost-effective and always improves specifications. The process has nine steps: elicit initial requirements; model requirements; identify constraints; prioritize initial requirements; design; evaluate designs; specification; interactive prototyping; and requirements validation.