what is Iterative or Incremental Model?

By -
An iterative life cycle model does not attempt to start with a full specification of requirements. Instead, development begins by specifying and implementing just part of the software, which can then be reviewed in order to identify further requirements. This process is then repeated, producing a new version of the software for each cycle of the model.

  • Requirements phase, in which the requirements for the software are gathered and analyzed. Iteration should eventually result in a requirements phase that produces a complete and final specification of requirements.
  • Design phase, in which a software solution to meet the requirements is designed. This may be a new design, or an extension of an earlier design.
  • Implementation and Test phase, when the software is coded, integrated and tested.
  • Review phase, in which the software is evaluated, the current requirements are reviewed, and changes and additions to requirements proposed. 
For each cycle of the model, a decision has to be made as to whether the software produced by the cycle will be discarded, or kept as a starting point for the next cycle.As the software evolves through successive cycles, tests have to be repeated and extended to verify each version of the software.

Advantages
  • Some working functionality can be developed quickly and early in the life cycle.
  • Results are obtained early and periodically.
  • Parallel development can be planned.
  • Progress can be measured.
  • Less costly to change the scope/requirements.
  • Testing and debugging during smaller iteration is easy.
  • Risks are identified and resolved during an iteration; and each iteration is an easily managed milestone.
  • Easier to manage risk - High risk part is done first.
  • With every increment operational product is delivered.
  • Issues, challenges & risks identified from each increment can be utilized/applied to the next increment.

Disadvantages 

  • More resources may be required.
  • Although cost of change is lesser but it is not very suitable for changing requirements.
  • More management attention is required.
  • Each phase of an iteration is rigid with no overlaps.
  • System architecture or design issues may arise because not all requirements are gathered. up front for the entire life cycle.
  • Does not allow iterations within an increment.
  • Defining increments may require definition of the complete system.

Comments

Post a Comment

Popular posts from this blog

what is Modified Waterfall Model?

By -
Image
In response to the perceived problems with the "pure" waterfall model, many modified waterfall models have been introduced. These models may address some or all of the criticisms of the "pure"  waterfall model. In Water fall method , there is no VALIDATION OR VERIFICATION between the phases , so the customer will finally get unsatisfied product. This Modified Waterfall Model Involves VALIDATION or VERIFICATION between the phases , so any deviations can be corrected immediately , providing the customer satisfaction, so this is preferred.
Read more

what is Prototype Model?

By -
Image
The goal of prototyping based development is to counter the first two limitations of the waterfall model. This prototype is developed based on the currently known requirements. Development of the prototype obviously undergoes design, coding and testing. But each of these phases is not done very formally or thoroughly. By using this prototype, the client can get an "actual feel" of the system. Advantages It could serve as the first system. Prototyping is an attractive idea for complicated and large systems for which there is no manual  process or existing system to help determining the requirements. The customer doesn’t need to wait long as in the Linear Model. Feedback from customers are received periodically and the changes don’t come as a last minute surprise. Users are actively involved in the development It provides a better system to users, as users have natural tendency to change their mind in specifying requirements and this method of developing systems s
Read more

What is User Documentation Testing

By -
User Documentation  covers all the manuals, user guides, installation guides, setup guides, read me files,software release notes, and online help that are provided along with the software to help the end user to understand the software system. User Documentation Testing should have two objectives:- To check if what is  stated in the document is available in the software To check if what is there in the product is explained correctly in the document This testing is plays a vital role as the users will refer this document when they start using the software at their location.a badly written document can put off a user and bias them against the product even the product offers rich functionality. Defects found in the user documentation need to be tracked to closure like any regular software defect.Because these documents are the first interactions the users have with the product. A good User Documentation  aids in reducing customer support calls.The effort and money spend on this effort
Read more