What are the drawbacks of the Waterfall methodology?

-

WHAT IS THE WATERFALL MODEL?

Software industry used the Waterfall model as the first approach to software development. Winston Royce introduced this model back in 1970. This is a traditional method in software development. Waterfall model is a “linear-sequential life-cycle model. The word waterfall indicates that this model is linear and flow like a waterfall from high to low level. It has five to seven stages which have different tasks to perform. Whereby, all the stages collectively describe the whole life cycle. The model runs sequence-wise, in which one stage follows the next stage and the cycle continues.

There is no overlapping or turning back of the phases. The output of each phase functions as the input of the next phase. Small software development projects use the waterfall model. These projects are easy to handle and do not have unclear requirements.

PHASES OF THE WATERFALL MODEL:

To understand the Waterfall model thoroughly, one must have to know the details of its phases. All the phases work precisely and are independent of each other. The seven successive phases of the Waterfall model are:

  • System Requirements

  • Software Requirements

  • Requirements Analysis

  • Program Design

  • Implementation or Deployment

  • Testing

  • Launch

Advantages and Disadvantages of Waterfall Model:

Here are the popular advantages of Waterfall model in Software Engineering with some disadvantages:

Advantages

Dis-Advantages

Before the next phase of development, each phase must be completed

Error can be fixed only during the phase

Suited for smaller projects where requirements are well defined

It is not desirable for complex project where requirement changes frequently

They should perform quality assurance test (Verification and Validation) before completing each stage

Testing period comes quite late in the developmental process

Elaborate documentation is done at every phase of the software’s development cycle

Documentation occupies a lot of time of developers and testers

Project is completely dependent on project team with minimum client intervention

Clients valuable feedback cannot be included with ongoing development phase

Any changes in software is made during the process of the development

Small changes or errors that arise in the completed software may cause a lot of problems


 

Comments

Post a Comment

Popular posts from this blog

How to log a bug with a detailed description ?

-
What is a Bug? A bug is an unexpected problem with software or hardware. Typical problems are often the result of external interference with the program's performance that was not anticipated by the developer. Minor bugs can cause small problems like frozen screens or unexplained error messages that do not significantly affect usage. How to log a Bug? Logging a bug involves documenting and reporting a software issue or unexpected behavior encountered during testing or product usage. Here's a step-by-step guide on how to log a bug effectively: 1. Identify the Bug: Reproduce the Bug: Ensure you can replicate the issue consistently. Understand the Context: Note the environment, device, browser, or any specific conditions required to reproduce the bug. 2. Choose a Bug Tracking Tool: Select a Bug Tracking System: Use tools like Jira, Bugzilla, GitHub Issues, or any other bug tracking software your team uses. Access the Tool: Open the bug track...
Read more

How to push changes to Git Hub using the command line?

-
Image
Go to the web page for your GitHub repository, and note the URL.  Open  Bash  on Windows. (If you're using Linux or Mac, open  Terminal .)  Use the  cd  command to switch to the directory you want to use to work on your project locally. Enter  git clone [URL of your repository]  to copy your repository to your local machine. Use the  cd  command to go into your repository directory. You'll know you're in the right place if your new command line ends with the name of the main branch of your repository. For example, the name of my main branch is "main," so  (main)  appears at the end of my command line. Once you've added your files to your directory and are ready to push to GitHub, in your  Bash  window, enter  git add .  to select all the files in your repository.  Enter  git commit -m "[commit message]"  to save the changes to your local repository. You can enter anything for the commit m...
Read more

How to log a defect with a detailed description?

-
What is Defect? The defect is an error occurring in software that is under development, which makes it impossible to complete the intended action. Defects are usually results of programmers’ slips, and they can appear at any stage of the software development process. How to log Defect? Logging a defect with a detailed description is crucial for effective communication between testers and developers. Here's a step-by-step guide on how to log a defect: 1. Identify the Defect: Reproduce the Issue: Make sure you can replicate the problem consistently. Understand the Context: Note the environment, device, browser, or any specific conditions required to reproduce the defect. 2. Choose a Defect Tracking Tool: Use a Defect Tracking System: Tools like Jira, Bugzilla, or Trello are commonly used for defect tracking. Open the System: Access the system and create a new defect report. 3. Provide Defect Details: Title/Summary: Write a concise yet descriptive title summarizing the issue. Des...
Read more