Prototyping is a technique used to create a working model of a system or product to validate

requirements and gather feedback. Let’s evaluate each statement to determine which are false :

Evaluation of Each Statement:

A . Suitable for waterfall requirements elicitation:

Prototyping is generally not suitable for traditional waterfall methodologies because waterfall

follows a linear, sequential approach where requirements are defined upfront before development

begins. Prototyping, on the other hand, involves iterative feedback loops, which are more aligned

with Agile methodologies.

Conclusion: This statement is false .

B . Allows an analyst to confirm their understanding of requirements:

Prototyping enables analysts to validate their understanding of requirements by creating a tangible

representation of the system for stakeholders to review and provide feedback.

Conclusion: This statement is true .

C . Only suitable for Agile project environments:

While prototyping is commonly used in Agile environments due to its iterative nature, it is not

limited to Agile. Prototyping can also be used in hybrid or iterative waterfall projects to clarify

requirements and reduce ambiguity.

Conclusion: This statement is false .

D . Enables the elicitation of usability requirements:

Prototyping is particularly effective for gathering usability requirements because it allows

stakeholders to interact with a mock-up or early version of the system, providing insights into user

experience and interface design.

Conclusion: This statement is true .