IPA IP 2024 Question 33
A question IPA Japan published in 令和6年度 ITパスポート試験 公開問題 問33, translated into English. ITPEC is based on the same exams.
Among the descriptions below, which of the following lists all and only the problems that can occur because the business requirements definition is ambiguous?
Explanation
C, D — an ambiguous business requirements definition shows up later, as rework from specification changes and as acceptance tests that cannot be designed.
Business requirements definition comes after planning: it fixes what the business needs from the system, and everything after it is built and checked against it.
- •A: the computerization concept and its approval belong to the planning process, which is finished before requirements are defined, so an ambiguous requirements definition cannot cause it
- •B: a coding error is a mistake in implementing a design; the program misbehaves even when the requirements are clear
- •C: requirements left vague get settled during development, so specifications change and work done already is redone
- •D: acceptance testing checks that the system meets the agreed requirements; vague requirements give no clear criteria to test against
Answer (d)
Why not others:
- •(a) A, B — both problems arise elsewhere: A in planning, before requirements exist, and B in coding
- •(b) B, C — includes the coding error B and leaves out D
- •(c) B, D — includes the coding error B and leaves out the rework C
Key rule: Requirements are the baseline for design and for acceptance; when they are vague, the cost appears as rework and untestable acceptance criteria.
System Planning · AI-written, may contain errors
This question comes from the past questions IPA Japan publishes, translated into English by ITPEC Practice. ITPEC Practice is an independent study tool and is not affiliated with IPA or ITPEC. See the original paper (PDF) or Report an issue.