Friday, December 28, 2012

Incremental Model

Incremental Model
Incremental Model

  • Constructs a partial implementation of a total system.
  • Then slowly adds increased functionality.
  • The incremental model prioritizes requirements of the system and then implements them in groups.
  • Each subsequent release of the system adds function to the previous release, until all designed functionality has been implemented.

Incremental Model Strengths:
Incremental Model - SDLC
Incremental Model

  • Develop high-risk or major functions first.
  • Each release delivers an operational product.
  • Customer can respond to each build.
  • Uses  “divide and conquer” breakdown of tasks.
  • Lowers initial delivery cost.
  • Initial product delivery is faster.
  • Customers get important functionality early.
  • Risk of changing requirements is reduced.

Incremental Model Draw Backs:

  • Requires good planning and design.
  • Requires early definition of a complete and fully functional system to allow for the definition of increments.
  • Well-defined module interfaces are required (some will be developed long before others).
  • Total cost of the complete system is not lower.

When to use Incremental Model:

  • Risk, funding, schedule, program complexity, or need for early realization of benefits.
  • Most of the requirements are known up-front but are expected to evolve over time.
  • A need to get basic functionality to the market early.
  • On projects which have lengthy development schedules.
  • On a project with new technology.

No comments:

Post a Comment

I would like to thank you for your comments..! Please keep commenting. To get posts and updates via mail, I would suggest you to subscribe the Blog. Thanks Again..!

Google Search