情報システム戦略策定の主たる目的として, 適切なものはどれか。
平成26年度 秋期 ITパスポート試験 問30
This question's explanation and your answers so far.
問 30
Incorrectア
“Clarify the requirements for the business and information systems to be newly built, and based on that, determine the scope of IT adoption and specify its concrete functions” is the purpose of the requirements definition process. For an individual development project, it fixes what the users want to do (business requirements) and how much of that will be realized by the system (functional and non-functional requirements); its granularity goes all the way down to the level of concrete functions. An information systems strategy sits above this: it gives direction on which areas to invest in in the first place and on how the company's information systems as a whole should be organized, so the level of the purpose is different. Requirements definition is carried out after the strategy and the systematization plan have been decided.
- イ
正解 The correct answer is イ. An information systems strategy is a policy that defines, from a medium- to long-term viewpoint, how information systems should be positioned and how they should be developed in order to realize the management strategy. The main purpose of formulating it is to draw the ideal form (To-Be) of the organization's whole information system based on the management strategy, and to decide the policy for overall optimization. There are two key points. First, the starting point is the management strategy — information systems are not built up from the bottom out of requests from the field; they are given direction from above as a means of achieving management goals (increasing sales, cutting costs, launching new businesses, and so on). Second, the target is not an individual business system but the organization's information systems as a whole — if each department builds systems on its own, data and functions end up duplicated and systems cannot be linked with one another (so-called partial optimization, or siloing), which is very wasteful when viewed company-wide. To avoid this, an overall optimization policy and an overall optimization plan are set, and the way shared information is held and the standard technology infrastructure are decided across the whole organization; this is exactly what formulating an information systems strategy means. A representative method for pursuing this overall optimization systematically is EA (Enterprise Architecture), which describes the current state (As-Is) and the ideal state (To-Be) at the business, data, application, and technology layers, and then creates a migration plan to close the gap. Choice イ states exactly those three elements — based on the management strategy, the ideal form of the entire information system, and deciding the overall optimization policy for the organization — so it is appropriate.
Incorrectウ
“For information system development, decide the development method and management method as an organization, and based on them, set the standard procedures for development and management” is the purpose of standardizing system development (establishing development standards and project management standards). It is an effort to keep quality from varying and to let development and management follow the same procedures even when the person in charge changes. It does indeed cover the whole organization, but what it decides is how development is carried out (the process), not the ideal form of the information systems based on the management strategy. An information systems strategy answers what to build and where to invest, whereas ウ answers how to build, so the purposes are different.
Incorrectエ
“Organize the requirements concerning the construction of the information system for the target business, and create the systematization policy and the implementation plan for its construction” is the purpose of the systematization plan (drawing up the systematization concept and plan). It is easy to confuse with イ, but the decisive point is the scope: as its opening words “for the target business” show, エ takes an individual business or individual project as its unit, and its deliverables are the systematization policy and implementation plan for that project (structure, schedule, cost, and so on). An information systems strategy comes before individual projects and decides an overall optimization policy with the whole organization as its unit; the systematization plan for each business is positioned under that policy. Not mixing up the relationship between the whole (イ) and the individual (エ) is what decides this question.
- The purpose of formulating an information systems strategy is to clarify, based on the management strategy, the ideal form of the information systems of the entire organization, and to decide the policy for overall optimization. The keywords are alignment with the management strategy, overall optimization, and the medium- to long-term ideal form; the aim is to prevent partial optimization by individual departments (duplicated investment, systems that cannot be linked). The method for pursuing overall optimization systematically is EA (Enterprise Architecture).
- Remember the correspondence between the steps from planning to development and their purposes as a hierarchy: information systems strategy (overall optimization policy for the whole organization) → systematization plan (systematization policy and implementation plan for an individual business) → requirements definition (clarifying the scope of IT adoption and the concrete functions) → development. Tell strategy from plan by whether the choice says the whole organization or the target business; and judge that talk of development methods and standard procedures is about establishing development standards, not about strategy.