In systems analysis and design, errors made during the system analysis stage typically surface later during which downstream activities?

Introduction / Context:
Mistakes made during system analysis create misaligned requirements, missing constraints, and vague acceptance criteria. These defects are inexpensive to fix early but grow costlier and more disruptive as the project moves into system design, development, testing, and implementation. This question checks understanding of defect propagation through the life cycle.

Given Data / Assumptions:

• The project follows a typical life cycle with analysis, design, build, test, and implementation.
• Requirements quality strongly influences all downstream artifacts.
• Defect cost of change increases as the project advances.

Concept / Approach:
When analysis is weak, design teams architect for the wrong goals, developers build the wrong features, and testers verify against incomplete or ambiguous acceptance criteria. Therefore, analysis defects can appear in design reviews, integration, user acceptance testing, and even during production rollout as operational incidents.

Step-by-Step Solution:
1) Identify where analysis artifacts are consumed: design, development, testing, operations. 2) Trace one flawed requirement: it misguides designers and developers, then triggers test failures. 3) Conclude that symptoms surface in design, development, and implementation together. 4) Therefore the inclusive choice 'All of the above' is correct.

Verification / Alternative check:
Industry studies consistently show the rising cost of late requirement fixes and their visibility during integration, UAT, and production deployment.

Why Other Options Are Wrong:
Option A: Correct but incomplete because issues also show in design and development.
Option B: Correct but incomplete for the same reason.
Option C: Correct but incomplete because implementation is also affected.
Option E: Incorrect, since problems do surface downstream.

Common Pitfalls:
Believing that rigorous coding or testing can fully compensate for poor analysis. In practice, late fixes are expensive and risky.

Final Answer:
All of the above