Build-and-fix model

From Dr. Joey Paquet Web Site
Revision as of 21:10, 14 November 2013 by Paquet (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

In this most simple model of software development, the product is constructed with minimal requirements, and generally no specifications nor any attempt at design, and testing is most often neglected. This is a representation of what is happening in many software development projects. Note that this way of doing is not only a counter-example: it has its benefits in some situations.

Advantages

  • Cost efficient for very small projects of limited complexity.

Disadvantages

  • Unsatisfying approach for products of reasonable size.
  • Cost is higher for larger projects.
  • Product will not be delivered on time most of the times.
  • Often results in a product of overall low quality.
  • No documentation is produced.
  • Maintenance can be extremely difficult without specification and design document.