現行システムの使用を開始してから10年が経過し, その間に業務内容も変化してきた。そこで, 全面的に現行システムを開発し直すことになった。開発者が, システム要求の分析と, それに基づく要件定義を行う場合, 開発者のシステム利用部門とのかかわり方として, 適切なものはどれか。
平成21年度 秋期 ITパスポート試験 問29
This question's explanation and your answers so far.
問 29
Incorrectア
If you avoid involving the user department, you cannot obtain the actual state of the business or the on-site requirements themselves. What requirements analysis needs is thorough interviewing of the user department, not cutting off information in the name of objectivity. The more you cut off involvement, the more omissions and errors the requirements contain, resulting in a system that cannot be used after development.
- イ
正解 Requirements definition is the process in which the developer organizes, completely and correctly, the business requirements that the system user department truly needs. Since the business operations have changed over ten years, the ones who know the right answer are the user department that runs those operations every day; the developer alone cannot detect omissions or misunderstandings in the requirements. So the compiled system requirements are read through together with the user department, and gaps in understanding or omissions are identified on the spot. This is a joint review. A joint review is the standard practice for confirming the validity of requirements at an early stage and preventing rework (specification changes and redoing work) in later processes, and it is also the occasion for obtaining the user department's agreement (approval). Therefore, choice イ, which states that the system requirements are reviewed jointly with the system user department, is appropriate.
Incorrectウ
The system requirements are the user department's business requirements themselves, so they are not something the developer may decide alone. If the user department's opinions are treated as merely reference material, the requirements diverge from the actual operations, causing major rework at acceptance testing or after the system goes into operation. Requirements must be agreed with the user department and approved before they are finalized.
Incorrectエ
The operation manual of the current system is merely a document describing what the current system can do; it does not reflect the present business requirements that changed over ten years. Deciding the functions based only on it would carry over the current system's constraints and functions that are no longer needed, failing to achieve the purpose of a complete redevelopment.
- In requirements definition the system user department (the client side, the people who actually perform the work) plays the leading role, while the developer elicits and organizes the requirements and confirms their validity and builds agreement through a joint review.
- A joint review is a technique for finding errors and omissions in requirements at an early stage of development, thereby lowering the cost of rework in later processes.