問2
頻出度★☆☆
システム構築プロジェクトを開始するに当たり，“品質”，“コスト”，“納期”の目標値を設定する段階として，適切なものはどれか。
平成22年度 秋期 ITパスポート試験 問2
ストラテジ系システム企画 › システム化計画
This question's explanation and your answers so far.
解説
問 2
- ア
正解 The correct answer is ア, drafting the system planning. In the Common Frame, the system life cycle proceeds in the order planning → requirements definition → development → operation → maintenance, and the planning process consists of two parts: drafting the system concept and drafting the system planning. Of these, drafting the system planning is the stage that turns the direction sketched out in the concept into an executable plan; it fixes the development structure and staffing, the overall schedule (delivery deadline), the necessary expenses (cost), the quality level to be achieved (quality), and even the risks and the return on investment. The stage the question refers to, where target values are set “when starting a project,” is exactly this planning work at the very top of the stream. Quality, cost, and delivery deadline are the basic management items called QCD in project management, and each of the later processes — requirements definition, development, and introduction — evaluates its progress and results against the target values set here.
Incorrectイ
Defining the system requirements belongs to the requirements definition process that comes after planning; it is the stage that decides the contents of what will be built — how the business will be systematized, and what functions, performance, reliability, and interfaces are needed. It is a process carried out along an already established plan, so the target values for the overall quality, cost, and delivery deadline of the project are not first set here.
Incorrectウ
Creating the software introduction plan is the stage that decides the procedures for introducing and migrating the completed deliverables into the production environment, and it comes fairly late in the life cycle. It deals with the work done at introduction time, such as data migration, user training, and switchover procedures, not with setting QCD targets at the start of a project.
Incorrectエ
Defining the software requirements is the stage, within the development process, that makes concrete the part of the system requirements that software is responsible for. Its scope is limited to the software unit, so it differs in granularity from setting targets for the project as a whole, and it also comes even later than planning and requirements definition; therefore it does not correspond to setting target values at the start of a project.
ここがポイント
- The order of the life cycle in the Common Frame is planning (drafting the system concept → drafting the system planning) → requirements definition → development → operation → maintenance. The target values for the overall quality, cost, and delivery deadline (QCD) of a project are set in drafting the system planning, the part of the planning process at the very top of the stream.
- The key is to distinguish the stage that sets the target values from the stage that builds the contents according to targets already decided. Requirements definition and the introduction plan are both later processes executed on the basis of the plan, not processes that decide the targets themselves.
用語