問12
頻出度★☆☆
ソフトウェアライフサイクルの主プロセスを, 企画, 要件定義, 開発, 運用, 保守に分け, 企画プロセスでシステム化計画の立案を行うとき, そこで実施する作業として, 適切なものはどれか。
平成22年度 春期 ITパスポート試験 問12
ストラテジ系システム企画 › システム化計画
This question's explanation and your answers so far.
解説
問 12
Incorrectア
Clarifying the “business requirements” — the content, rules, and constraints of the target business — is a task of the requirements definition process, which comes after planning. It is the stage where, once the planning process has modeled the business and fixed the target scope, what is needed to make that business work is settled as requirements; it is not a task of the planning process.
- イ
正解 In the Common Frame (SLCP), the main processes of the software life cycle are placed in the order planning → requirements definition → development → operation → maintenance, and the level of detail becomes finer the further along you go. The first process, planning, consists of “formulating the systemization concept” and “formulating the systemization plan”. At this point the individual system functions are not yet being decided; rather, taking up the needs of management, this is the stage that decides “which business operations are to be systemized, within what scope, and with what organization, cost, and schedule”. For that reason, when formulating the systemization plan you first confirm and analyze the target business, diagram the business flow and the business functions as a business model, and identify the current problems and the scope to be systemized. Choice イ, “Confirm and analyze the target business, and model the business functions”, is exactly this task, so イ is appropriate.
Incorrectウ
Clarifying the “system requirements” — the functions, capabilities, security, and so on of the target system — is system requirements definition, which is carried out after the business requirements have been received; it is a task later than the planning process (from requirements definition through development). Going this far at the planning stage would mean deciding the system specifications while the target scope has not even been fixed yet.
Incorrectエ
Creating a test specification document is a task performed in the development process, after the system requirements and software requirements have been fixed. Only once what is to be built and how it is to be built have been decided can the test viewpoints and pass/fail criteria be written; at the planning-process stage, where the systemization plan is being formulated, there is no way to create it.
ここがポイント
- The planning process consists of “formulating the systemization concept” and “formulating the systemization plan”. Formulating the systemization plan involves confirming and analyzing the target business, modeling the business functions, and examining the scope to be systemized, the overall schedule, the organization, and the cost-effectiveness.
- The main processes are refined step by step: planning (modeling the business) → requirements definition (business requirements) → development (system requirements, design, testing) → operation → maintenance. By looking at which level of detail a choice is talking about, you can tell which process the task belongs to.
用語