This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Fast, Cheap Requirements: Prototype, or Else!
March/April 1994 (vol. 11 no. 2)
pp. 85-87

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.

Index Terms:
software prototyping; formal specification; systems analysis; cheap requirements prototype; requirements modeling management; prototyping process; requirements modeling; throwaway prototyping; exploratory prototyping; initial requirements; constraints; specification; interactive prototyping; requirements validation
Citation:
"Fast, Cheap Requirements: Prototype, or Else!," IEEE Software, vol. 11, no. 2, pp. 85-87, March-April 1994, doi:10.1109/MS.1994.10015
Usage of this product signifies your acceptance of the Terms of Use.