Curso de QA da He4rt Developers

# Waterfall Model

It is a sequential framework that divides software development into predefined phases. Each one must be completed before the next one can begin, with no overlap between phases.

Each stage is structured to carry out a specific activity during the SDLC phase.

Waterfall Flowchart

# Stages of the Waterfall Model

  • Business Requirement Gathering Phase: Gathering as much information as possible about the details and specifications of the software desired by the client.

  • Design Phase: Planning the programming language to be used, the database, etc. It should fit the project, as well as high-level functions and architecture.

  • Construction Phase: After the Design, we proceed to actually build the software code.

  • Testing Phase: Afterward, we test the software to verify that it has been created according to the specifications provided by the client.

  • Implementation Phase: It implements the application in the designated environment.

  • Maintenance Phase: Once the system is ready for use, it may be necessary to change the code later depending on user requests.

# When to Use the Waterfall Model?

It can be applied when:

  • Requirements do not change constantly;
  • The application is not overly complex;
  • The project is short;
  • Business rules are clear;
  • The environment is stable;
  • Technology and tools used are not dynamic but stable;
  • Resources are available and directed;

# Advantages of the Waterfall Model

  1. Before the next development phase, the previous one must be completed.
  2. Suitable for smaller projects with well-defined requirements.
  3. Quality Assurance (verification and validation) tests should be applied before completing each stage.
  4. Documentation development is done at each stage of the SDLC.
  5. The project is entirely dependent on the team, with minimal customer involvement.
  6. Any changes to the software are made during the development process.

# Disadvantages of the Waterfall Model

  1. Errors can only be fixed in the next stage.
  2. Not suitable for complex projects where requirements change constantly.
  3. The testing period only occurs in the later stages of the development process.
  4. Documentation takes up a significant amount of developers' and testers' time.
  5. Valuable customer feedback cannot be included in the ongoing development process.
  6. Small changes or errors that arise in the finished software can lead to major problems.

← V-Model →