問38
頻出度★★★
要求事項が明確であり仕様変更が少ないことが見込まれるソフトウェアの開発に用いる開発モデル・手法として，最も適切なものはどれか。
令和8年度 ITパスポート試験 問38
マネジメント系ソフトウェア開発管理技術 › 開発プロセス・手法
This question's explanation and your answers so far.
解説
問 38
Incorrectア
Agile development repeats short iterations to build working software bit by bit, incorporating additions and changes to the specification each time. It suits development where specification changes occur frequently or where the requirements are hard to fix at first. Under this question’s premise of clear requirements and few changes, the benefit of its flexibility is not put to use, so it is not the most appropriate.
- イ
正解 The correct answer is “イ Waterfall model.” The waterfall model is a development method that advances the phases of requirements definition → design → implementation → testing in one direction from upstream to downstream, and in principle it does not go back to an earlier phase. Because it moves to the next phase only after each phase is complete, it presupposes that the requirements can be fixed at the very first stage. For software like the one in this question, where “the requirements are clear and few specification changes are expected,” almost no backtracking or rework occurs, so the waterfall model, which lets the phases proceed in a planned way, is the most appropriate.
Incorrectウ
The spiral model divides the development target into parts and repeats the cycle of “design → prototype → evaluation” in a spiral, raising the level of completion step by step while checking risks. It suits development with large risk or uncertainty, but when the requirements are clear and changes are few, the effort of this repetition becomes excessive, so it is not the most appropriate.
Incorrectエ
The prototyping model builds a prototype at an early stage for users to confirm, fixing the specification while resolving ambiguity in the requirements. It is effective when the requirements are unclear, but in this question the requirements are already clear, so there is little need to verify the requirements with a prototype, and it is not the most appropriate.
ここがポイント
- The waterfall model advances phases in order from upstream to downstream without going back, and it suits development where the requirements are clear and specification changes are few.
- Agile, spiral, and prototyping are iterative or prototype-based methods that are good at coping with specification changes and ambiguous requirements, and they are chosen according to the preconditions.
用語