Difficulty: Easy
Correct Answer: Structure chart
Explanation:
Introduction / Context:This question revisits the distinction between analysis and design artifacts. In structured design, we focus on how software modules interact and pass control/data.
Given Data / Assumptions:
Concept / Approach:Structure charts are the canonical tool in structured design, showing hierarchical module relationships, parameters, and coupling. They guide implementation and testing plans.
Step-by-Step Solution:
Select tool that shows hierarchy and calls → structure chart.Exclude DFDs (analysis of data movement).Exclude flowcharts (low-level control flow).Verification / Alternative check:Design reviews typically require structure charts to assess cohesion/coupling.
Why Other Options Are Wrong:DFDs and flowcharts target different concerns; a bare “module” list lacks relationships.
Common Pitfalls:Overly deep hierarchies and tight coupling; refactor to improve cohesion.
Final Answer:Structure chart
Discussion & Comments