Iterative Enhancement Software Model

Iterative Enhancement Software Model Assignment Help | Iterative Enhancement Software Model Homework Help

Iterative Enhancement Software Model

In this model, it has been proposed that the changes in the software system throughout its lifetime are an iterative process. This model is used where requirement were not fully understood and a full system could not be built.

Adapted for maintenance, the model assumes complete documentation as it relies on modification of this as the starting point of each iteration. The model is effectively a three stage cycle.
•    Analysis
•    Characterization of proposed modifications
•    Redesign and implementation.

Iterative enhancement model

The existing documentation of each stage (requirements, design, coding, testing and analysis) is modified starting with highest-level document affected by the proposed changes. These modifications are propagated through the set of documents and the system is redesigned. The model explicitly supports reusability of codes and also accommodates other models, for example the quick-fix model.

The pressure of the maintenance environment often dictates that a quick solution is found but, as we have seen, the use of the quickest solution can lead to more problems than it solves. In the first iteration, problem areas would be identified and next iteration would specifically address the problem.

The problems with this model are the assumptions made about the existence of full documentation and the ability of the maintenance team to analyze the existing product in full. Wider use of structured maintenance models will lead to a culture where documentation tends to be kept upto date and complete, the current situation is that this is not often the case.

For more help in Iterative Enhancement Software Model click the button below to submit your homework assignment