Incremental Process Model
• Combines elements of linear and parallel process flows.
• It delivers a series of releases, called increments that provide progressively more functionality for the customer as each is delivered
• The first increment is often a core product.
• The plan addresses the modification of the core product to better meet the needs of the customer and the delivery of additional feature and functionality.
• It focuses on the delivery of an operational product with each increment.
• It is useful when staffing is unavailable for a complete implementation.
• Increments can be planned to manage technical risks.
Spiral model:
• Originally proposed by Barry Boehm.
• It couples the iterative nature of prototyping with the controlled and systematic aspects of water fall model.
• The process is represented as a spiral rather than as a sequence of activities with backtracking.
• Each loop in the spiral represents a phase in the process.
• No fixed phases such as specification or design - loops in the spiral are chosen depending on what is required.
• Risks are explicitly assessed and resolved throughout the process.
• It is a realistic approach to the development of large-scale systems and software.
• The software evolves as the process progresses, the developer and customer better understand and react at each evolutionary level.
• It uses prototyping as a risk reduction mechanism.
• It demands considerable risk assessment expertise and realises this expertise for success.
I hope this article is useful to you, plz follow the next volume for more information.
You can write to me at codingallrounders@gmail.com
please post your doubts in the comment box.
Subscribe by Email
Follow Updates Articles from This Blog via Email
No Comments