Difficulty: Easy
Correct Answer: top-down refinement and data-flow analysis are emphasized
Explanation:
Introduction / Context:
Structured design emerged to manage complexity by decomposing systems into well-defined modules with clear interfaces. It emphasizes disciplined analysis prior to coding and employs standardized notations to reduce ambiguity. Understanding its guiding principles helps distinguish it from other approaches such as bottom-up design or ad hoc prototyping without formal artifacts.
Given Data / Assumptions:
Concept / Approach:
The method starts with requirements, models processes and data movement with DFDs, and refines into modules via top-down design. The aim is to isolate responsibilities, define inputs/outputs precisely, and minimize inter-module dependencies. While bottom-up can be useful for component reuse, the hallmark of structured design is the dominance of top-down refinement coupled with rigorous analysis artifacts that drive an unambiguous specification.
Step-by-Step Solution:
Verification / Alternative check:
Foundational texts (e.g., Yourdon/DeMarco) emphasize DFDs, structured charts, and refinement, supporting the selected statement as representative of structured design.
Why Other Options Are Wrong:
Common Pitfalls:
Equating structured methods with heavy documentation; the goal is clarity and testability, not paperwork for its own sake.
Final Answer:
top-down refinement and data-flow analysis are emphasized
Discussion & Comments