In modular design, what is the hierarchical chart that decomposes a large program into lower level modules called?

Introduction / Context:
When designing software using top down decomposition, architects visualize how a system breaks into modules and how those modules relate. The artifact that captures this hierarchy is the structure chart.

Given Data / Assumptions:

• We need a design time view of modules and their calling relationships.
• Greater detail appears at lower levels.
• Objective is clarity of structure, coupling, and cohesion.

Concept / Approach:
A structure chart is a tree like diagram that shows modules, control flow, and data interfaces between parent and child components. It emphasizes low coupling and high cohesion and guides allocation of responsibilities before coding.

Step-by-Step Solution:

Verification / Alternative check:
Schema and sub schema are database terms. A module inventory is simply a list. Pseudo code is textual logic, not a hierarchical chart.

Why Other Options Are Wrong:

Common Pitfalls:
Over decomposing into tiny modules or ignoring interface definition both hinder maintainability.

Final Answer:
Structure chart.