問25
頻出度★★☆
システム開発における要件定義プロセスを説明したものはどれか。
平成21年度 春期 ITパスポート試験 問25
ストラテジ系システム企画 › 要件定義
This question's explanation and your answers so far.
解説
問 25
- ア
正解 The correct answer is ア. In the Common Frame, the life cycle of a system proceeds as “planning process → requirements definition process → development process → operation and maintenance process”. Among these, the requirements definition process takes over the systemization plan drawn up in the planning process, gives concrete shape to what is required of the newly built business and system (business requirements, functional requirements, and non-functional requirements), and fixes the scope and functions of systemization. Even more important, this is not decided by the developer side alone: it must be agreed among the stakeholders on the system acquirer’s side, such as the user departments, management, and the information systems department, and this agreement becomes the basis for the design and development that follow. Choice ア states “clarify the specifications of the newly built business and system, as well as the scope and functions of systemization, and reach agreement on them among the stakeholders on the system acquirer’s side”, which matches the definition of the requirements definition process itself.
Incorrectイ
This describes the planning process, the step that comes before the requirements definition process (formulating the systemization concept and formulating the systemization plan). Starting from the objectives and goals of the business, it compiles the requirements for the system that is needed and works out the systemization policy and the implementation plan (organization, schedule, cost, and so on). It has not yet reached the stage of fixing and agreeing on the individual business specifications or on the scope and functions of systemization.
Incorrectウ
This describes the development process. It covers everything from defining the system requirements and the software requirements, through system architecture design and software architecture design, up to actually building the system and the software products. The requirements definition process goes only as far as deciding and agreeing on “what is to be achieved”; it does not cover “how to build it”, such as architecture design or construction of the product.
Incorrectエ
This describes testing within the development process (software qualification testing and system qualification testing). It is the step that verifies whether things have been realized in line with the requirements already defined, not the step that establishes the requirements themselves and reaches agreement on them. Requirements definition is the side that creates the baseline (the requirements) against which these tests check.
ここがポイント
- Get the order of the processes in the Common Frame straight: planning (deriving the systemization policy and implementation plan from the business goals) → requirements definition (clarifying and agreeing on what is required of the business and the system) → development (requirements definition, architecture design, construction, and testing) → operation and maintenance. Telling which stage each choice refers to is the standard pattern for this type of question.
- The keywords of the requirements definition process are “clarifying the scope and functions of systemization” and “reaching agreement among the stakeholders on the system acquirer’s side”. Including consensus building is the biggest point that sets it apart from work that merely writes out a list of requests.
用語