Software engineering strategy: What is the development strategy called in which the executive control modules (high-level control and interfaces) of a system are coded and tested first, followed by lower-level modules?

Introduction / Context:
Choosing a development strategy influences testing order, integration risk, and feedback loops. In systems and firmware projects, teams often decide whether to start from user-visible control logic or from low-level utilities and drivers. This question checks understanding of the classic top-down approach.

Given Data / Assumptions:

• Executive control modules are created and validated first.
• Lower-level components are integrated afterward.
• We are identifying the strategy name used in software engineering literature.

Concept / Approach:

Top-down development begins with the overall architecture and high-level flow, building stubs for unimplemented services. As lower-level modules (drivers, utilities) are completed, the stubs are replaced and the system becomes fully functional while preserving the high-level control structure designed at the outset.

Step-by-Step Solution:

Verification / Alternative check:

Standard SE texts define top-down vs bottom-up: top-down proceeds from abstract control logic to concrete implementations; bottom-up starts from utilities and data structures and composes them upward.

Why Other Options Are Wrong:

• Bottom-up development: the inverse strategy, building from low-level modules first.
• Left-Right development: not a recognized strategy name in this context.
• All of the above / None of the above: distractors; only top-down fits the description.

Common Pitfalls:

Confusing top-down with incremental or spiral models; assuming top-down forbids concurrent bottom-up prototyping (hybrids are common, but the definition remains top-down).

Final Answer:

Top-down development