Waterfall model in Software Engineering - Step-by-Step Execution

Concept Flow - Waterfall model

Requirements

↓

Design

↓

Implementation

↓

Testing

↓

Deployment

↓

Maintenance

↓

END

The Waterfall model follows a step-by-step flow from Requirements to Maintenance, completing each phase fully before moving to the next.

Execution Sample

Software Engineering

Phase 1: Gather requirements
Phase 2: Design system
Phase 3: Write code
Phase 4: Test system
Phase 5: Deploy
Phase 6: Maintain

This sequence shows the Waterfall model phases executed one after another without overlap.

Analysis Table

Step	Phase	Action	Output	Next Phase
1	Requirements	Collect all user needs	Clear requirements document	Design
2	Design	Plan system architecture	Design specifications	Implementation
3	Implementation	Write and build code	Working software modules	Testing
4	Testing	Check for bugs and errors	Test reports and fixes	Deployment
5	Deployment	Release software to users	Software in production	Maintenance
6	Maintenance	Fix issues and update	Updated software	END

💡 All phases completed sequentially; no phase starts before previous finishes.

State Tracker

Phase	Status Start	After Completion
Requirements	Not started	Completed
Design	Not started	Completed
Implementation	Not started	Completed
Testing	Not started	Completed
Deployment	Not started	Completed
Maintenance	Not started	Ongoing or Completed

Key Insights - 3 Insights

Why can't we go back to a previous phase once it's done?

In the Waterfall model, each phase must finish completely before the next starts, so going back is not part of the process (see execution_table rows 1-6).

What happens if a problem is found during Testing?

Testing phase fixes issues before Deployment, but major changes require revisiting Implementation or Design, which is difficult in Waterfall (see execution_table row 4).

Is Maintenance part of the development or after release?

Maintenance happens after Deployment to fix bugs or update software while it is in use (see execution_table rows 5-6).

Visual Quiz - 3 Questions

Look at the execution_table, what is the output after the Design phase?

A Test reports and fixes

B Working software modules

C Design specifications

D Clear requirements document

💡 Hint

Check the Output column in row 2 of the execution_table.

At which step does the software get released to users?

A Step 3

B Step 5

C Step 4

D Step 6

💡 Hint

Look at the Phase and Action columns in the execution_table for deployment.

If a bug is found during Testing, which phase is responsible for fixing it before release?

A Testing

B Requirements

C Deployment

D Implementation

💡 Hint

Refer to the Action and Output in the Testing phase in the execution_table.

Concept Snapshot

Waterfall model is a linear software development process.
Phases: Requirements -> Design -> Implementation -> Testing -> Deployment -> Maintenance.
Each phase must finish before the next starts.
Changes are hard to make once a phase is complete.
Best for projects with clear, fixed requirements.

Full Transcript

The Waterfall model is a step-by-step approach to software development. It starts with gathering all requirements, then designing the system, followed by coding, testing, deploying, and finally maintaining the software. Each phase must be fully completed before moving on to the next. This model does not allow going back easily to previous phases. Testing finds bugs which are fixed before deployment. Maintenance happens after release to keep the software updated. This model works well when requirements are clear and unlikely to change.

Practice

1. Which of the following best describes the Waterfall model in software engineering?

easy

A. An iterative approach with frequent feedback and overlapping phases.

B. A linear and sequential approach where each phase must be completed before the next begins.

C. A model that focuses on rapid prototyping and user involvement throughout.

D. A flexible model that allows phases to be skipped or repeated in any order.

Solution

1. Step 1: Understand the Waterfall model structure

   The Waterfall model is known for its strict, linear sequence of phases where each phase must be finished before the next starts.

2. Step 2: Compare options with the model's characteristics

   A linear and sequential approach where each phase must be completed before the next begins. matches this description exactly, while others describe different models like iterative or prototyping.

3. Final Answer:

   A linear and sequential approach where each phase must be completed before the next begins. -> Option B

4. Quick Check:

   Waterfall = Linear & Sequential [OK]

Hint: Waterfall means one step at a time, no going back [OK]

