An important role of the systems analyst is the feasibility study. A feasibility study is simply the analysis and evaluation of what a project can potentially deliver and if it’s financially worthwhile. The study tends to be based on in depth research of of the proposal. The aim is to determine quickly,at a reasonable cost, if the problem can be solved and if it is worth solving. Minor bugs may not be worth the investment to be solved. On the other hand technological constraints may prevent the solution of more major difficulties and are unfortunately,unachievable. There is quite a degree of skill involved in conducting feasibility studies. An analyst cannot compromise quality over cost or vice versa. Lack of a feasibility study will result in disaster and will either end up wasting company funds or not solve the problem at all. It is a major risk to not undertake a feasibility study
Developing a new system is like an investment. As with any investment there is a risk of failure. Therefore in terms of an IS it makes sense to investigate the likelihood of success. The success of any system depends on the skill of the analyst involved and that success is easier to determine with a thorough feasibility study. The point of the feasibility study is to determine, at a reasonable cost, if the problem is worth solving. Thus the cost of the feasibility study should represent a tiny fraction of the estimated cost of developing and implementing the system,generally less than ten percent of the scope. Assuming that a feasible solution exists, the analyst must prepare a feasibility study report that identifies several alternatives and recommends a course of action. A good systems analyst should be able to come up with several solutions to any problem that presents itself.