問19
頻出度★☆☆
システムのライフサイクルを企画プロセス, 要件定義プロセス, 開発プロセス, 運用プロセス, 保守プロセスに分けたとき, 企画プロセスの完了時の状態として適切なものはどれか。
平成25年度 秋期 ITパスポート試験 問19
ストラテジ系システム企画 › システム化計画
This question's explanation and your answers so far.
解説
問 19
- ア
正解 The correct answer is ア. In the Common Frame, the system life cycle is arranged in the order planning process → requirements definition process → development process → operation process → maintenance process. The planning process at the head of this sequence is the most upstream study stage, in which, starting from the management strategy and management objectives, the “formulation of the systemization concept” and the “formulation of the systemization plan” are carried out. Here, after analyzing management issues and needs, the target scope of systemization is set — which operations are to be supported by the system and to what extent — and the overall system configuration and the basic architecture (the broad approach to hardware, software, and networks) for realizing that scope are given direction, together with a rough plan for the return on investment, the development structure, and the schedule. Therefore, the state at the completion of the planning process matches the statement in ア: “The scope of systemization, the system configuration, and the basic architecture required to achieve the management objectives have been determined.” The key point is the distinction between stages: the planning process only fixes the framework and the policy of what is to be built and how far, while the individual requirements that the system should have are not yet defined.
Incorrectイ
“The requirements and constraints for the system have been determined” describes the state at the completion of the requirements definition process, which follows the planning process. In the requirements definition process, taking over the scope of systemization set during planning, the functional requirements the system must realize, the non-functional requirements such as performance and security, and constraints such as budget, delivery deadline, and legal regulations are identified in concrete terms and agreed upon. At the planning process stage only the framework and policy have been settled, and the individual requirements and constraints are not yet fixed, so this is wrong.
Incorrectウ
“The software requirements optimized in light of the system requirements have been determined” describes the state at the end of software requirements definition (the work that precedes software architectural design) within the development process, a later stage than requirements definition. That work allocates the system requirements to hardware, software, and manual operations, and elaborates the portion handled by software into requirements; seen from the planning process it is two stages ahead. As the state at the completion of the planning process, therefore, it is wrong.
Incorrectエ
“The requirements concerning the organization for the business and operations that include the target system have been determined” describes the state at the completion of business requirements definition (defining the procedures of the target operations, the division of roles, the operating structure, and so on) within the requirements definition process. How to reorganize business flows and the operating organization on the premise of the new system is something examined after the scope of systemization has been decided, and it is not yet fixed at the time the planning process is completed. It is therefore wrong as the state at the completion of the planning process.
ここがポイント
- Memorize the order of the system life cycle in the Common Frame together with the deliverables of each process. Planning process = taking over the management objectives, decide the scope of systemization, the system configuration, and the basic architecture (systemization concept, systemization plan); requirements definition process = decide the functional requirements, non-functional requirements, and constraints for the system as well as the requirements for the business and the operating organization; development process = derive the software requirements from the system requirements and carry out design, implementation, and testing; operation process = live running and day-to-day operation; maintenance process = corrections and improvements after the system is in operation.
- The planning process is the most upstream stage, starting from the management strategy, and it is no more than the stage that decides the policy and framework of “what is to be systemized and how far”. The individual requirements are settled only in the next stage, the requirements definition process; this separation of stages is the decisive point for solving questions of this kind.
用語