Question

Which software process model is most appropriate for projects with poorly defined requirements that are expected to evolve significantly over time?

• A. Waterfall Model
• B. Iterative Prototyping
• C. V-Model
• D. Incremental Model

Hint:

Prototyping is the best choice when the customer is unsure of exactly what they want. It bridges the communication gap between the user and the developer.

Answer 1

The Correct Option is B

Concept:
Different software projects require different process models based on the clarity of requirements and the level of risk. When requirements are "fuzzy" or unknown at the start, a linear model will likely fail because it assumes a perfect understanding of the system from day one.

Step 1: The Logic of Prototyping.
The Prototyping model involves building a "mock-up" or a simplified version of the software early in the lifecycle. This allows users to interact with a visual representation of the system. Their feedback is then used to refine the actual requirements.

Step 2: Handling Requirement Evolution.
In an "Iterative" prototyping approach:
• The prototype is built, tested, and evaluated by the user.
• Changes are made based on feedback.
• The process repeats until the requirements are clearly understood. This "evolutionary" approach is specifically designed to handle uncertainty and changing user expectations.

Step 3: Comparison with others.
The Waterfall Model requires all requirements to be frozen at the start. The V-Model is similar but focuses on testing. Neither handles requirement "evolution" well. Prototyping reduces the risk of building the "wrong system."