Curioustab Logo Curioustab
Home » Computer Science » System Analysis and Design

What is a structure chart in software design and how is it used to partition a program?

Difficulty: Easy

Correct Answer: A hierarchical partitioning of a program into modules with defined interfaces

Explanation:


Introduction / Context:
During design, teams need a clear view of how a program is broken down and how modules communicate. The artifact that expresses this hierarchy and the associated interfaces is the structure chart.


Given Data / Assumptions:

  • Top down design is being applied.
  • Multiple modules will collaborate.
  • Interfaces must be identified early.


Concept / Approach:
A structure chart depicts parent child relationships, control flow, and data passed between modules. It encourages low coupling and high cohesion and informs staffing, integration planning, and test design.


Step-by-Step Solution:

1) Start from main responsibilities at the root. 2) Decompose into child modules that each have a single purpose. 3) Draw connections and annotate parameters or data structures passed. 4) Review for excessive coupling and refactor as needed. 5) Use the chart to drive incremental integration testing.


Verification / Alternative check:
If the artifact is a business or requirements document, it is not a structure chart. The correct choice explicitly states hierarchical partitioning into modules.


Why Other Options Are Wrong:

Business objectives and requirement statements are not design hierarchy diagrams. Screen layout and change request logs are separate deliverables.


Common Pitfalls:
Equating structure charts with class diagrams or omitting interface details are common errors.


Final Answer:
A hierarchical partitioning of a program into modules with defined interfaces.

← Previous Question Next Question→

More Questions from System Analysis and Design

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion