Structured systems analysis deliverables: which item below would NOT typically be a major deliverable of the analysis phase?
-
AData dictionaries describing entities and attributes
-
BData flow diagrams showing processes and data movements
-
CEntity-relationship diagrams modeling data structures
-
DA high-fidelity prototype model (solution mock-up)
-
EContext diagrams and logical models
Answer
Correct Answer: A high-fidelity prototype model (solution mock-up)
Explanation
Introduction / Context:Structured systems analysis focuses on understanding the problem domain before solution design and implementation. Its deliverables emphasize logical models of processes and data, not fully realized solutions.
Given Data / Assumptions:
- Analysis produces logical representations (DFDs, ERDs, data dictionaries, context diagrams).
- Prototyping can occur, but high-fidelity prototypes are usually design-phase artifacts.
- We are distinguishing typical analysis outputs from later-phase deliverables.
Concept / Approach:Analysis asks “what” the system should do; design and build answer “how.” Detailed prototypes that mimic final behavior and UI are part of design/implementation validation, not core analysis.
Step-by-Step Solution:1) List standard analysis outputs: DFDs, ERDs, data dictionaries, context diagrams.2) Identify which item belongs to later phases: high-fidelity prototype model.3) Select the prototype as the atypical analysis deliverable.
Verification / Alternative check:Many methodologies (e.g., SSADM) reserve substantial prototyping for design/build, while permitting low-fidelity sketches during analysis if needed.
Why Other Options Are Wrong:DFDs, ERDs, and data dictionaries are canonical analysis artifacts; context/logical models likewise belong to analysis.
Common Pitfalls:Premature solutioning—jumping into implementation details before finalizing logical requirements.
Final Answer:A high-fidelity prototype model (solution mock-up).