answersLogoWhite

0


Best Answer

Waterfall model tends to consume a lot more time compared to other software development models though it is able to pinpoint definite starting and ending points for a given project. This model assumes the requirements to remain static during the life of the project, so there is little or no chance of incorporating new changes to the software once work begins. If changes are tried to be incorporated it leads to more confusion and further delays. Its strong points lie in the fact that it is sequential, so there would be no confusion on the steps and the processes are straight down--no need to worry about so many conditions while working on a project. Additionally, this type of model tends to pack up on so much documentation. Therefore, such tends to be useful for future code revisions and reference. However, its drawbacks become apparent in the length of time a project will be developed and the cost it is able to consume.

User Avatar

Wiki User

15y ago
This answer is:
User Avatar
More answers
User Avatar

Wiki User

15y ago

•Simple and easy to use

•Easy to manage due to the rigidity of the model - each phase has specific deliverables and a review process.

•Phases are processed and completed one at a time.

•Works well for smaller projects where requirements are very well understood

This answer is:
User Avatar

User Avatar

Wiki User

15y ago

An Advantage is that it is reasonably good for new projects and it is a good model to teach

The Main Disadvantage of the waterfall model is that it does not allow for very much Iteration.

for example you are in the testing stage and you realize that something has not been designed correctly.

In theory if following the model as closely as possible and trying to make it iterative this would lead you back to the design stage and then through the implementation until you arrived back at testing again

This answer is:
User Avatar

User Avatar

Wiki User

9y ago

Waterfall model has following advantages :

1) Each stage has well defined deliverable or milestones.

2) It acts as a template (guiding model) into which methods for analysis, design, code, test and maintenance can be placed.

This answer is:
User Avatar

User Avatar

Wiki User

14y ago
  • Time Consuming
  • Costly
  • Programmer can not move on to the next step unless the previous is completed
This answer is:
User Avatar

User Avatar

Wiki User

9y ago

In water fall model we have to make a product in one go we cannot go back into previous phase. In prototype model we make test product that depicts what our end product will look like.

This answer is:
User Avatar

Add your answer:

Earn +20 pts
Q: Why should you use waterfall model in software projects?
Write your answer...
Submit
Still have questions?
magnify glass
imp
Related questions

Which software industries are using waterfall model for software development?

All industries are using the waterfall model for software development.


What is Waterfall Solutions?

Waterfall is one of the software development life cycle model. Waterfall model has five stages.


Which model is simplest model in Software Development?

Waterfall model


Is waterfall model of software engineer a flexible model?

No, water fall model in software engineering is not a flexible model . Waterfall model have certain limitations like we can not go back into earlier phase .


What is the Difference between RAD model and waterfall model?

The RAD model, also known as the Rapid Application Development, is a linear software for creating prototypes. The Waterfall model is a sequential software.


Which is the best software life cycle model?

Waterfall model is the best software life cycle model.


What is the iterative waterfall?

Iterative waterfall model is a software process model also called the incremental process model. http://en.wikipedia.org/wiki/Iterative_and_incremental_development


Waterfall model of the software life cycle?

It consists of different stages of software life cycle.


Which phase consumes the maximum effort in waterfall model for developing a software product and why?

The testing phase consumes the maximum effort in waterfall model.


Discuss the advantages of waterfall model?

Advantage: - 1-You get the software according to your demand. 2-It is best for small projects. 3-It is very much sequential & systematic.


What is water fall model?

The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design (validation), Construction, Testing and maintenance. The unmodified "waterfall model". Progress flows from the top to the bottom, like a waterfall.It should be readily apparent that the waterfall development model has its origins in the manufacturing and construction industries; highly structured physical environments in which after-the-fact changes are prohibitively costly, if not impossible. Since no formal software development methodologies existed at the time, this hardware-oriented model was simply adapted for software development. Ironically, the use of the waterfall model for software development essentially ignores the 'soft' in 'software'. The first formal description of the waterfall model is often cited to be an article published in 1970 by Winston W. Royce (1929-1995), although Royce did not use the term "waterfall" in this article. Ironically, Royce was presenting this model as an example of a flawed, non-working model (Royce 1970). This is in fact the way the term has generally been used in writing about software development-as a way to criticize a commonly used software practice.


What is the water fall model?

The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design (validation), Construction, Testing and maintenance. The unmodified "waterfall model". Progress flows from the top to the bottom, like a waterfall.It should be readily apparent that the waterfall development model has its origins in the manufacturing and construction industries; highly structured physical environments in which after-the-fact changes are prohibitively costly, if not impossible. Since no formal software development methodologies existed at the time, this hardware-oriented model was simply adapted for software development. Ironically, the use of the waterfall model for software development essentially ignores the 'soft' in 'software'. The first formal description of the waterfall model is often cited to be an article published in 1970 by Winston W. Royce (1929-1995), although Royce did not use the term "waterfall" in this article. Ironically, Royce was presenting this model as an example of a flawed, non-working model (Royce 1970). This is in fact the way the term has generally been used in writing about software development-as a way to criticize a commonly used software practice.