問49
頻出度★★★
システム開発において, システム要件定義の結果を受けてシステム化を進めるに当たり, 最初に行うべき作業はどれか。
平成23年度 秋期 ITパスポート試験 問49
マネジメント系システム開発技術 › システム開発技術
This question's explanation and your answers so far.
解説
問 49
Incorrectア
Formulating the migration plan means planning how to switch the developed system from the existing environment over to the new one, and it belongs to the late stage of development (the migration and acceptance phase), after design, implementation, and testing. It is not the first task done right after requirements definition.
Incorrectイ
The system test plan is a plan for checking whether the system as a whole operates according to the required specifications. It is drawn up after the system configuration — the division of functions between hardware and software — has been decided, that is, from system architectural design onward. While that division is still undecided, you cannot make concrete what to verify or how.
- ウ
正解 The correct answer is ウ. Once system requirements definition has fixed the functions and performance the system must satisfy, the next step is system architectural design, whose core is allocating those fixed requirements to hardware, to software, or to manual work done by people — that is, clarifying how the functions are divided. Until this division is decided, you cannot determine what the software should do or how far it should go, so you cannot begin the design and implementation from software requirements definition onward. Therefore, the task to be performed first upon receiving the results of system requirements definition is ウ, clarifying the functions that should be allocated between hardware and software.
Incorrectエ
Detailed design at a level that allows programming (detailed software design) is the step immediately before implementation, coming after system architectural design, software requirements definition, and software architectural design. It sits at the very back of the development process, so it cannot be the task to be performed first.
ここがポイント
- The order of the development process in the Common Frame (SLCP): system requirements definition → system architectural design → software requirements definition → software architectural design → detailed software design → programming → the various tests → migration. Remember the hierarchy: design at the system level comes first, design at the software level comes after.
- The role of system architectural design (system design) is to decide the division of functions — whether each system requirement is assigned to hardware, to software, or to manual work. Only once this is settled can you move on to requirements definition and design on the software side.
用語