問40
頻出度★★★
システム開発を, システム要件定義, システム方式設計, ソフトウェア要件定義, ソフトウェア方式設計, ソフトウェア詳細設計の順で実施するとき, ソフトウェア詳細設計で初めて決定する項目として, 適切なものはどれか。
平成25年度 秋期 ITパスポート試験 問40
マネジメント系システム開発技術 › システム開発技術
This question's explanation and your answers so far.
解説
問 40
- ア
正解 The correct answer is ア. Software detailed design is the phase that further breaks down the structure of components (parts) decided in software architecture design, refining it to a level of detail at which programming (coding) can be started directly. It is here that, for each individual program / module that serves as a unit of coding, the specifications are fixed for the first time: the processing it performs, its input and output data, and its internal algorithms and data structures. The five phases in the question follow the order “system requirements definition → system architecture design → software requirements definition → software architecture design → software detailed design”, moving step by step from the whole system down to individual programs. What is decided at that final stage, that is, the finest-grained item “the specification of each individual program”, corresponds to ア.
Incorrectイ
“The functions and response time required of the software” are requirements about what the software must satisfy, and they are decided in software requirements definition. Functional requirements (the necessary functions) and non-functional requirements (performance such as response time) are fixed at a stage before design begins, so this is not an item first determined in detailed design.
Incorrectウ
“The top-level structure of the target software” concerns the architecture, namely how the software is divided into components and how they are combined, and it is decided in software architecture design. Detailed design takes that structure as its premise and works out the inside of each part, so the top-level structure has already been determined before detailed design.
Incorrectエ
“The specification concerning the interfaces between multiple software components” is handled in system architecture design, where the whole system is allocated to constituent elements such as hardware, software, and manual operations, and the coordination among them is decided. Because it is determined in a phase higher than software detailed design, which deals with the inside of an individual piece of software, it is not an item first determined here.
ここがポイント
- The development phases follow the order “system requirements definition → system architecture design → software requirements definition → software architecture design → software detailed design → programming”, and the scope narrows step by step from the whole system down to individual programs. By looking at which level of granularity each item is about, you can judge which phase determines it.
- Software architecture design = the phase that divides software into components and decides the top-level structure; software detailed design = the phase that breaks components down into the programs (modules) that serve as units of coding and decides their specifications. This distinction is a frequently tested point.
用語