0% found this document useful (0 votes)
20 views4 pages

Feasibility Study Essentials in IT Systems

The document discusses the six categories of feasibility for systems analysis projects: economic, technical, operational, schedule, legal/contractual, and political. It also defines common cost-benefit analysis techniques like net present value, return on investment, and break-even analysis. The document distinguishes between a statement of work and baseline project plan. It defines tangible and intangible benefits and costs as well as one-time and recurring benefits and costs. Matching questions are provided to test understanding of the concepts.

Uploaded by

Keanu Reevs
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views4 pages

Feasibility Study Essentials in IT Systems

The document discusses the six categories of feasibility for systems analysis projects: economic, technical, operational, schedule, legal/contractual, and political. It also defines common cost-benefit analysis techniques like net present value, return on investment, and break-even analysis. The document distinguishes between a statement of work and baseline project plan. It defines tangible and intangible benefits and costs as well as one-time and recurring benefits and costs. Matching questions are provided to test understanding of the concepts.

Uploaded by

Keanu Reevs
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Systems Analysis and Design 

ITC 240 TUTORIAL 5

Essay Questions
1. Briefly identify and define the six major categories of feasibility.

1. Economic Feasibility: tries to figure out what the project's financial advantages and
expenses are.
2. Technical Feasibility: seeks to determine if the organization is capable of developing the
new system.
3. Operational Feasibility: examines the degree of likelihood that the candidate system will be
able to solve the business problem or take advantage of opportunities.
4. Schedule Feasibility: examines the likelihood that all potential time frame and completion
date schedules can be met.
5. Legal and Contractual Feasibility: tries to assess the potential legal ramifications due to the
construction of the new system
6. Political Feasibility: determining stakeholder’s views of the candidate system is the intent of
political feasibility

2. Briefly identify three commonly used economic cost-benefit analysis techniques.

1. Net Present Value (NPV): NPV uses a discount rate determined from the company’s cost of
capital to establish the present value of a project. The discount rate is used to determine the
present value of both cash receipts and outlays.
2. Return on Investment (ROI): ROI is the ratio of the net cash receipts of the project divided
by the cash outlays of the project. Trade-off analysis can be made among projects competing
for investment by comparing their representative ROI ratios.
3. Break-Even Analysis (BEA): BEA finds the amount of time required for the cumulative
cash flow from a project to equal its initial and ongoing investment.

3. What is a Statement of Work and Baseline Project Plan? How are they different?
Baseline Project Plan (BPP) A major outcome and deliverable from the project initiation and
planning phase that contains the best estimate of a project’s scope, benefits, costs, risks, and resource
requirements
Statement of Work (SOW) Effectively, it defines the specific goals for a project; what needs to be
delivered, and the performance criteria. This is often confused with the scope of work as they’re both
abbreviated to SOW. With the scope of work, you’re looking at all the specific tasks that a particular
project manager has to perform to reach all the objectives. While both are important, the statement of
work is the more critical of the two.
SOW is a document represent a contract between the information system staff and consumer for
estimating time for system development project, but the BPP is a document intended to guide the
project development team and it mainly contains: - Introduction. - Project Description. - Assessment
and Feasibility.
Systems Analysis and Design ITC 240 TUTORIAL 5

4. Describe the differences between tangible and intangible benefits and costs, and between one-time
and recurring benefits and costs.

Tangible benefit: A benefit derived from the creation of an information system that can be measured
in dollars and with certainty.
Intangible benefit: A benefit derived from the creation of an information system that cannot be easily
measured in dollars or with certainty.

So in short, tangible benefits can be measured in dollars or monetary value and is certain but
intangible benefits cannot be measured in dollars or monetary value and is uncertain.

Tangible cost: A cost associated with an information system that can be measured in dollars or with
certainty.
Intangible cost: A cost associated with an information system that cannot be easily measured in terms
of dollars or with certainty.

The same way with tangible and intangible benefits, tangible costs can be measured in dollars or
monetary value and is certain but intangible costs cannot be measured in dollars or monetary value and
is uncertain.

One-time cost: A cost associated with project start-up and development or system start-up.
Recurring cost: A cost resulting from the ongoing evolution and use of a system.

So in short, one-time cost occurs only once when the system starts up but recurring cost can occur
multiple times usually in a year-round or month round or whatever the system evolution lifecycle is.

Matching Questions
Match each of the following terms with its definition.
a. economic feasibility
b. legal and contractual feasibility
c. operational feasibility
d. political feasibility
e. schedule feasibility
f. technical feasibility

1. A process of identifying the financial benefits and costs associated with a development project.
Economic Feasibility

2. The process of assessing the degree to which the potential time frame and completion dates for all
major activities within a project meet organizational deadlines and constraints for affecting change.
Schedule Feasibility

3. The process of evaluating how key stakeholders within the organization view the proposed system.
Political Feasibility

4. The process of assessing the degree to which a proposed system solves business problems or takes
advantage of business opportunities.
Operational Feasibility
Systems Analysis and Design ITC 240 TUTORIAL 5

5. The process of assessing potential legal and contractual ramifications due to the construction of a
system.
Legal and Contractual Feasibility

6. A process of assessing the development organization’s ability to construct a proposed system.


Technical feasibility

Match each of the following terms with its definition.


a. tangible cost
b. intangible cost
c. one-time cost
d. recurring cost
e. tangible benefit
f. tangible cost

1. A cost associated with an information system that can be measured in dollars and with certainty.
Tangible cost

