When a project combines top-down decomposition with bottom-up aggregation and validation, what is this blended method typically called?

Introduction / Context:
Project and system design methods often leverage both top-down and bottom-up perspectives. Top-down starts from goals and breaks work into smaller parts, while bottom-up builds from detailed components and evidence back to the whole. The recognized blended strategy is an integrative approach that fuses the two for better completeness and feasibility.

Given Data / Assumptions:

• There are high level objectives and architectural constraints.
• There exist detailed components, data, or reusable services that influence feasibility.
• Consistency across abstraction levels is required.

Concept / Approach:
The integrative approach decomposes goals (top-down) while continuously validating with component capabilities, proofs of concept, and empirical data (bottom-up). It prevents designs that look good on paper but fail in reality, and it avoids myopic assembly of parts without strategic alignment.

Step-by-Step Solution:

Verification / Alternative check:
A quick check is whether decisions reflect both strategic goals and the truths discovered in detailed spikes or pilots. If so, you are working integratively rather than only top-down or only bottom-up.

Why Other Options Are Wrong:

Common Pitfalls:
Locking designs too early without component validation, or conversely, assembling parts opportunistically without architectural cohesion.

Final Answer:
Integrative approach.