Build and fix life-cycle model in software engineering

Build and Fix Life-Cycle Model

This is also known as Ad-hoc Model. This is the original and probably most widely used software life-cycle model or process model.
it is unfortunate that many software products are developed using what might be termed as Build and Fix approach. The software is developed without first addressing specifications or design. Instead the developer simply build a product that is reworked as many times a necessary until it satisfies it's client.

Instead of Build and Fix approach, it is essential that before of development of product begins, an overall process model be chosen. The process model specifies the various phases of the software process, such as the requirement specifications, planning, design, implementation, integration and maintenance phase, and the order in which they are to be carried out. Once the process model has been agreed to by all the parties concerned, development of product can begin.

NOTE:-Until early 1980, the waterfall model was the only widely accepted model.

Limitations of Build and Fix Life-cycle Model

  • This approach may work well on problems having about 100 or 200 lines long but is totally unsatisfactory products of any reasonable size.
  • Cost of this model is high if the specification are drown up and a design carefully developed.
  • Maintenance of product is extremely very difficult in the absence of specification or design documents
  • Chances of an regression fault occurring are considerably high.
  • The cost of this process model is actually far greater in comparison of the cost of a properly specified and designed project.

Post a comment