問42
頻出度★★★
ソフトウェア詳細設計の結果, ソフトウェア仕様書を作成した。この結果を受けて開発の次工程を担当する者は誰か。
平成25年度 春期 ITパスポート試験 問42
マネジメント系システム開発技術 › システム開発技術
This question's explanation and your answers so far.
解説
問 42
Incorrectア
A system auditor inspects and evaluates, from the standpoint of an independent third party, whether an information system and its development and operation are appropriate, and then reports the audit results. The auditor is not a worker built into the development process, and is not in a position to receive the deliverables of detailed design and carry the next process forward.
Incorrectイ
The system operator is involved in the operation process that comes after development and testing are finished and the system has been migrated to the production environment (daily operation monitoring, running jobs, backups, handling failures, and so on). Right after detailed design, not a single line of the program has been written yet, so it is not the operator’s turn.
Incorrectウ
The system user takes an active part in upstream requirements definition and in acceptance testing (user acceptance testing) after the system is completed. Detailed design is the process in which the development side decides how the system is built internally, and the user is not the one who receives its deliverables and takes charge of the next process.
- エ
正解 The correct answer is エ (Programmer). Software development proceeds from upstream to downstream in this order: software requirements definition → software architectural design (external design) → software detailed design (internal design, program design) → programming (coding) → testing → migration and operation. Software detailed design is the process that decides how the program is actually to be built — the internal structure of modules, the processing procedures, the data structures — and its deliverables, the specification and design documents, serve directly as the instructions for implementation. Therefore the person who receives these deliverables and takes charge of the next process is the programmer, who writes the source code exactly as specified and carries out unit testing. Once you have the handover from design to implementation in mind — the chain of roles “the person who writes the design document (systems engineer) → the person who writes the code (programmer)” — it is clear that エ is the only choice that performs the actual work of a development process.
ここがポイント
- Learn the order of the software development processes: software requirements definition → software architectural design (external design) → software detailed design (internal design) → programming (coding) → testing → migration and operation. The process after detailed design is programming, and the person in charge is the programmer.
- Separate out who is in charge of each process: the user handles requirements definition and acceptance testing, the systems engineer handles design, the programmer handles implementation and unit testing, the operator takes over after the system goes live, and the system auditor inspects independently from outside the processes.
用語