Explain Phases of the waterfall model

Introduction to Software development life cycle, phases of SDLC, Requirements Gathering, Analysis & Planning, Software design, Coding, Testing, and Release & Maintenance.
Post Reply
Ram
Posts: 1
Joined: Mon Dec 10, 2018 7:29 am

Explain Phases of the waterfall model

Post by Ram » Mon Dec 10, 2018 7:41 am

Explain Phases of the waterfall model?

Shiv
Posts: 1
Joined: Mon Dec 10, 2018 7:37 am

Re: Explain Phases of the waterfall model

Post by Shiv » Mon Dec 10, 2018 7:45 am

The five-main phase of waterfall model are:

Requirements gathering
Design
Development
Testing
Implementation & Maintenance

adi_31
Posts: 15
Joined: Fri Dec 07, 2018 11:28 am

Re: Explain Phases of the waterfall model

Post by adi_31 » Mon Dec 10, 2018 12:04 pm

I just wanted this answer and i got here. Thanks.!!

chowdarybabu
Posts: 18
Joined: Thu Jan 03, 2019 3:52 am

Re: Explain Phases of the waterfall model

Post by chowdarybabu » Sat Jan 05, 2019 8:07 am

In “The Waterfall” approach, the whole process of software development is divided into separate phases. The outcome of one phase acts as the input for the next phase sequentially. This means that any phase in the development process begins only if the previous phase is complete. The waterfall model is a sequential design process in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production/Implementation, and Maintenance.

As the Waterfall Model illustrates the software development process in a linear sequential flow; hence it is also referred to as a Linear-Sequential Life Cycle Model.

Requirements
System design
Implementation
Integration and testing
Development of system
Maintenance

Requirements: The first phase involves understanding what need to be design and what is its function, purpose
etc. Here, the specifications of the input and output or the final product are studied and marked.
System Design: The requirement specifications from first phase are studied in this phase and system design is
prepared. System Design helps in specifying hardware and system requirements and also helps in
defining overall system architecture. The software code to be written in the next stage is created
now.
Implementation: With inputs from system design, the system is first developed in small programs called units,
which are integrated in the next phase. Each unit is developed and tested for its functionality
which is referred to as Unit Testing.
Integration and Testing: All the units developed in the implementation phase are integrated into a system after
testing of each unit. The software designed, needs to go through constant software
testing to find out if there are any flaw or errors. Testing is done so that the client does
not face any problem during the installation of the software.
Deployment of System: Once the functional and non-functional testing is done, the product is deployed in the
customer environment or released into the market.
Maintenance: This step occurs after installation, and involves making modifications to the system or an individual
component to alter attributes or improve performance.These modifications arise either due to
change requests initiated by the customer, or defects uncovered during live use of the system.
Client is provided with regular maintenance and support for the developed software.

satyanarayanareddy
Posts: 17
Joined: Thu Jan 03, 2019 3:54 am

Re: Explain Phases of the waterfall model

Post by satyanarayanareddy » Sat Jan 05, 2019 8:09 am

What are the Advantages and Dis-Advantages of WaterFall Model

sekhar
Posts: 42
Joined: Mon Dec 31, 2018 6:40 am

Re: Explain Phases of the waterfall model

Post by sekhar » Sat Jan 05, 2019 10:30 am

Advantages of Waterfall Model:
===========================
*The advantage of waterfall development is that it allows for departmentalization and control. A schedule can be set with deadlines for each stage of development and a product can proceed through the development process model phases one by one.
*The waterfall model progresses through easily understandable and explainable phases and thus it is easy to use.
*It is easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process.
*In this model, phases are processed and completed one at a time and they do not overlap. Waterfall model works well for smaller projects where requirements are very well understood.

Disadvantages of Waterfall Model:
=============================
*It is difficult to estimate time and cost for each phase of the development process.
*Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage.
*Not a good model for complex and object-oriented projects.
*Not suitable for the projects where requirements are at a moderate to high risk of changing.

kishore
Posts: 55
Joined: Thu Jan 03, 2019 3:57 am

Re: Explain Phases of the waterfall model

Post by kishore » Mon Jan 07, 2019 7:36 am

Phases of the waterfall model
Image

srini
Posts: 76
Joined: Thu Jan 03, 2019 3:58 am

Re: Explain Phases of the waterfall model

Post by srini » Fri Jan 18, 2019 4:24 am

Advantages of waterfall model:
==============================
=>This model is simple and easy to understand and use.
=>It is easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process.
=>In this model phases are processed and completed one at a time. Phases do not overlap.
=>Waterfall model works well for smaller projects where requirements are clearly defined and very well understood.

Disadvantages of waterfall model:
=================================
=>Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage.
=>No working software is produced until late during the life cycle.
=>High amounts of risk and uncertainty.
=>Not a good model for complex and object-oriented projects.
=>Poor model for long and ongoing projects.
=>Not suitable for the projects where requirements are at a moderate to high risk of changing.

Post Reply

Return to “Software Development Life Cycle”