問33
頻出度★★★
ソフトウェア詳細設計書に関する記述として, 適切なものはどれか。
平成21年度 秋期 ITパスポート試験 問33
マネジメント系システム開発技術 › システム開発技術
This question's explanation and your answers so far.
解説
問 33
Incorrectア
System integration testing is a higher-level process in which programs and subsystems are combined and run, and its test specifications correspond to system architectural design (where the plan for system integration testing is drawn up). What corresponds to the software detailed design document is the specification for unit testing, which checks each module individually. Because the design process and the test process are mismatched, this choice is wrong.
- イ
正解 Software detailed design is the process of refining each component (module) determined in software architectural design down to a level of detail that can be written directly as a program. The software detailed design document produced here describes, for each module, the processing steps, input and output data, the data structures used, and the calling relationships. In other words, programmers read this document as a blueprint and write code exactly as specified. Therefore, choice イ, which states that programming is carried out based on the software detailed design document, is appropriate. The development flow proceeds as: system requirements definition → system architectural design → software requirements definition → software architectural design → software detailed design → programming → unit testing → integration testing, and the detailed design document is the deliverable that comes immediately before programming.
Incorrectウ
What begins upon the completion of system requirements definition is system architectural design. After that come software requirements definition and software architectural design in turn, and only at the end does software detailed design begin. Creation of the detailed design document never starts immediately after requirements definition; this choice skips steps in the process order, so it is wrong.
Incorrectエ
The detailed design document is the input that programming depends on, so finalizing it only after unit testing is finished reverses the correct order. It is indeed necessary to reflect changes that arise after implementation back into the design document to keep it up to date (maintaining consistency for maintenance purposes), but that is a different matter from postponing its completion.
ここがポイント
- The software detailed design document is the direct input to programming: a blueprint for implementation that describes, module by module, the processing steps, inputs and outputs, and data structures.
- Correspondences in the V-model: system requirements definition ↔ system testing, system architectural design ↔ system integration testing, software detailed design ↔ unit testing. Learn how each design process pairs with its test process.
用語