問49
頻出度★★★
ユーザの要求を定義する場合に作成するプロトタイプはどれか。
平成28年度 春期 ITパスポート試験 問49
マネジメント系ソフトウェア開発管理技術 › 開発プロセス・手法
This question's explanation and your answers so far.
解説
問 49
Incorrectア
Software for users themselves to extract and process data from a core system describes tools such as spreadsheets or BI used in end-user computing (EUC); it is not a prototype for confirming requirements.
Incorrectイ
Something that describes the flow of business operations users request is a business flow diagram (such as a DFD) — a “diagram” — which differs from a prototype, a working piece of trial software.
Incorrectウ
Something that describes the interactions between users and the system is a “diagram” such as a use case diagram or a sequence diagram; this too is not a prototype (working software).
- エ
正解 A prototype is a simple (working) piece of software built early in development so that user requirements can be understood and confirmed. It is not a finished product but a rough implementation of screens and key functions that users actually try out, so that vague or mismatched requirements are found and corrected early. Choice エ, “a simple piece of software created to understand user requirements”, is exactly this definition and is therefore correct.
ここがポイント
- Definition of a prototype: a simple trial piece of software built early in the requirements-definition stage. It is actually run and shown to users so that mismatches in requirements are found and corrected early.
- The aim of the prototyping model is to align, early on, requirements that are hard to convey through documents or diagrams alone by using a “working trial build”. It is distinguished from diagrams (DFD / use case diagrams) and from EUC tools.
用語