What is the graphic representation that shows the control logic and module relationships of a system's processing functions?

Introduction / Context:
Different notations emphasize different views. A structured chart (structure chart) focuses on the architecture of modules—how they call one another, data passed, and control logic at the module level. It is distinct from narratives (Structured English) and end-to-end flow depictions (system flowcharts).

Given Data / Assumptions:

• We need a diagram emphasizing module decomposition and invocation relationships.
• Granularity is at the component/procedure level, not just data movement.
• Control logic is summarized via hierarchy, sequencing, selection, and iteration at the module-call level.

Concept / Approach:
A structured chart is typically a top-down diagram showing major modules, their submodules, and interfaces. It communicates coupling, cohesion, and control flow among modules, aiding partitioning and team assignment.

Step-by-Step Solution:
1) Map artifacts to viewpoints: data vs. control vs. narrative. 2) Identify the artifact that best reflects control and modular structure: structured chart. 3) Distinguish from system flowcharts (overall processing/data paths) and Structured English (textual algorithmic statements). 4) Select structured chart.

Verification / Alternative check:
Design methods present structure charts as the standard for depicting module hierarchies and interfaces.

Why Other Options Are Wrong:
Option A: “Structured analysis” is a methodology, not a specific diagram.
Option C: Narrative form, not a graphic hierarchy.
Option D: Emphasizes processes and data flows at a system level, not module call structure.

Common Pitfalls:
Confusing DFDs/system flowcharts with structure charts; the latter highlight module relationships and control.

Final Answer:
Structured chart