
Water-fall model:
• Oldest software lifecycle model & best understood by upper management
• Used when requirements are well understood, and risk is low
• Workflow is in a linear fashion.
• Used often with well-defined adaptations or enhancements to current software
Disadvantages:
• Real projects rarely follow the sequential flow.
• Difficult for customers to state all requirements explicitly and up front
• Requires customer patience because a working version of the program doesn't occur until the final phase
• Doesn't support iteration, so changes can cause confusion and Leads to “blocking states”.
Advantages:
• Where requirements are fixed and are to proceed to completion in a linear manner.
I hope this article is useful to you, plz follow the next volume for more information.
please post your doubts in the comment box.
You can write to me at codingallrounders@gmail.com
Subscribe by Email
Follow Updates Articles from This Blog via Email
No Comments