In systems analysis (requirements and logical design), which of the following is NOT typically used as an analysis tool: system test data, decision tables, data flow diagrams (DFDs), or flowcharts?

Introduction / Context:
Systems analysis focuses on discovering and documenting what a system should do before building it. Analysts rely on visual and tabular techniques to express logic, data movement, and rules. This question asks you to separate analysis tools from testing artifacts used later in the lifecycle.

Given Data / Assumptions:

• Phase: analysis (requirements and logical models), not testing.
• Candidate techniques: decision tables, data flow diagrams, flowcharts.
• Test data is generally associated with verification/validation phases.

Concept / Approach:

Decision tables enumerate conditions and actions, clarifying business rules. Data flow diagrams (DFDs) model processes, data stores, and data movement. Flowcharts capture procedural logic at a high level. In contrast, system test data are crafted to verify implemented functionality and are not core tools for analysis modeling.

Step-by-Step Solution:

Verification / Alternative check:

Standard SDLC mappings place decision tables/DFDs/flowcharts in analysis/design deliverables; test data creation belongs to the testing plan and quality assurance phases.

Why Other Options Are Wrong:

Decision tables, DFDs, and flowcharts are well-established analysis instruments.

“None of the above” is incorrect because one option (system test data) does not belong to analysis.

Common Pitfalls:

Confusing documentation created during analysis with artifacts created for QA. Maintain a clear phase boundary to avoid rework.

Final Answer:

System test data