あるシステムの開発において, システムを 24 時間連続稼働させることになった。稼働時間について利用部門と取決めを行う工程はどれか。
平成21年度 秋期 ITパスポート試験 問32
This question's explanation and your answers so far.
問 32
Incorrectア
System integration testing is the process of combining the separately built software and hardware and verifying whether the system works correctly as a whole. It is the stage for checking that the system behaves according to requirements that are already fixed, not the place where the operating time itself is agreed with the user department.
Incorrectイ
System testing is the process of confirming whether the completed system satisfies the requirements decided in system requirements definition (including the 24-hour continuous operation). It is on the side that verifies what has been agreed, not the process in which the agreement is made.
- ウ
正解 System requirements definition is the process of organizing the demands of the user department (the business side), clarifying the functional and non-functional requirements that the system must satisfy, and reaching agreement among the stakeholders. Operating the system continuously for 24 hours is a non-functional requirement about availability and operating time, and agreements such as from when to when it must run and whether there are time slots in which it may be stopped become the premise for the later design and testing. Therefore, the process in which the operating time is agreed with the user department is system requirements definition, the most upstream process of development.
Incorrectエ
Software architectural design is a design process on the developer side that decides with what structure (component breakdown and interfaces) the software will be built in order to realize the fixed requirements. It is not the process of agreeing on requirements with the user department.
- Non-functional requirements such as operating time, availability, performance, and security must be identified in system requirements definition and agreed with the user department, just like functional requirements.
- In the flow of the Common Frame (system requirements definition, system architectural design, software architectural design, and so on through system integration testing and system testing), the roles are separated: agreeing on things belongs to the upstream requirements definition, while checking whether they are satisfied belongs to the downstream tests.