問49
頻出度★★★
ソフトウェアの受入れに関する記述として, 適切なものはどれか。
平成22年度 春期 ITパスポート試験 問49
マネジメント系システム開発技術 › システム開発技術
This question's explanation and your answers so far.
解説
問 49
Incorrectア
It is wrong to say that there must be no involvement of the developer in the acceptance. That the acquirer is the party which judges pass or fail is a separate matter from whether the developer may provide support. In an actual acceptance, support from the developer — preparing the test environment, explaining operations, fixing the defects detected — is indispensable, and as long as the acquirer makes the judgment on its own initiative, the objectivity of the acceptance is preserved even when such support is received.
Incorrectイ
It is wrong to take the detailed design document as the criterion for judging the acceptance. The detailed design document is a deliverable in which the developer decided how to build the software internally; it does not express the business requirements that the acquirer asked for. Acceptance testing is carried out based on the requirements definition document and the order specification presented by the acquirer, from the viewpoint of whether the business operations can be performed as required. Verifying against the detailed design document belongs to the unit testing and integration testing stages carried out on the developer side.
Incorrectウ
It is wrong to say that the acceptance is carried out primarily by the developer; the responsible party is the other way around. If developers judged what they themselves built to have passed, the inspection would be meaningless and would not be an objective confirmation of quality. What the developer carries out on its own initiative goes only as far as the system test (overall test) before delivery; after that, judging whether the acceptance passes or fails falls within the responsibility of the acquirer, the party that placed the order.
- エ
正解 The correct answer is エ. Software acceptance is the work in which the party that placed the order and received the delivery (the acquirer) confirms whether the delivered software was built as required at the time of ordering, and then inspects and accepts it. The acquisition process of the Common Frame also stipulates that the responsibility for conducting acceptance tests and acceptance reviews and judging pass or fail lies with the acquirer. On the other hand, work such as building the test environment, preparing test data, explaining operations, and fixing the defects pointed out cannot proceed without the cooperation of the developer (supplier), so the developer plays the role of supporting the acceptance. Choice エ states exactly this division of roles — the acquirer judges, and the developer helps — so it is appropriate.
ここがポイント
- The party responsible for acceptance (acceptance testing and formal acceptance) is the acquirer, the party that placed the order, while the developer (supplier) is in a supporting position. This is the basic division of roles in the acquisition process of the Common Frame, and from it you can judge that a choice which reverses the responsible party, or which denies the developer's support, is wrong.
- The criterion for judging acceptance testing is the requirements presented by the acquirer, such as the requirements definition document and the order specification, not the detailed design document, which is an internal deliverable of the developer. It is unit testing and integration testing on the developer side that use the detailed design document as their criterion, so it is a good idea to memorize which document each testing stage verifies against.
用語