Design documentation visuals: Which diagram provides a graphic representation of system modules and their interconnections?

Introduction / Context:
Different diagrams communicate different aspects of a system. Selecting the right artifact speeds comprehension among analysts, developers, and testers. When the intent is to show modules (procedures/components) and how they call or relate to each other, a specific chart is traditionally used in structured design.

Given Data / Assumptions:

• We want module-level structure, not data or control flow detail.
• We need to depict interconnections/call relationships visually.
• Audience is familiar with structured design conventions.

Concept / Approach:
A structural chart (or structure chart) depicts modules as boxes linked by lines indicating invocation and interfaces. It emphasizes hierarchy, cohesion, and coupling. A flowchart details control flow inside a single process. “System chart” is vague, and a “pie chart” is for quantitative proportions, not architecture.

Step-by-Step Solution:

Verification / Alternative check:
Structured design texts use structure charts alongside module specifications to guide implementation and testing.

Why Other Options Are Wrong:

• Pie chart: Displays proportions, not architecture.
• Flow chart: Shows intra-process logic, not module interconnections.
• System chart: Ambiguous label without a standard definition.

Common Pitfalls:
Overloading flowcharts to represent architecture; failing to document interfaces and data passed between modules.

Final Answer:
Structural chart