Software lifecycle reality: Mistakes made during the requirements analysis stage typically surface most visibly and expensively during which later stage of the SDLC?

Introduction / Context:
Errors introduced early in the Software Development Life Cycle (SDLC), especially during requirements analysis, propagate through design and coding. They frequently become highly visible and costly when the system is tested, because test execution reveals mismatches between expected behavior and implemented functionality.

Given Data / Assumptions:

• Requirements drive design, code, and tests.
• Defects are cheaper to fix earlier and costlier later.
• Testing is where discrepancies are detected against acceptance criteria.

Concept / Approach:
While errors can be noticed at any later stage, the System testing phase is where end-to-end behavior is evaluated against requirements and user scenarios. Ambiguities, omissions, or incorrect requirements often manifest as failing test cases, change requests, and rework. This is why robust requirements validation, prototyping, and early reviews are essential to reduce downstream surprises.

Step-by-Step Solution:

Verification / Alternative check:
Cost-of-change curves in software engineering consistently show higher remediation costs during system/acceptance testing and post-implementation, confirming the importance of early correctness.

Why Other Options Are Wrong:
Design and development may pass along the error without detection; implementation merely deploys what was built. Testing is the dedicated phase for validation.

Common Pitfalls:
Underinvesting in requirements reviews, prototypes, and user walkthroughs; writing tests that mirror flawed requirements without independent validation.

Final Answer:
System testing