Q: What are the most exciting, promising software engineering ideas or techniques on the horizon? A: I don't think that the most promising ideas are on the horizon. They are already here and have been for years, but are not being used properly. David L. Parnas OVERVIEW Research, historical, and other evidence related to IID. Evidence of waterfall risks. Business case for skills transfer to adopt IID.
Some have no need to justify iterative development. Others need to make a case; this material can help. For students of software engineering methods or those needing to motivate an iterative experiment, this chapter provides some data, in several categories: research evidence | expert thought leader advice | early large projects | business case | standards-body advice | waterfall problems |
IID practices have been entrenched for years in some development markets, yet some government standards still promote single-pass, document-driven, waterfall development, as do some larger IT and consulting organizations, government and military service suppliers, engineering curriculums, and many requirements texts. For example, the Call For Papers in the 2002 Time-Constrained Requirements Engineering workshop stated: In general, requirements engineering literature has been working with the assumption that a system should be clearly specified before its design and implementation can start. | 