Difficulty: Easy
Correct Answer: IPO charts
Explanation:
Introduction / Context:
Before writing code, programmers analyze the problem to understand what information goes in, how it should be transformed, and what results must come out. A classic artifact that captures this end-to-end thinking is the IPO chart, short for Input–Process–Output. It provides a compact, structured summary that is easy for both technical and non-technical stakeholders to review.
Given Data / Assumptions:
Concept / Approach:
An IPO chart has three columns or sections: Inputs, Processing, and Outputs. Inputs list data items, sources, and preconditions. Processing outlines the major steps or rules that transform inputs into results. Outputs specify the required reports, screen fields, files, or messages. This structure directly supports validation (“Do we have every input we need?” “Are all outputs justified?”) and helps derive test cases for each transformation rule.
Step-by-Step Solution:
Verification / Alternative check:
Compare IPO with other artifacts. Flowcharts show control flow, which is useful later but can be too detailed for early analysis. Separate “input charts,” “output charts,” or “processing charts” fragment the view and make consistency checks harder. IPO integrates all three perspectives in one place.
Why Other Options Are Wrong:
Common Pitfalls:
Leaving units undefined, mixing detailed algorithmic logic with high-level processing, and failing to validate that every output is traceable to specific inputs and rules are common mistakes when preparing IPO charts.
Final Answer:
IPO charts.
Discussion & Comments