volume_mute

Choosing a Development Model in the Spiral

publish date: 2026/05/31 04:48:58.393230 UTC

volume_mute

In the spiral model's development and validation sector, how is the development model chosen?

It is chosen by the customer at the start of the project and cannot be changed

It is always the waterfall model regardless of the risks identified

It is chosen based on the dominant risk — for example, throwaway prototyping for UI risks, formal transformations for safety risks, or waterfall for sub-system integration risks

It is always an agile method because the spiral model is an agile framework

Correct Answer

It is chosen based on the dominant risk — for example, throwaway prototyping for UI risks, formal transformations for safety risks, or waterfall for sub-system integration risks

Explanation

In the development and validation sector, after risk evaluation, a development model for the system is chosen based on the dominant risk. If user interface risks are dominant, throwaway prototyping may be best. If safety risks are main, formal transformations may be most appropriate. If sub-system integration is the main risk, the waterfall model may be best.

Reference

Software Engineering, Ian Sommerville, 9th edition

Quizzes you can take where this question appears

Boehm's Spiral Model