問10
頻出度★☆☆
情報戦略に基づいて, 開発の対象業務, 費用, スケジュール, 体制, 投資効果などを明確化する業務はどれか。
平成24年度 春期 ITパスポート試験 問10
ストラテジ系システム企画 › システム化計画
This question's explanation and your answers so far.
解説
問 10
Incorrectア
The operations task is the work of actually running a system that has been developed and introduced, and of keeping it in a state where users can use it without trouble day to day. Specifically, it centers on running and monitoring jobs according to the operations plan, backing up and restoring data, managing user accounts, answering inquiries and giving first-line response when failures occur, and maintaining the availability and response times promised in the service level agreement (SLA). In terms of timing it is a stage after the system is complete, and what it deals with is the quality of the running service and day-to-day operating costs. It is not the stage that, based on the information strategy, first estimates the target operations, development costs, development schedule, development organization structure, and investment effect of a system yet to be built and obtains approval for the investment.
Incorrectイ
The development task is the stage that actually builds the system, taking as input the plan approved in the planning task and the requirements agreed in the requirements definition task. It covers system design (external design and internal design), programming, the various tests from unit testing through integration testing, migrating data from existing systems, and preparing for the start of operation. In other words, the development task is the side that builds within a budget, schedule, and organization structure given to it in advance; it is not the side that decides that budget, schedule, organization structure, or investment effect itself based on the information strategy. The question asks for the stage that decides them, so the development task, which executes inside a framework already fixed, does not apply. In terms of order as well, note that it comes after the planning task: planning → requirements definition → development.
- ウ
正解 The correct answer is ウ, the planning task. The planning task (called the planning process in the Common Frame) sits at the very top of the system life cycle, which runs planning → requirements definition → development → operations → maintenance. Taking the information strategy (IT strategy) derived from the management strategy as its starting point, it is the stage that decides the overall framework of what will be built, at what cost, by when, and by whom. Concretely, it proceeds in two steps. First, in drawing up the system concept, management issues and operational problems are organized, and a direction is sketched out for which business areas will be addressed with IT. Next, in drawing up the system plan, that concept is turned into an executable plan. What gets documented here is exactly the set of items the question lists: which operations are made the target of the system (the target operations of development), how much development and introduction will cost (costs), when work starts and when the system goes live (schedule), how internal departments and external contractors divide the work (organization structure), and how much return the investment is expected to bring, such as reduced working hours or increased sales (investment effect, that is, cost-effectiveness). Putting all of this together, presenting it to management, and obtaining approval on whether to invest is the goal of the planning task. Only once the scope, budget, timeline, and organization structure are settled here can the flow move on to the requirements definition task, where individual requirements are made concrete, and then to the development task, where the system is actually built. Conversely, starting development without this estimation and approval leads to cost overruns, missed deadlines, and a system that does not justify its investment. Therefore, the task that clarifies these five items based on the information strategy is ウ, the planning task.
Incorrectエ
The maintenance task is the work performed on a system that has already gone live: fixing defects found during operation, responding to changes in laws and regulations, adding and improving functions in line with changes in the business, improving performance, and keeping up with hardware replacement. Like the operations task, its object is a system that already exists and is running, and it sits at the very end of the life cycle. It is not the upstream decision-making stage that judges from the information strategy whether to build a new system and clarifies the target operations, costs, schedule, organization structure, and investment effect in order to obtain management approval. Note that when maintenance calls for a large-scale modification, the relationship is that you go back to the planning task and draw up the plan again.
ここがポイント
- The role of the planning task (planning process) — the most upstream stage, which takes the information strategy derived from the management strategy and draws up the system concept and the system plan. In the system plan, the target operations of development, costs, schedule, organization structure, and investment effect (cost-effectiveness) are clarified, and management approval on whether to invest is obtained. The decisive clue for the answer is that the five items listed in the question are exactly the contents recorded in the system plan.
- The order of the software life cycle — planning → requirements definition → development → operations → maintenance. Remember them by separating out the purpose and timing of each task: planning decides whether to build and sets the broad outline, requirements definition makes concrete and agrees on what to build, development builds within the fixed framework, and operations and maintenance keep the service running and respond to change after go-live.
用語