システム開発のプロセスには, ソフトウェア要件定義, ソフトウェア方式設計, ソフトウェア結合テスト, ソフトウェア導入, ソフトウェア受入れなどがある。システム開発の関係者を開発者側と利用者側に分けたとき, ソフトウェア受入れで実施する作業はどれか。
平成28年度 春期 ITパスポート試験 問42
This question's explanation and your answers so far.
問 42
Incorrectア
Deploying the completed software into the production environment is a task of software installation, and it is also done by the developer side. It is a separate process from acceptance (the step where the user side confirms), so it is wrong.
Incorrectイ
Conducting interviews with the user side to clarify the required functions and performance is a task of software requirements definition, which is the entry point of development. Its process differs from acceptance in the final stage, so it is wrong.
- ウ
正解 Software acceptance (acceptance testing) is the final stage of system development, in which the user side confirms that the delivered software has the functions and performance defined in the requirements and has reached a level where it can actually be used, and then accepts it. Choice ウ states that “the user side confirms that the software meets the requirements and is at a usable level,” so both the party that performs acceptance (the user side) and its purpose (confirming that the requirements are met and the software is usable) are correct. Therefore, ウ is the correct answer.
Incorrectエ
Having the developer side review whether the software requirements definition document satisfies the user side's needs is validation at the requirements definition stage, and the deliverable is still just a document. This differs from acceptance, in which the user side checks working software, so it is wrong.
- Software acceptance = the final step (acceptance testing) in which the user side confirms and approves whether the completed software meets the requirements and is usable.
- For each step of the development process (requirements definition, architecture design, integration testing, installation, acceptance), match and distinguish who does what.