問33
頻出度★★☆
次の記述のうち, 業務要件定義が曖昧なことが原因で起こり得る問題だけを全て挙げたものはどれか。 a 企画プロセスでシステム化構想がまとまらず, システム化の承認を得られない。 b コーディングのミスによって, システムが意図したものと違う動作をする。 c システムの開発中に仕様変更による手戻りが頻発する。 d システムを受け入れるための適切な受入れテストを設計できない。
令和6年度 ITパスポート試験 問33
ストラテジ系システム企画 › 要件定義
This question's explanation and your answers so far.
解説
問 33
Incorrectア
The combination of a and b. a is a problem where the systemization concept cannot be finalized in the planning process, but planning is a process that comes before business requirements definition and is not caused by ambiguous requirements definition. b is a defect at the implementation stage, namely a coding mistake, unrelated to requirements. Since neither applies, it is wrong.
Incorrectイ
The combination of b and c. c is correct because it is caused by ambiguous requirements, but b is a malfunction due to a coding mistake, a problem of the programming process rather than requirements definition. Because it includes b, which does not apply, it is wrong.
Incorrectウ
The combination of b and d. d is correct because it is caused by ambiguous requirements, but b is a defect in implementation, namely a coding mistake, unrelated to requirements definition. Because it includes b, which does not apply, it is wrong.
- エ
正解 The correct answer is エ (c, d). Business requirements definition is the process in which the business side clearly defines what business operations and functions they want the new system to realize; it is the foundation for all subsequent design, development, and testing. c is a typical case: when requirements are ambiguous the specifications cannot be fixed, and during development many specification changes such as “actually, please do it this way” arise later, causing frequent rework, so it qualifies as such a problem. d, the acceptance test, is work in which the business side verifies whether the system was built as required, so if the requirements themselves are ambiguous, the criteria for judging pass or fail cannot be set and an appropriate test cannot be designed. Therefore the problems directly caused by ambiguous business requirements definition are only c and d, and エ, which lists both without excess or omission, is correct.
ここがポイント
- Business requirements definition is the process of clarifying the functions and business operations the business side needs; if the requirements are ambiguous, it leads to downstream rework caused by specification changes.
- The acceptance test is verification against the requirements, so if the requirements are ambiguous the pass/fail criteria cannot be defined and the test design breaks down. Problems such as the planning process or coding mistakes belong to other processes and should be distinguished.
用語