The Waterfall Model

Core idea of the waterfall model

1 pts

volume_mute

The waterfall model is one of the earliest and most influential software process models. It structures development into a sequence of distinct phases, each producing documents or artifacts that feed into the next.

Which statement best describes the core idea of the waterfall model?

The system is delivered as a single increment without any prior specification.

Development is organized into sequential phases with limited overlap.

Software is always developed by reusing existing components only.

All phases are performed in parallel with no ordering.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Phases of the waterfall model

1 pts

volume_mute

The waterfall model defines a set of major phases that reflect the fundamental development activities.

Which set of phases best matches the waterfall model?

Component analysis; requirements modification; system design with reuse; development and integration

Planning; coding; refactoring; decommissioning

Feasibility study; prototyping; deployment; retirement

Requirements analysis and definition; system and software design; implementation and unit testing; integration and system testing; operation and maintenance

note_alt Add notes

flag Flag

Correct Answer

Explanation

Plan-driven nature of the waterfall model

1 pts

volume_mute

The waterfall model is often described as a plan-driven process.

What does it mean for the waterfall model to be plan-driven?

All process activities are planned and scheduled before development begins.

Only testing activities are planned in advance.

Planning is avoided to keep the process flexible.

Plans are created incrementally after each phase is completed.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Diagram: basic waterfall flow

1 pts

volume_mute

The following diagram illustrates the classic waterfall flow of phases.

What does this diagram emphasize about the waterfall model?

Phases are arranged in a largely sequential, stepwise fashion.

All phases are repeated continuously in a tight loop.

Phases are executed randomly with no order.

Only testing and maintenance are important in the process.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Documents and visibility

1 pts

volume_mute

In the waterfall model, each phase typically produces one or more documents that are reviewed and approved.

Which is a key advantage of this documentation-heavy approach?

The process becomes visible and managers can monitor progress against the plan.

It removes the need for communication with customers.

It guarantees that no changes will be required later.

It eliminates the need for any testing activities.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Freezing requirements

1 pts

volume_mute

In practice, iterations in the waterfall model are costly because of the need to revise documents and approvals.

What is a common consequence of this cost?

Requirements are prematurely frozen, even if not fully understood.

Design is always postponed until after implementation.

No documentation is produced to save time.

Requirements are continuously changed without control.

note_alt Add notes

flag Flag

Correct Answer

Explanation

When to use the waterfall model

1 pts

volume_mute

The waterfall model is not suitable for all types of systems.

In which situation is the waterfall model most appropriate?

When requirements are highly volatile and poorly understood.

When requirements are well understood and unlikely to change significantly.

When the system must be delivered in many small increments with frequent changes.

When no documentation is required by stakeholders.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Limitations of the waterfall model

1 pts

volume_mute

Despite its historical importance, the waterfall model has well-known limitations.

Which of the following is a major limitation?

It is difficult to respond to changing customer requirements once the process is underway.

It completely eliminates the need for testing.

It does not allow any documentation to be produced.

It cannot be used for any safety-critical systems.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Formal system development as a variant

1 pts

volume_mute

An important variant of the waterfall model is formal system development, where mathematical models and transformations are used.

Which statement best characterizes formal system development?

Only user interface prototypes are developed formally.

Testing is the only activity that uses formal methods.

Code is written first and requirements are inferred later.

A mathematical specification is refined through correctness-preserving transformations into executable code.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Use of formal methods

1 pts

volume_mute

Formal development processes are not used for all systems.

For which type of system are formal development processes particularly suited?

Systems with stringent safety, reliability, or security requirements.

Simple brochure-style web pages.

Games developed for entertainment only.

Small throwaway scripts with no long-term use.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Classification of activities

1 pts

The waterfall model’s phases can be mapped to the four fundamental process activities: specification, development, validation, and evolution.

Classify each waterfall phase into the most closely related fundamental activity.

To complete the line match

Click on an item in the first group
Click on the match in the second group

To delete a match, double click on a line

Waterfall Phase

Implementation and unit testing

Integration and system testing

Operation and maintenance

Requirements analysis and definition

Fundamental Activity

Specification

Development

Validation

Evolution

note_alt Add notes

flag Flag

Correct Answer

Explanation

Match: waterfall phase to description

1 pts

Match each waterfall phase to its primary description.

To complete the line match

Click on an item in the first group
Click on the match in the second group

To delete a match, double click on a line

Phase

System and software design

Implementation and unit testing

Integration and system testing

Requirements analysis and definition