2. A benefit derived from the creation of an information system that can be measured in dollars and with
certainty.
Tangible benefit

3. A cost resulting from the ongoing evolution and use of a system.


Recurring cost

4. A cost associated with project startup and development, or system startup.


One-time cost

5. A cost associated with an information system that cannot be easily measured in terms of dollars or
with certainty.
Intangible cost

6. A benefit derived from the creation of an information system that cannot be easily measured in dollars
or with certainty.
Intangible benefit

Match each of the following feasibility criteria with its purpose.


a. economic
b. legal and contractual
c. operational
d. political
e. schedule
f. technical
Systems Analysis and Design ITC 240 TUTORIAL 5

1. To gain an understanding of the degree to which the proposed system will likely solve the business
problems or take advantage of the opportunities outlined in the systems service request or project
identification study.
Operational

2. To gain an understanding of the organization’s ability to construct the proposed system.


Technical

3. To provide an understanding of any potential legal ramifications due to the construction of the system.
Legal and contractual

4. To evaluate how key stakeholders within the organization view the proposed system.
Political

5. To provide an understanding of the likelihood that all potential time frames and completion date
schedules can be met, and that meeting these dates will be sufficient for dealing with the needs of the
organization.
Schedule

6. To identify the financial benefits and costs associated with the development project.
Economic

Common questions

Powered by AI

One-time costs are associated with project start-up, development, or system launch and occur only once, like initial investments in infrastructure or software . Recurring costs arise from the ongoing use and evolution of a system, including maintenance, operation, and support costs . Distinguishing between these costs is crucial for accurate budgeting and financial forecasting, as it impacts long-term financial commitments and resource allocation for system sustainability.

Tangible costs and benefits are those that can be measured in monetary terms with certainty, such as initial investment costs or expected revenue increases from an information system . These quantifiable factors are often used in cost-benefit analysis to evaluate the financial viability of a project. Intangible costs and benefits, such as employee satisfaction or improved decision-making, cannot be easily measured in dollars and with certainty . While intangible factors may not be directly quantified, they can greatly influence decision-making by impacting long-term strategic goals and stakeholder satisfaction. These considerations often require qualitative assessments alongside financial analyses to provide a more comprehensive evaluation of a project's potential impact.

Technical feasibility evaluates whether the development organization has the capability to build the proposed system, including the technological resources and expertise required . Failure to properly assess technical feasibility can result in a project that is technically unviable, leading to unexpected technical challenges, system failures, or the inability to meet performance requirements. This oversight can cause cost overruns, project delays, and ultimately, failure to deliver a system that meets business needs, thereby risking stakeholder disapproval and wasting organizational resources.

A Statement of Work (SOW) is a document that defines the specific goals for a project, including deliverables and performance criteria, effectively representing a contract between the information system staff and the consumer . In contrast, a Baseline Project Plan (BPP) is a deliverable from the project initiation and planning phase that provides the best estimate of the project's scope, benefits, costs, risks, and resource requirements . While the SOW focuses on specific tasks and objectives, the BPP serves as a guiding document for the development team, outlining the project's broader framework and feasibility assessments.

Operational feasibility examines whether a candidate system can likely address business problems or capitalize on opportunities outlined in the project scope . It evaluates practical aspects such as user acceptance, organizational compatibility, and potential changes to business processes. A system with high operational feasibility is more likely to be effectively implemented and used, as it aligns well with existing workflows and stakeholder expectations. Therefore, it significantly influences the probability of achieving intended business outcomes.

The primary economic cost-benefit analysis techniques are Net Present Value (NPV), Return on Investment (ROI), and Break-Even Analysis (BEA). NPV uses a discount rate to determine the present value of cash receipts and outlays, helping organizations assess the financial viability of a project . ROI measures the ratio of net cash receipts to cash outlays, facilitating comparisons among competing projects . BEA calculates the time required for cumulative project cash flow to cover initial and ongoing investments, aiding organizations in understanding the project's payback period .

Legal and contractual feasibility evaluates potential legal ramifications of developing a new system, including compliance with laws, contracts, and regulatory standards . Overlooking this aspect can lead to legal disputes, fines, and project delays. It may also result in violations of data protection laws, intellectual property issues, or breaches of contract terms, significantly affecting the project's credibility and financial health. Therefore, ensuring legal and contractual feasibility is crucial to mitigate risks associated with legal liabilities.

Schedule feasibility assesses the likelihood that a project's timeline and deadlines can be met, which is crucial for aligning the project's deliverables with strategic and operational needs . Inaccurate schedule projections can lead to significant project setbacks, including cost overruns, resource allocation issues, and missed opportunities. Delays could disrupt business operations, reduce competitive advantage, and diminish stakeholder confidence. Hence, accurately evaluating schedule feasibility is vital for project success and organizational alignment.

Political feasibility assesses how stakeholders within an organization view a proposed information system, focusing on their interests and potential resistance . Successful implementation depends on securing stakeholder support, as political resistance can lead to project delays, increased costs, or even failure. By engaging stakeholders early and addressing their concerns, organizations can enhance political feasibility, smoothing the path for project approval and acceptance.

Tangible benefits, measured in monetary value and certainty, provide a direct indicator of an information system's effectiveness by showing quantifiable gains such as cost savings or increased revenue . They offer concrete data that managers can use to justify investments and assess project outcomes. By demonstrating financial returns, tangible benefits can influence managerial decision-making, guiding resource allocation, and priority setting. These tangible metrics help build a business case for systems investment.

You might also like