1 Re: what are the advantages and disadvantages of waterfall model? Answer #1 DisAdvatages 1.

Inflexible partitioning of the project into distinct stages makes it difficult to respond to changing customer requirements. 2. The lifecycle can take so long that the original requirements may no longer be valid by the time the system is implemented. 3. Estimating time and costs is difficult for each stage. 2 Re: what are the advantages and disadvantages of waterfall model? Answer #2 actually the waterfall model is a dependent model. so in the every phase depends upon another phase.So after completion one phase(sdlc) then goes to next phase. for example after completion of coding testing should happen.it should dependent. If u want to add any new requirement it should be so cost effective. advantage is cheaper. Re: what are the advantages and disadvantages of waterfall model? Answer #3 Advantages: Model is simple. Easy to understand. Disadvantages: Time consuming as the testing process starts the last stages till the build is given for testing the testers will be idle. hence man power is wasted Advantages: it is simple and easy to understand. it takes less cost. disadvantages: in this stage every phase requirements are freezed. we can't do modifications. Advantages of Waterfall Model 1. Clear project objectives. 2. Stable project requirements. 3. Progress of system is measurable. 4. Strict sign-off requirements. Disadvantages of Waterfall Model 1. Time consuming 2. Never backward (Traditional) 3. Little room for iteration 4. Difficulty responding to changes Re: what are the advantages and disadvantages of waterfall model? Answer #8

It is difficult to accommodate any change after the requirement is finished or we can say that it freeze the requirement phase Re: what are the advantages and disadvantages of waterfall model? Answer #9 ADVANTAGE 1) helps you to be perfect. 2) logic of software development is clearly understood. 3) Project management. i.e; a)assurance of task completed. b)better project review. c)better resource allocation. d)better resource utilization. project planning is best done in waterfall model. Re: what are the advantages and disadvantages of waterfall model? Answer # 10 Advantage: Less human resources required as once one phase is finished those people can start working on to the next phase. The main drawback of the waterfall model is the difficulty of accommodating change after the process is underway. One phase has to be complete before moving onto the next phase. Inflexible partitioning of the project into distinct stages makes it difficult to respond to changing customer requirements. Therefore, this model is only appropriate when the requirements are wellunderstood and changes will be fairly limited during the design process. Few business systems have stable requirements. The waterfall model is mostly used for large systems engineering projects where a system is developed at several sites. Disadvantage of waterfall model it doesnt allow for much revision and reflection once an app;ication is in testing stage its difficult to go back and change something that wasnt well thought out in concept stage The Waterfall Model The most important aspect of the waterfall model is that unless a particular stage is complete, the next stage cannot be started off with. Here, in this article, we will try to understand a simple waterfall model, broken into six stages. Let us try to understand each of these stages one by one. Stage 1: Requirement Phase Whether you design a small program to add two numbers or you are into developing a software system for the automation of an entire airline company, this is the first stage which can never be overridden. Unless you know what you are going to design, you cannot approach the problem. Here, the specifications of the output or the final product is studied and marked. Stage 2: Specification Phase With all the requirements and constraints in hand, a final view of how the product should exactly be, is decided. The exact way in which the software should function is mentioned in this stage.

Stage 3: Design Phase: Here the actual work begins. Every type of resource which will be required for the smooth designing of the software, is mentioned here in this phase. What type of database will be required, what type of data should be supported, etc. are some of the important aspects that are decided in this phase. The algorithm of the process in which the software needs to be designed, is made in this phase. This algorithm forms the backbone for the actual coding process, that takes place in the next phase. Stage 4: Implementation and Testing Phase Now starts the coding. Here, the software is coded as per the algorithm. Hence it becomes very important that the algorithm should be properly designed. The software designed, needs to go through constant software testing and error correction processes to find out if there are any flaw or errors. Stage 5: Integration and Testing Phase Here the various codes designed by different programmers are integrated and is tested if the software works as per the specifications provided. The setup of the final software which needs to be installed at the clients system, is also designed and tested, so that the client does not face any problem during the installation of the software. The product is then handed over to the client. Stage 6: Maintenance Phase The cycle of software development does not end with handing the software to the client. Software designers may have to constantly provide support to the client to resolve any issues which may arise. During the maintenance phase, support and debugging is provided for all such problems. Advantages and Disadvantages Advantages The waterfall model is the oldest and most widely used model in the field of software development. There are certain advantages of this model, which makes it, one of the most widely used models as yet. Some of them are: Being a linear model, it is very simple to implement. The amount of resources required to implement this model are minimal. Documentation is produced at every stage of the software's development. This makes understanding the product designing procedure, simpler. After every major stage of software coding, testing is done to check the correct running of the code. Disadvantages The question that must be bothering you now is that with so many advantages at hand, what could be the possible disadvantages of the waterfall model? Here are a few: Ironically, the biggest disadvantage is one of its greatest advantages. You cannot go back a step; if the design phase has gone wrong, things can get very complicated in the implementation phase. Often, the client is not very clear of what he exactly wants from the software. Any changes that he mentions in between, may cause a lot of confusion. Small changes or errors that arise in the completed software may cause a lot of problems. Until the final stage of the development cycle is complete, a working model of the software does not lie in the hands of the client. Thus, he is hardly in a position to inform the developers, if what has been designed is exactly what he had asked for.

SPIRAL MODEL

Advantages
1. This model improves avoidance of risk 2. This model is very useful to choose a methodology for a software iteration 3. This model can associate other methodologies like Waterfall, Prototyping, and Incremental methodologies. Suppose a project having a low risk of not meeting the user requirement and on other side having high risk of missing budget would follow waterfall approach 4. In this model more functionality can be added in later versions.

Disadvantages
1. This model limiting reusability 2. This model is quite complex 3. Spiral model is very customized for every project 4. To use this model an experienced and skilled team required 5. There is no proper control to move from one cycle to another cycle

Spiral Model Merits:-- This model is an example of evolutionary model and combines the features
of the prototyping model and the waterfall model . Estimates (i.e. Budget, schedule, etc.) become more realistic as work progresses, because important issues are discovered earlier. Software engineers can get their hands in and start working on a project earlier. Prototyping is used as a risk reduction mechanism After final iteration, all risks are resolved and the requirements are ready for development. Demerits:-- The spiral model is intended for large, expensive and complicated projects. Highly customized limiting re-usability. Risk of not meeting budget or schedule. Requires considerable expertise in risk evaluation and reduction. Complex, relatively difficult to follow strictly Advantages: Risk reduction mechanisms are in place Supports iteration and reflects real-world practices Systematic approach Disadvantages: Requires expertise in risk evaluation and reduction Complex, relatively difficult to follow strictly Applicable only to large systems Idris Lawal Merits: 1) dynamic requirement changes present. 2) integration testing is present

demerits:
1) time taken to deliver the product is more 2) only intended to large and complicated project

Merits:
1) dynamic requirement changes present. 2) integration testing is present 3)changes made in one module will not have any impact on another demerits1) time taken to deliver the product is more 2) only intended to large and complicated project