UNIT 1: FEASIBILITY STUDY

---

1. What is a Feasibility Study?

Definition

A Feasibility Study is an evaluation or analysis of the potential impact of a proposed project or system. It is conducted early in the System Development Life Cycle (SDLC) to determine if a project is legally, technically, and economically justifiable.

The primary goal of a feasibility study is to answer the question: "Is this project worth the investment, and can it be successfully completed?"

---

2. Importance of Feasibility Study

Before committing significant time, money, and resources to developing a new system, it is crucial to conduct a feasibility study.

• Risk Mitigation: It helps identify potential bottlenecks and reasons not to proceed before massive investments are made.
• Cost-Benefit Clarification: It clarifies whether the financial benefits will actually outweigh the development and maintenance costs.
• Resource Allocation: It helps management decide where to allocate limited resources effectively.
• Alternative Evaluation: It often provides multiple alternative solutions, allowing the organization to pick the most efficient path.

---

3. Types of Feasibility (TELOS Framework)

A comprehensive feasibility study usually evaluates five main areas, easily remembered by the acronym TELOS: Technical, Economic, Legal, Operational, and Schedule.

---

1. Technical Feasibility

This assessment focuses on the technical resources available to the organization. It answers the question: "Do we have the technology and skills to build this?"

• Hardware and Software: Does the current infrastructure support the proposed system, or do new servers/software licenses need to be purchased?
• Technical Expertise: Does the internal development team have the necessary skills (e.g., knowledge of specific programming languages or cloud architectures) to build and maintain the system?
• Technology Maturity: Is the technology required to build the system mature and stable, or is it highly experimental and risky?

---

2. Economic Feasibility

Also known as Cost-Benefit Analysis (CBA), this is often the most critical aspect for management. It answers the question: "Will this system provide a good return on investment?"

• Cost Identification: Identifying all costs involved, including tangible costs (hardware, developer salaries) and intangible costs (initial drop in employee productivity during the learning curve).
• Benefit Identification: Identifying financial gains, such as direct revenue increases, cost savings (e.g., fewer paper supplies needed), and intangible benefits (e.g., improved customer goodwill).
• Metrics Used: Break-even analysis, Return on Investment (ROI), and Net Present Value (NPV).

---

3. Legal Feasibility

This assessment ensures that the proposed system does not conflict with any legal requirements. It answers: "Is this project legally permissible?"

• Data Privacy: Does the system comply with regulations like GDPR or HIPAA?
• Intellectual Property: Does the system infringe on any existing copyrights or patents?
• Contracts: Does the new system violate any existing vendor contracts or organizational agreements?

---

4. Operational Feasibility

This measures how well the proposed system solves the problems and if it will actually be used by the staff. It answers: "Will the users accept and use the system?"

• User Acceptance: Is there strong resistance to change among the employees? Will the new system disrupt the organizational culture significantly?
• Management Support: Does management fully support the implementation of the new system?
• Usability: Does the system align with the way users currently prefer to work, or does it force an unnatural workflow?

---

5. Schedule Feasibility

A project might be technically and economically viable but impossible to complete within the required timeframe. It answers: "Can we build it in time?"

• Deadlines: Are there hard statutory deadlines (e.g., a new tax calculation system must be live by January 1st)?
• Resource Availability: Are the developers available immediately, or are they tied up in other projects?

---

4. The Feasibility Report

At the conclusion of the study, a formal document called a Feasibility Report is presented to management or project sponsors.

A typical report includes:

1. Executive Summary: A brief overview of the findings.
2. Problem Description: Why the new system is needed.
3. Alternative Solutions: 2-3 different approaches to solving the problem (e.g., custom build vs. buying off-the-shelf software).
4. Cost-Benefit Analysis: The financial breakdown of each alternative.
5. Final Recommendation: A clear cut "Go" or "No-Go" decision on whether to proceed to the next SDLC phase.

---

5. Conclusion

A feasibility study is a vital checkpoint in system analysis. It acts as a safety valve, preventing organizations from wasting millions of dollars and years of effort on projects that are destined to fail due to technical limits, poor user adoption, or lack of financial return.

---

Practice MCQs – Feasibility Study

🎯 Start Practice MCQ Quiz →