問32
頻出度★★★
図のプロセスでシステム開発を進める場合，システム方式設計に含める作業として，適切なものはどれか。 システム要件定義 → システム方式設計 → ソフトウェア要件定義 → ソフトウェア方式設計
平成24年度 秋期 ITパスポート試験 問32
マネジメント系システム開発技術 › システム開発技術
This question's explanation and your answers so far.
解説
問 32
Incorrectア
“Determining the functions and processing capacity of the system” is a task of system requirements definition, which is one step earlier in the figure. It is the stage where you clarify, as requirements from the user side, what functions the system should have and how much processing volume and response performance it must meet. It is a different process from system architectural design, which decides the means (the architecture) for realizing those requirements.
Incorrectイ
“Determining the top-level structure of the software and the software components” is a task of software architectural design, which comes last in the figure. It receives the portion that was assigned to software in system architectural design, divides it into components (program units), and determines the structure, so it is two steps later.
- ウ
正解 The correct answer is “ウ Determining the configuration of hardware and networks”. System architectural design is the process that takes over “what is to be realized”, which was fixed in the immediately preceding system requirements definition, and then decides “how to realize it” — that is, which component it should be assigned to: hardware, software, or manual work. The figure also shows that system architectural design comes right after system requirements definition and before software requirements definition, so it sits where the physical foundation supporting the whole system is settled before the contents of the software are worked out. Deciding hardware and network configurations, such as the number and models of servers and clients and the configuration of lines and LANs, is exactly a typical task of this stage.
Incorrectエ
“Determining the user interface” is a task of software requirements definition, which is one step later in the figure. It is the stage where the behavior of the software as seen by the user, such as the layout of screens and printed forms, is defined, and it is not yet handled at the point of system architectural design.
ここがポイント
- System architectural design is the process of allocating system requirements to hardware, software, or manual work for realization, and deciding the hardware configuration and the network configuration is included here.
- In the Common Frame, the development processes run in the order “system requirements definition (functions and processing capacity) → system architectural design (hardware and network configuration) → software requirements definition (the user interface, such as screens) → software architectural design (the top-level structure and components of the software)”. Keep track of which process each task belongs to by this order.
用語