In the SDLC, what is the principal deliverable of the system investigation phase that summarizes findings and recommends whether to proceed?

Introduction / Context:
The system investigation phase is an early SDLC activity that frames the problem, explores solution approaches at a high level, and assesses viability. Its output guides executives on whether the project should advance to detailed requirements and design.

Given Data / Assumptions:

• Investigation focuses on problem definition, scope, alternatives, risks, and value—not detailed design.
• Stakeholders need a concise recommendation.
• Economic, technical, and operational feasibilities are examined.

Concept / Approach:
The feasibility report summarizes the business need, current-state pain points, proposed alternatives, preliminary cost–benefit analysis, risk profile, and a go/no-go recommendation. It does not lock in full requirements or detailed designs; those follow if the recommendation is positive.

Step-by-Step Solution:
1) Conduct preliminary analysis and stakeholder interviews.2) Evaluate feasibility dimensions and outline solution options.3) Estimate high-level costs and benefits; identify risks and mitigations.4) Compile findings into a feasibility report with a recommendation.

Verification / Alternative check:
Methodologies consistently place the formal feasibility assessment before requirements specification. Requirements and design reports are deliverables of later phases.

Why Other Options Are Wrong:
A design report: belongs to design phase after requirements.A requirement report: produced in the analysis/requirements phase.All of the above: incorrect because investigation culminates specifically in a feasibility report.None of the above: incorrect because a feasibility report is correct.

Common Pitfalls:
Overcommitting to a solution during investigation; underestimating change-management costs; skipping stakeholder validation before making the go/no-go decision.

Final Answer:
A feasibility report