問33
頻出度★★★
ある開発プロジェクトでソフトウェア結合テストを終了し, システムの機能を確認するシステムテストを行っている。このシステムテストで, あるプログラムに不良が多発しているとの報告があった。プロジェクトマネージャが最初に行うべきこととして, 最も適切なものはどれか。
平成22年度 春期 ITパスポート試験 問33
マネジメント系プロジェクトマネジメント › プロジェクトマネジメント
This question's explanation and your answers so far.
解説
問 33
Incorrectア
Starting over from the software integration testing is rework on the largest scale, sending the entire process back. The defects are concentrated in only one particular program, and rolling everything back while neither the cause nor the scope of impact has been confirmed would cause excessive losses in cost and schedule. This is an option to consider only once a re-evaluation of the quality has revealed that the quality of the integration testing was insufficient; it is not the first thing to do.
Incorrectイ
Adding testing personnel is only symptomatic treatment for the schedule delay, and it solves nothing about the quality problem of the program itself, which is the cause of the frequent defects. Increasing the number of people who test does not reduce the defects already built into the program, and adding staff can even invite further delay through the burden of handover and training. Putting resources in without grasping the cause and the impact gets the order wrong.
- ウ
正解 The correct answer is ウ. At the point when a report comes in during system testing that “defects are occurring frequently in a certain program,” it is not yet known why they are occurring so often (whether the cause lies in the design or in the implementation, or whether the test data is at fault), nor how far the impact reaches (the integration points with other functions, the later tests, the schedule). What the project manager should do first is to grasp the facts: re-evaluate the quality of the problematic program to clarify the number of defects, their causes, the process in which they were introduced, and how widely they have spread, and then determine the impact on the system testing as a whole. Countermeasures such as starting over, adding personnel, or recreating the program should be chosen only on the basis of the facts obtained from this re-evaluation. Among the choices, only ウ grasps the current situation and the impact instead of jumping straight to a countermeasure, so it is the most appropriate as the first thing to do.
Incorrectエ
Removing the program from the test scope and recreating it is major rework carried out without confirming the cause. If the cause of the defects lies in the specification or the design, the same defects will reappear even after it is rebuilt, and while it is out of the test scope the testing of its integration points with other functions cannot proceed, so the system testing as a whole stalls. Whether recreating it is appropriate is also something to judge only after first re-evaluating the quality and grasping the impact.
ここがポイント
- The project manager's basic sequence of actions when trouble occurs is: grasp the facts and the current situation → analyze the scope of impact → plan and carry out countermeasures. What is being tested here is not jumping to countermeasures such as starting over, adding personnel, or rebuilding while neither the cause nor the impact is known.
- Frequent defects are a sign of poor quality, and re-evaluating the quality of that deliverable to determine its impact on the following process (here, the system testing) is the standard practice of quality management. Only once the impact is grasped can appropriate corrective action and schedule adjustment be judged.
用語