Waterfall Model

What is the Waterfall Model?

The acronym (SDLC) which stands for System Development Life Cycle was the earliest to utilize for the system development and it is called "The Waterfall Model". It can also be called as the "Linear-Sequential Life Cycle Model". The waterfall model illustrates software growth procedure in a liner sequential flow. If the previous stage is completed, the growth process shall begin. The progression in the waterfall model is distinguished as flowing gradually downwards through the stages as all these phases are arrange in a series or sequence to each other. The firstly phase should be finished before continuing to the following stage and the next phase will only start later at the specified allocated of goals are attained and checked. This only means that each stage is relied on the phase before it.The important part is that phases does not overlap in the waterfall model.

What are the sequential stages of the waterfall model?

• Requirement Gathering and Analysis -Entirely attainable pre-requisite of the system to be broaden are accumulated in this stage and written or documented/written in a request or pre-requisite identification document.

• System Design − The demand designation from the first stage are examined in this stage and the system model is produce. This structure model helps in recognizing hardware and structure desire and helps in determining the general system formation.

• Implementation − With information from the structure model, the system is first generated in small agenda called units, which are integrate in the next stage. Each unit is supported and tested for its usefulness, which is called as Unit Testing.

• Integration and Testing − All the components manufactured in the achievement phase are mixed into a structure after testing of each unit. After the incorporate stage, the whole system is inspected and tested for any bugs and errors.

• System Deployment − After the testing is done for functional and non-functional; the product is utilized in the client domain or dissimenate into the demand.

• Maintenance − There are some matter which arise in the customer domain. To resolve those problems, patches are dissemenate. Also to increase the outcome, some upgraded variation are revealed. Conservation is done to dissimenate these replacement in the client domain.

What are the waterfall model’s advantages?

Waterfall Model Development allows for Departmentalization and control as it's advantages. Stage of development can set a schedule with deadlines and the product can progress through the growth procedure model stages accordingly.

Evolution moves from idea, through sketch, implementation, testing, installation, troubleshooting, and ends up at functioning and preservation. Each stages of development proceeds accordingly.

Major advantages of the Waterfall Model are as follows −

• Easy to utulize and very well understood.

• Easy to supervise due to the model being irreversible. Each stage has particular pre-requisite and a rechecking process.

• Stages are procedure and finished individually.

• Doing well for minor projects where pre-requisite are very well understandable.

• Distinctly equivalent stages.

• Understandable achievements.

• It is effortless to organized tasks.

• Procedure and Outcome are well written or documented.

What are the waterfall model’s disadvantages?

Demonstration or alteration does isn't allowed much is mainly the disadvantage of waterfall development. Under any circumstances of an implementation in the testing phase, it is very inconvenient to go back and revise something that was not well written or documented or thought upon in the idea stage

The Waterfall Moder have some major disadvatages like−

• No working software is manufactured throughout behind schedule during the life cycle.

• High quantity of uncertainty and risks.

• Not a sturdy model for compound and object-oriented projects.

• Sub-standard model for long interval and proceeding projects.

• Pre-requisite are at an average to high risk of change are unsuitable for the projects, uncertainty and instability are high with this development model

• It is troublesome to calculate development within stages.

• Cannot lodge sufficient changing pre-requisite.

• Balancing scope throughout the life cycle can terminate a project.

• Integration or composite is done as a "bigbang which does not authorize in determining any technological or business or hindrances early

Who uses the waterfall model?

The people who commonly utilize the waterfall model are software development contractors as system software cannot be implemented without finishing every single specified task chronologically.

Where is the waterfall model commonly used?

The waterfall model is frequently used in construction industries, manufacturing industries and software development companies. The models are used in highly builded physical environments in which changes after the implementation are very expensive, if it is not difficult to deal with. Since it was first used in physical processes, one after another when software was not abundant, the waterfall model was only later modified for software development.

How are ideas presented in a waterfall model?

Since the waterfall model is very straightforward and understandable and it follows a step-by-step procedure, ideas are presented in a specific manner. The users of the model focus on only merely idea at a time and follow the waterfall model’s phases and will carry on to the next set of ideas for specified phases. As said in the other component of the research, the users of this model cannot proceed unless the stage in focus is finished.

Why is the waterfall model important?

The waterfall model is crucial because it can easily help the users and developers to understand the sequential procedure in development. Since it shows the processes in a cascaded format, each process is easily recognized by anyone who looks at its diagram.

When is the waterfall model used and when was it introduced?

Dr. Winston W. Royce introduced the waterfall model in a paper which was published in 1970. Every Developed software is unique and involves an appropriate System Development Life Cycle (SDLC) move toward in judging from two factors which are internal factors and external factors. The use of waterfall model is most appropriate at some situations because of-

• The Pre-requisite are well written or documented, simple and steady.

• The definition of products is steady of fixed.

• Technology is understandable and is not dynamic.

• There are certainly no vague or obscure requirements.

• There are sufficient assets with an indemand proficiency available to reinforce the product

• The project is relatively small in extent.

Minimal purchase communication is comprehend throughout the product development. When the product is all set, it can be demonstrate to the end users. And once the product is starting to expand and implement and if any errors arises then the value of fixing such problems are high and there would be a need to improve everything from the beginning of the document to the system's logic.

By  : Trisha Jade Cruz 
        Raven Alejandrino