問37
頻出度★★☆
システム開発プロジェクトで作成されるドキュメントのうち, 開発の対象範囲を規定するものはどれか。
平成26年度 秋期 ITパスポート試験 問37
ストラテジ系システム企画 › 要件定義
This question's explanation and your answers so far.
解説
問 37
Incorrectア
A migration plan is a document that specifies by what procedure and on what schedule existing data and operations will be switched over to the completed new system. It is used at a stage where the scope has already been fixed and development is nearly finished, so it plays no role in defining the scope of development.
Incorrectイ
An integration test specification is a document that compiles the procedures and expected results used to verify that individual modules work together correctly once they are combined. It is a deliverable for checking, after the fact, the scope decided in the requirements definition document; it does not decide the scope itself.
- ウ
正解 The correct answer is ウ, the requirements definition document. Taking up the purpose of introducing the system, the requirements definition document is the deliverable in which the users and the developers agree on what functions and performance the business needs and fix that agreement in writing. It is here that the line is drawn between “this function will be built” and “this operation is out of scope”, so this is the document that defines the scope of development. What is written in the requirements definition document becomes the standard for all of the design, programming, and testing that follow, and it also serves as the reference for judging in later processes whether something was included in the requirements. Conversely, if the requirements definition document stays vague, the scope never becomes fixed, and this causes the work to expand without limit during development (scope creep).
Incorrectエ
A user manual is a document that explains to users how to operate the completed system. It is prepared toward the final stage of development or the start of operation, and is not a document that defines what will be developed.
ここがポイント
- A requirements definition document is the document that fixes, by agreement with the users, the functions and performance the system needs; it is the basis that defines the scope of development.
- Memorize each system development document together with its process: requirements definition document (what to build) → design document (how to build it) → test specification (was it built correctly) → migration plan and user manual (how to start using it).
用語