Which one of the following is the second step in System Analysis?

In a typical, sequential System Development Life Cycle (SDLC) model, the process begins with a preliminary investigation or problem identification (Step 1). The logical subsequent step is the Feasibility Study (Step 2). This study is a critical checkpoint that evaluates the project's viability based on technical, economic, legal, operational, and scheduling (TELOS) factors. It is conducted before committing significant resources to detailed requirements gathering and system design to determine if the project should proceed. Therefore, it is considered the second major step in the overall system analysis and development process.

B. Select an alternative: This action occurs later in the analysis or early design phase, after requirements are understood and several potential solutions have been proposed and evaluated.

C. Recommendation Review: This is a concluding step of the analysis phase, where the system analyst presents their findings and proposed solution to stakeholders for approval.

D. Analysis and Design: This option is too broad as it combines two distinct, major phases of the SDLC, rather than representing a single, sequential step.

1. Valacich, J. S., George, J. F., & Hoffer, J. A. (2015). Essentials of systems analysis and design (6th ed.). Pearson. In Chapter 2, "Initiating and Planning Systems Development Projects," the authors detail the assessment of project feasibility (pp. 39-42). This activity follows the initial project identification (covered in the same chapter) and precedes the detailed analysis phase of determining requirements (Chapter 3), establishing its position as a critical early-stage activity.

2. Whitten, J. L., & Bentley, L. D. (2007). Systems Analysis and Design Methods (7th ed.). McGraw-Hill/Irwin. The textbook outlines the initial phases of a project, starting with project initiation and planning. The feasibility analysis is presented as a core component of this initial planning phase (Chapter 3, "Systems Analysis"), which must be completed before moving to the detailed analysis of system requirements. This confirms its role as a foundational step following problem identification.