Software-Engineering
August 25, 2024Software-Engineering
August 25, 2024Software-Engineering
| Question 259 |
Working software is not available until late in the process in
| Waterfall model | |
| Prototyping model | |
| Incremental model | |
| Evolutionary Development model |
Question 259 Explanation:
Waterfall Model: We can not go back in previous project phase as soon as as we proceed to next phase ,So inflexible
Advantages:
→Waterfall model is simple and easy to understand.
→It works as reference model for others.
Disadvantage:
→Real projects cannot be sequential
→Initially all requirements should known i.e requirements are frozen. It may be suited for static projects.
→Error omission too costly
→Maintenance is too costly(We have to redesign the whole project from scratch)
→Customer must have patience
→It is based on Big-Bang approach
Advantages:
→Waterfall model is simple and easy to understand.
→It works as reference model for others.
Disadvantage:
→Real projects cannot be sequential
→Initially all requirements should known i.e requirements are frozen. It may be suited for static projects.
→Error omission too costly
→Maintenance is too costly(We have to redesign the whole project from scratch)
→Customer must have patience
→It is based on Big-Bang approach
Correct Answer: A
Question 259 Explanation:
Waterfall Model: We can not go back in previous project phase as soon as as we proceed to next phase ,So inflexible
Advantages:
→Waterfall model is simple and easy to understand.
→It works as reference model for others.
Disadvantage:
→Real projects cannot be sequential
→Initially all requirements should known i.e requirements are frozen. It may be suited for static projects.
→Error omission too costly
→Maintenance is too costly(We have to redesign the whole project from scratch)
→Customer must have patience
→It is based on Big-Bang approach
Advantages:
→Waterfall model is simple and easy to understand.
→It works as reference model for others.
Disadvantage:
→Real projects cannot be sequential
→Initially all requirements should known i.e requirements are frozen. It may be suited for static projects.
→Error omission too costly
→Maintenance is too costly(We have to redesign the whole project from scratch)
→Customer must have patience
→It is based on Big-Bang approach