Description

Allocates requirements to hardware and software and defines overall architecture

Establishes services, constraints, and goals through consultation with users

Realizes the design as program units and verifies each unit

Combines program units and checks that requirements have been met

note_alt Add notes

flag Flag

Correct Answer

Explanation

Waterfall vs. incremental visibility

1 pts

volume_mute

Managers often care about process visibility—how easily they can see progress.

How does the waterfall model compare to incremental development in terms of visibility?

Waterfall has no visibility because it produces no intermediate artifacts.

Incremental development always has higher visibility because it produces no documents.

Both have identical visibility characteristics.

Waterfall has high visibility due to documents at each phase; incremental may have lower visibility if documentation is minimized.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Waterfall and feedback

1 pts

volume_mute

Although the waterfall model is often drawn as a simple cascade, real projects involve feedback between phases.

Which statement best reflects this reality?

In practice, phases overlap and information flows back to earlier phases when problems are discovered.

Feedback is only allowed from maintenance back to requirements.

Phases never overlap and no feedback is allowed.

Feedback is only allowed if the customer pays extra.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Waterfall and maintenance

1 pts

volume_mute

Operation and maintenance is often the longest phase in the waterfall life cycle.

Which of the following activities is not typically part of maintenance?

Enhancing the system’s services as new requirements are discovered

Developing a completely unrelated system for another customer

Correcting errors not discovered earlier

Improving the implementation of system units

note_alt Add notes

flag Flag

Correct Answer

Explanation

Waterfall and risk of misfit

1 pts

volume_mute

Because requirements are fixed early in the waterfall model, there is a risk that the delivered system does not match user needs.

Which factor most contributes to this risk?

Documentation is always incorrect by definition.

Testing is performed too frequently.

Programming languages are too expressive.

Users may not fully understand their needs at the start of the project.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Waterfall and large projects

1 pts

volume_mute

Large engineering projects often use management models similar to the waterfall model.

Why is the waterfall model still commonly used in such contexts?

It completely eliminates project risk.

It guarantees that no changes will ever be requested.

It requires no coordination between teams.

It aligns with other engineering disciplines that also use phase-based, plan-driven processes.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Classification: advantages vs disadvantages

1 pts

Classify each statement as an advantage or disadvantage of the waterfall model.

drag and drop the selected option to the right place

note_alt Add notes

flag Flag

Correct Answer

Explanation

Diagram: waterfall with feedback

1 pts

volume_mute

The following diagram shows a more realistic waterfall with feedback loops.

What do the curved arrows in this diagram represent?

Random jumps between phases with no rationale.

Feedback from later phases to earlier phases when problems are discovered.

User navigation paths in a user interface.

Data flow between unrelated systems.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Waterfall model: phase dependencies

1 pts

volume_mute

The waterfall model assumes that each phase depends on the outputs of the previous phase. This creates a structured flow of information and artifacts.

The diagram below illustrates this dependency chain using labeled connectors.

What does this diagram illustrate about the waterfall model?

Implementation always begins before design is completed.

Phases are executed in any order depending on developer preference.

Each phase relies on the completed outputs of the previous phase before it can begin.

Requirements are optional and can be skipped if the team is experienced.

note_alt Add notes

flag Flag

Core idea of the waterfall model

Correct Answer

Explanation

Phases of the waterfall model

Correct Answer

Explanation

Plan-driven nature of the waterfall model

Correct Answer

Explanation

Diagram: basic waterfall flow

Correct Answer

Explanation

Documents and visibility

Correct Answer

Explanation

Freezing requirements

Correct Answer

Explanation

When to use the waterfall model

Correct Answer

Explanation

Limitations of the waterfall model

Correct Answer

Explanation

Formal system development as a variant

Correct Answer

Explanation

Use of formal methods

Correct Answer

Explanation

Classification of activities

Waterfall Phase

Fundamental Activity

Correct Answer

Explanation

Match: waterfall phase to description

Phase

Description

Correct Answer

Explanation

Waterfall vs. incremental visibility

Correct Answer

Explanation

Waterfall and feedback

Correct Answer

Explanation

Waterfall and maintenance

Correct Answer

Explanation

Waterfall and risk of misfit

Correct Answer

Explanation

Waterfall and large projects

Correct Answer

Explanation

Classification: advantages vs disadvantages

drag and drop the selected option to the right place

Correct Answer

Explanation

Diagram: waterfall with feedback

Correct Answer

Explanation

Waterfall model: phase dependencies

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: