システムの利用者と開発者の間で, システムの設計書の記載内容が利用者の要求を満たしていることを確認するために実施するものはどれか。
平成31年度 春期 ITパスポート試験 問51
This question's explanation and your answers so far.
問 51
- ア
正解 The correct answer is 'ア Joint review'. A joint review is an activity in which the user side and the developer side of a system gather together to jointly verify and confirm the contents of a deliverable (such as a design document). As in this question, it is the most suitable means for cross-checking, from both the user's and the developer's viewpoints, whether the contents described in the design document satisfy the users' requirements. Rather than confirming things by running something that actually works, as in testing, its characteristic is that it reviews a document (the design document) so that gaps in understanding or gaps against the requirements can be found early. This matches the question's conditions of 'between the user and the developer' and 'confirming that the design document's contents satisfy the requirements'.
Incorrectイ
Integration testing is a process in which developers combine multiple modules (programs) that have already passed unit testing and verify whether the interfaces and cooperation between the modules operate correctly. It targets programs that actually run, and is not an activity of confirming together with users whether the document called the design document satisfies the users' requirements, so it is incorrect.
Incorrectウ
Simulation is a method that models (imitates) the target system or a part of it in order to predict and evaluate its behavior or performance. It is effective for verifying performance or checking behavior in advance, but it is not the setting where users and developers cross-check and confirm whether the contents described in the design document satisfy the users' requirements, so it is incorrect.
Incorrectエ
A progress meeting is a meeting held to share and manage whether the project's work is progressing on schedule and whether there are any delays or issues. Its purpose is management (grasping progress), and it is not an activity of technically verifying whether the design document's contents satisfy the users' requirements, so it is incorrect.
- A joint review is an activity in which users and developers jointly verify a deliverable (such as a design document) and detect, at an early stage, its alignment with requirements or any defects.
- Grasp the distinction that 'cross-checking documents to confirm = review' versus 'running something that actually works to verify = testing'. Integration testing and simulation are means of verifying by running, and a progress meeting aims at progress management; none of them is suitable as a means of confirming whether the requirements are satisfied.