システム開発のプロセスには,システム要件定義,システム方式設計,システム結合テスト,ソフトウェア受入れなどがある。システム要件定義で実施する作業はどれか。
平成29年度 秋期 ITパスポート試験 問55
This question's explanation and your answers so far.
問 55
Incorrectア
The commissioning party using the software under conditions identical to actual operation and confirming that it runs normally is the task of “software acceptance” listed in the question. It is where the commissioning party decides whether to accept the system in the final phase of development, a different process from requirements definition in the earliest phase.
Incorrectイ
Creating the system test plan and preparing the test environment are preparatory tasks aimed at the testing process, and they belong to the test planning and execution stage rather than requirements definition. Because they are performed after the requirements have been fixed, this choice is wrong.
- ウ
正解 System requirements definition is the process of clarifying what the target system should achieve—that is, identifying and making clear the functions that users and business operations need (functional requirements) and the quality attributes such as performance, reliability, and response time (non-functional requirements). Choice ウ, “Clarify the functions and performance required of the system,” describes the very act of defining these requirements, which is the central task of system requirements definition. Therefore the correct answer is ウ.
Incorrectエ
Writing the program (coding) and reviewing the test results according to the evaluation criteria are tasks performed in the programming and testing processes that come after architectural design. They fall into the implementation and verification stage, which is later than requirements definition where you decide what to build, so this choice is wrong.
- System requirements definition is the process of deciding “what to build,” and its central task is to clarify the system’s functional requirements and non-functional requirements such as performance.
- Grasp the order of the system development processes (requirements definition → architectural design → programming → integration/system testing → acceptance) and the correspondence between each process and the tasks performed in it.