FEASIBILITY

ANALYSIS

WEEK 2
FEASIBILITY ANALYSIS
A feasibility study, or feasibility analysis, assesses the viability of the project idea
from different perspectives. Its goal is to help top managers narrow down alternatives
and make informed go/no-go decisions.

ensures the analysis of every small aspect of the feasibility of the proposed
software or project.
help you analyze for multiple purposes to understand whether the software will
be able to withstand the market or not.
helps developers understand the product in the right terms from the point of view
of development, implantation, the contribution of the project to the organization.

mtbl
FEASIBILITY ANALYSIS
For example, Cedric wants to launch a new home decor business. So, he evaluates factors like
potential profitability, effect on the environment, legal requirements, etc. It is his feasibility study,
and based on the findings, he can decide whether or not to move forward with the project.

wants to open HOME

CEDRIC DECOR
SET-UP

so he performs

FEASIBILITY STUDY

BASIS PROFITABILITY ENVIRONTMENT LEGAL

results If Cedric got a
legal approval, he
Can generate good No harm to the Needs regulatory
ANALYSIS can go ahead with
profit? environtment approval
the start-up; else
it is not feasible.
OUTCOME Suitable Suitable Unsuitable
mtbl
 FIVE KEY AREAS TO BE COVERED IN AN
OVERALL FEASIBILITY STUDY

TELOS FRAMEWORK
T E L
TECHNICAL FEASIBILITY ECONOMIC FEASIBILITY LEGAL FEASIBILITY
Is the project technically How can legal limitation affect
Does it make financial sense?
possible? the problem?

O S
OPERATIONAL FEASIBILITY SCHEDULING FEASIBILITY
How hard is it to maintain and Can we keep up on realistic
manage the project? deadline?

mtbl
 TECHNICAL FEASIBILITY
Technical feasibility inspects whether software can be built at all with available tools
and experts. In software engineering, technical feasibility (TF) is the most time-
consuming and complex part of the full feasibility analysis.
Generate
ideas
Feasibility is assessed at the ideation phase of product development, after gathering
early project requirements — namely
Lorem ipsum dolor sit
amet, consectetur
adipiscing elit, sed do

functional requirements, captured by business analysts and describing features of

eiusmod tempor
incididunt

the solution; and

non-functional requirements, usually collected by a software architect and related
to the properties of the system — like performance, scalability, and so on.

mtbl
DIFFERENCE BETWEEN FUNCTIONAL AND NON-
FUNCTIONAL REQUIREMENTS:

FUNCTIONAL NON-FUNCTIONAL

They define a system or its component. They define the quality attribute of a system

It specifies, “How should the system fulfill the

It specifies, “What the system should do?”
functional requirements?”

Non-functional requirement is specified by

User specifies functional requirement. technical peoples e.g. Architect, Technical
leaders and software developers.

mtbl
DIFFERENCE BETWEEN FUNCTIONAL AND NON-
FUNCTIONAL REQUIREMENTS:

FUNCTIONAL NON-FUNCTIONAL

It is not mandatory to meet these

It is mandatory to meet these requirements.
requirements.

It is captured in use case. It is captured as a quality attribute.

Defined at a component level. Applied to a whole system.

mtbl
DIFFERENCE BETWEEN FUNCTIONAL AND NON-
FUNCTIONAL REQUIREMENTS:

FUNCTIONAL NON-FUNCTIONAL

Helps you to verify the functionality of the Helps you to verify the performance of the
software. software.

Non-Functional Testing like Performance,

Functional Testing like System, Integration,
Stress, Usability, Security testing, etc are
End to End, API testing, etc are done.
done.

Usually easy to define. Usually more difficult to define.

mtbl
EXAMPLES OF FUNCTIONAL AND NON-
FUNCTIONAL REQUIREMENTS:

mtbl
 ECONOMIC FEASIBILITY
Economic feasibility determines if a project can make enough money to be
worthwhile. It looks at the project’s costs and compares them to potential profits to
see if they are suitable investments. It’s about figuring out whether a project will
Generate
succeed financially. ideas

Economic feasibility in terms of software development helps companies to examine

Lorem ipsum dolor sit
the development costs and adipiscing
financial
amet, consectetur gains.
elit, sed do
eiusmod tempor
incididunt

mtbl
 LEGAL FEASIBILITY
A part of the legal feasibility study includes examining legal requirements, such as
contracts, data protection, and copyright infringement. Unbeknownst to the technical
staff, there could be a host of legal traps. Subsequently, a business entity could face
Generate
expensive litigation if these are not checked and anticipated.
ideas

Laws and regulations control the activities of commercial

Lorem ipsum dolor sit

enterprises. Thus, legal adipiscing

feasibility is an essential factor in
amet, consectetur
elit, sed do
eiusmod tempor
software development projects. Take online trading, for instance.
incididunt

Some countries outlaw online gambling and lotteries. Therefore, it

would be illegal to develop betting software in such regions. In
short, software development projects that breach the law are
legally not feasible.
mtbl
 OPERATIONAL FEASIBILITY
Operational feasibility analyzes the level of service delivery according to requirements
and the ease of operating and maintaining the product after deployment. Along with
these other operational areas, it determines the product’s usability, whether the
Generate
software development team’s decisions for the proposedideas solution are acceptable, and
so on.

Determine if the expected issue in the user request is a high priority.

Determine if the organization is satisfied with alternative solutions
proposed by the software development team.
Determine if the solution proposed by the software development team is
acceptable.
Analyze whether users are comfortable with new software.

mtbl
 SCHEDULING FEASIBILITY
