what is Waterfall Model?

The waterfall model is a sequential SDLC model in which development is seen as flowing steadily downwards (like a waterfall) through several phases.
The waterfall model maintains that one should move to a phase only when its preceding phase is completed and perfected. Phases of development in the waterfall model are thus discrete, and there is no jumping back and forth or overlap between them.

The most probable phases through which it progresses downwards are
  1. Definition Study/Analysis
  2. Basic Design
  3. Technical Design/Detailed Design
  4. Construction
  5. Testing
  6. Integration
  7. Management and
  8. Maintenance




  • Definition Study / Analysis: During this phase research is being conducted which includes brainstorming about the software, what it is going to be and what purpose is it going to fulfill. 
  • Basic Design: If the first phase gets successfully completed and a well thought out plan for the software development has been laid then the next step involves formulating the basic design of the software on paper. 
  • Technical Design / Detail Design:  After the basic design gets approved, then a more elaborated technical design can be planned. Here the functions of each of the part are decided and the engineering units are placed for example modules, programs etc. 
  • Construction / Implementation: In this phase the source code of the programs is written. 
  • Testing: At this phase, the whole design and its construction is put under a test to check its functionality. If there are any errors then they will surface at this point of the process. 
  • Integration: in the phase of Integration, the company puts it in use after the system has been successfully tested. 
  • Management and Maintenance: Maintenance and management is needed to ensure that the system will continue to perform as desired.

Advantages of the Waterfall Model

  •    The project requires the fulfillment of one phase, before proceeding to the next. Therefore if there is a fault in this software it will be detected during one of the initial phases and will be sealed off for correction.
  •    A lot of emphasis is laid on paperwork in this method as compared to the newer methods. When new workers enter the project, it is easier for them to carry on the work from where it had been left. The newer methods don’t document their developmental process which makes it difficult for a newer member of the team to understand what step is going to follow next. The Waterfall Model is a straight forward method and lets one know easily what stage is in progress.
  •    The Waterfall method is also well known amongst the software developers therefore it is easy to use. It is easier to develop various software through this method in short span of time.
Disadvantages of the Waterfall Model

  •     not suitable for change driven projects
  •     not fit for large projects    
  •    huge amount of time is also wasted like Phase II cannot be executed until Phase I has been successfully completed; so while the designers are still designing the software, time of the builders is completely wasted.
  •    the testing period comes quite late in the developmental process Elaborate documentation during the Waterfall method has its advantages, but it is not without the disadvantages as well. It takes a lot of effort and time, which is why it is not suitable for smaller projects.

Comments

Post a Comment

Popular posts from this blog

what is Modified Waterfall Model?

what is Prototype Model?

What is User Documentation Testing