問10
頻出度★★☆
ソフトウェアライフサイクルを，企画プロセス，要件定義プロセス，開発プロセス，運用プロセスに分けるとき，要件定義プロセスの実施内容として，適切なものはどれか。
平成27年度 春期 ITパスポート試験 問10
ストラテジ系システム企画 › 要件定義
This question's explanation and your answers so far.
解説
問 10
Incorrectア
Migration of business operations and systems means switching the developed system over to the production environment and handing over the business operations and data of the old system to the new one. It is carried out in the stage where the latter part of the development process moves into the operation process, which is far downstream of requirements definition.
Incorrectイ
Drafting of the systemization plan means organizing the issues of the target business operations in light of the management strategy, and deciding the purpose, scope, schedule, organizational structure, rough cost estimate, and so on of systemization. It belongs to the planning process, which comes before requirements definition. The requirements definition process starts by taking this plan as its input.
Incorrectウ
Detailed design of the software is work at the level of implementation means, deciding how the requirements are to be realized (the internal structure of the programs and the processing content of the modules), and it belongs to the development process. The requirements definition process is the stage that decides “what is to be realized”, and it does not go into implementation methods.
- エ
正解 The correct answer is エ. The requirements definition process takes over the purpose and scope of systemization decided in the planning process, and is the stage that clarifies “whose needs must this system satisfy, and what are they?”. The starting point here is the identification of stakeholders (executives, users in the business departments, operations staff, business partners, and so on). Their needs, requests, and constraints are drawn out without omission and organized, then compiled into business requirements and system requirements, and agreed upon among the parties concerned. Choice エ, “Identification of stakeholders' needs”, is exactly the entry-point activity of this requirements definition process, so it is appropriate.
ここがポイント
- Requirements definition process = the stage that identifies stakeholders, draws out their needs and constraints, defines them as business requirements / system requirements, and reaches agreement among the parties concerned (it decides “what is to be realized”).
- Use the flow of the Common Frame, “planning → requirements definition → development → operation”, to tell apart the work handled by each stage: planning = drafting of the systemization plan; requirements definition = identification of stakeholders' needs and agreement on the requirements; development = design, implementation, and testing; operation = running and evaluation after the migration.
用語