Common Mistakes:

• Confusing Waterfall with iterative or agile models
• Thinking phases can overlap or repeat
• Believing Waterfall allows skipping phases

2. Which phase comes immediately after the 'Design' phase in the Waterfall model?

easy

A. Implementation

B. Testing

C. Requirement Analysis

D. Maintenance

Solution

1. Step 1: Recall the Waterfall phase order

   The typical order is Requirement Analysis, Design, Implementation, Testing, then Maintenance.

2. Step 2: Identify the phase after Design

   After Design, the next phase is Implementation where the actual coding happens.

3. Final Answer:

   Implementation -> Option A

4. Quick Check:

   Design -> Implementation [OK]

Hint: Design is followed by coding (Implementation) [OK]

Common Mistakes:

• Choosing Testing instead of Implementation
• Mixing up Maintenance as next phase
• Confusing Requirement Analysis as next phase

3. Consider this sequence of Waterfall phases completed in order: Requirement Analysis, Design, Implementation, Testing, Maintenance. What is the main risk if a requirement was misunderstood in the first phase?

medium

A. The error will be caught early during Implementation.

B. The error will be fixed easily during Maintenance without impact.

C. The project will need to restart from Requirement Analysis after Testing.

D. The error will not affect later phases since they are independent.

Solution

1. Step 1: Understand Waterfall's linear flow and error impact

   Since each phase depends on the previous, an error in requirements affects all later phases.

2. Step 2: Analyze consequences of misunderstood requirements

   Errors found late (like during Testing) require going back to Requirement Analysis, causing delays and restarts.

3. Final Answer:

   The project will need to restart from Requirement Analysis after Testing. -> Option C

4. Quick Check:

   Misunderstood requirements cause restart after Testing [OK]

Hint: Errors in early phases cause costly restarts later [OK]

Common Mistakes:

• Assuming errors are caught early in Implementation
• Thinking Maintenance fixes all errors easily
• Believing phases are independent and errors don't propagate

4. A team following the Waterfall model started Testing before completing Implementation. What is the main problem with this approach?

medium

A. Testing before Implementation breaks the Waterfall sequence and may cause incomplete tests.

B. Testing early improves quality and is recommended in Waterfall.

C. Implementation and Testing can happen simultaneously in Waterfall.

D. Skipping Design phase is acceptable if Testing starts early.

Solution

1. Step 1: Recall Waterfall phase order and rules

   Waterfall requires completing one phase fully before starting the next.

2. Step 2: Identify issue with starting Testing before Implementation

   Testing before Implementation means testing incomplete or missing code, violating the model's sequence.

3. Final Answer:

   Testing before Implementation breaks the Waterfall sequence and may cause incomplete tests. -> Option A

4. Quick Check:

   Waterfall = phases done fully in order [OK]

Hint: Waterfall phases must finish fully before next starts [OK]

Common Mistakes:

• Thinking Testing can start early in Waterfall
• Believing Implementation and Testing overlap
• Assuming Design phase can be skipped

5. A project has very clear, fixed requirements and a strict deadline. Why is the Waterfall model often preferred for such projects?

hard

A. Because it skips testing to save time and meet deadlines.

B. Because it allows flexible changes during development to meet deadlines.

C. Because it encourages continuous user feedback and iterative improvements.

D. Because its linear phases help plan and track progress clearly with fixed requirements.

Solution

1. Step 1: Understand Waterfall suitability for fixed requirements

   Waterfall works best when requirements are clear and unlikely to change, allowing straightforward planning.

2. Step 2: Analyze why linear phases help with deadlines

   Its sequential approach makes progress easy to track and manage, fitting strict deadlines well.

3. Final Answer:

   Because its linear phases help plan and track progress clearly with fixed requirements. -> Option D

4. Quick Check:

   Fixed requirements + strict deadlines = Waterfall preferred [OK]

Hint: Waterfall suits fixed needs and clear progress tracking [OK]

Common Mistakes:

• Thinking Waterfall allows flexible changes easily
• Confusing Waterfall with iterative feedback models
• Believing Waterfall skips testing to save time