Scheduling feasibility is a type of feasibility that helps you to set realistic deadlines
and adhere to them. A thorough feasibility study cannot be conducted without
extensive knowledge of finance, technology, and legislation.
Generate
ideas
In Schedule Feasibility Study mainly timelines/deadlines is analyzed for
proposed project which includes how many times teams will take to
complete final project which has a great impact on the organization as
purpose of project may fail if it can’t be completed on time.

mtbl
 STEPS FOLLOWED IN A SOFTWARE
DEVELOPMENT FEASIBILITY STUDY

01 Assessment

A system overview is the first step in the assessment phase. It states the company
name, system title, category, and operational extent. The software development team
determines whether the new system will achieve an organization’s objectives. It also
states whether the existing system upgrades are viable or not.
Examples of guiding questions are:

Does implementing the new system require new technology?

The scope of work, and is it within the system development budget?
Answers to these and other questions are all aspects of the assessment phase.
mtbl
mtbl
 STEPS FOLLOWED IN A SOFTWARE
DEVELOPMENT FEASIBILITY STUDY

02 Gathering Information

In this phase, the team collects views and ideas from users. They must concisely
define and document the user requirements. Failure to nail this step often results in a
faulty end product. In addition, the requirements should drill down to different user
levels.
Typically, the software development team will interview end users inside an
organization. They will also request that external users, i.e., customers and suppliers,
share feedback. On the other hand, if an organization is modifying its existing
systems, the team will review the documentation.
mtbl
 STEPS FOLLOWED IN A SOFTWARE
DEVELOPMENT FEASIBILITY STUDY

03 Drafting a Feasibility Study Report

It contains findings and recommendations. The report states whether the company
should develop new software or improve the existing system. The software review
team highlights budgetary changes and an estimated work completion schedule.

Also in the report are references to documents reviewed and definitions of terms
used, including abbreviations and acronyms. Risks and delays that may be
encountered during implementation also form part of the report’s contents.

mtbl
 STEPS FOLLOWED IN A SOFTWARE
DEVELOPMENT FEASIBILITY STUDY

04 Requirements Analysis

Once a study returns a feasible verdict, the client gives the go-ahead. The first step is
to conduct a systems analysis. At this point, analysts determine the bones and flesh of
the new system.
What inputs will it need? What output shall it generate? Will it need paper forms and
external files? Answers to these and other queries go into a requirements document.
This document is called a Software Requirement Specification (SRS). It contains:

Details of the problem Software system requirements

Alternative solutions System constraints
mtbl
 STEPS FOLLOWED IN A SOFTWARE
DEVELOPMENT FEASIBILITY STUDY

05 Systems Specification

It contains detailed instructions, file definitions, flowcharts, and other diagrams.

Along the way, analysts and system users engage in brainstorming sessions. The two
teams meet regularly as the project progresses. In this phase, also called the design
phase, software engineers transform the SRS document into a software architecture.

mtbl
 STEPS FOLLOWED IN A SOFTWARE
DEVELOPMENT FEASIBILITY STUDY

06 Programming

Upon verifying and checking that the system’s specification is accurate and verified,
programmers take over. They write and test the software codes. Numerous tests get
underway using automated tools and quality assurance checks. Module testing also
takes place at this stage. It follows a structured approach, defining a test plan,
testing criteria, and managing test cases. Debugging takes place in this stage too.

mtbl
 STEPS FOLLOWED IN A SOFTWARE
DEVELOPMENT FEASIBILITY STUDY

07 Production

After testing the system thoroughly, production or changeover takes place. End-users
undergo thorough training. The system development team stays on alert to respond to
queries and correct various errors that crop up. A system at this stage takes several
weeks before reaching stability.

mtbl
 STEPS FOLLOWED IN A SOFTWARE
DEVELOPMENT FEASIBILITY STUDY

08 Evaluation

Once the system stabilizes, an evaluation of its correctness gets underway. There is an entire list of things that
need correcting. Besides, the team must also contend with unanticipated issues. Further, the integration of
software modules takes place in this phase.
The software development engineers test each module before adding the next one and
testing again. It is an incremental process. The team seeks to ascertain whether the
software conforms to the SRS document’s requirements. Once all modules were in place,
they tested the system as a fully developed product. There are three system testing
phases: Alpha, Beta, and Acceptance. Alpha testing is done at the software developer’s
site. Beta testing targets customers, while the client does Acceptance testing.
mtbl
 STEPS FOLLOWED IN A SOFTWARE
DEVELOPMENT FEASIBILITY STUDY

09 Implementation

After months of designing, training, and stabilizing a system, the next phase is implementing it.
Programmers have already tested the software and are confident that it meets the
organization’s requirements. Implementation of feasibility studies in software engineering
takes place in two phases. In the first phase, the client gets a trial version of the software as
an experiment to determine whether any changes are needed. Users are encouraged to share
feedback on the system’s operation.
The complete system is delivered to the client during the second implementation phase. Even
more importantly, the system must be secure. Note, a system delivery could replace a manual
system, a new system, or a modification.
mtbl
 STEPS FOLLOWED IN A SOFTWARE
DEVELOPMENT FEASIBILITY STUDY

10 Maintenance

Software maintenance is a critical stage in the system development life cycle. Even
though maintenance is a rewarding experience, it can also be time-consuming. Types
of maintenance carried out are corrective, adaptive, perfective, and preventive.

Corrective: Involves correcting past problems or repairing current performance failures.

Adaptive: Changing the system so that it is in sync with the external environment, e.g., changes in
taxation.
Perfective: Enhancement or modification to match changing needs.
Preventive: This is the maintenance process to prevent the system from becoming obsolete.

mtbl
THANK YOU
FOR LISTENING!

mtbl