Understanding Requirements in Waterfall

What is the primary goal of the requirements analysis phase in the Waterfall methodology?

• To develop the software

• To understand and document the needs of the stakeholders

• To test the software

• To deploy the software

In the Waterfall methodology, which phase follows the requirements analysis and gathering phase?

• Design

• Implementation

• Testing

• Maintenance

Which of the following is a key characteristic of the Waterfall methodology?

• Iterative development

• Parallel processing

• Sequential phases

• Agile sprints

What is a common tool used during the requirements gathering phase?

• Gantt chart

• Interview

• Compiler

• Debugger

Which document is typically produced at the end of the requirements analysis phase?

• Source code

• Test plan

• Requirements specification

• User manual

Why is it important to have clear requirements in the Waterfall methodology?

• To reduce the cost of hardware

• To ensure the project can skip the testing phase

• To minimise changes during later stages

• To allow for flexible project timelines

Which of the following is NOT a technique used in requirements gathering?

• Brainstorming

• Prototyping

• Coding

• Surveys

What is the role of a stakeholder in the requirements analysis phase?

• To write code

• To provide input and feedback on requirements

• To test the software

• To design the user interface

In the Waterfall model, changes to requirements are:

• Easily accommodated at any stage

• Discouraged after the requirements phase

• Encouraged throughout the project

• Only allowed during the testing phase

Which of the following best describes the Waterfall methodology?

• Flexible and adaptive

• Rigid and structured

• Collaborative and iterative

• Fast and unplanned