During Phase 1 (preliminary investigation and analysis) of the System Development Life Cycle, which aspects are typically examined to define scope and feasibility—outputs, input transactions, or controls?

Introduction / Context:
Early SDLC phases validate that a proposed system is feasible and worth building. Analysts must understand what information the system must produce (outputs), what data it will collect or receive (inputs), and how integrity and compliance will be ensured (controls). A balanced view prevents rework later.

Given Data / Assumptions:

• Phase 1 focuses on current-state assessment and high-level requirements.
• Outputs define value; inputs fuel processing; controls assure quality, security, and auditability.
• Stakeholders include users, auditors, and IT operations.

Concept / Approach:

Good analysis starts with outputs (what decisions need what reports or services), then works backward to inputs and processing. Controls (validation, authorization, logging) are integral from the start to meet regulatory and security needs. Ignoring any leg of this triad risks failure or noncompliance.

Step-by-Step Solution:

Verification / Alternative check:

Feasibility studies and requirements workshops habitually gather output mockups, input layouts, and control requirements together.

Why Other Options Are Wrong:

Focusing on only one area creates gaps (e.g., secure inputs but useless outputs).

“None” contradicts standard practice.

Common Pitfalls:

Postponing controls to later phases; security and audit need early design inputs.

Final Answer:

All of the above