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

What are compatibility tests and how are they performed?

-
  Compatibility Testing: Compatibility testing is a non-functional testing that assesses how well a software application performs across different environments, devices, browsers, and operating systems. The primary objective is to ensure that the software operates correctly and consistently on multiple platforms and configurations that users may use. What is backwards and forwards compatibility testing Backward compatibility testing verifies that a new version works with older ones, while forward compatibility testing verifies that an older version works with newer ones. That means you might ensure that a new OS update will work great with your software via forward compatibility testing; and ensure that users still on older operating systems continue having a great experience in you new update in backwards compatibility testing. Key Aspects of Compatibility Testing: Cross-Browser Testing: Ensures the software works seamlessly across different web browsers such as Chrome, Firefox, Safa
Read more

What Is a Use Case, Purpose of Use Case and How to Write Use Case?

-
  Use Case Use cases serve as a powerful way to outline and understand how users interact with a system or product. They're like detailed stories that capture various scenarios, including: Success scenarios: These describe the expected and desired interactions between the user and the system. They outline how the system should ideally behave when everything goes right. Failure scenarios: These highlight potential issues or errors that might occur during interaction. They cover what happens when things don’t go as planned and help prepare for handling such situations. Critical variations or exceptions: These are deviations from the standard paths outlined in the success scenarios. They often involve edge cases or unique scenarios that need special attention. Use cases are valuable not just for developers but also for quality assurance teams. They help ensure that the software is tested comprehensively, covering both regular and edge-case scenarios. Purpose of  Use Case The purpos
Read more

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