Feasibility studies

For all new systems, the requirements engineering process should start with a feasibility
study. The input to the feasibility study is a set of preliminary business requirements,
an outline description of the system and how the system is intended to supportbusiness processes. The results of the feasibility study should be a report that recommends
whether or not it is worth carrying on with the requirements engineering
and system development process.
A feasibility study is a short, focused study that aims to answer a number of
questionh:
I. Doe:; the system contribute to the overall objectives of the organisation?
2. Can the system be implemented using (:urrent technology and within given cost
and schedule constraints?
3. Can the system be integrated with other systems which are already in place?
The issue of whether or not the system (:ontribut,es to business objectives is critical.
If a system does not support these objectives, it has no real value to the business.
While this may seem obvious, many organisaljons develop systems which do
not contribute to their objectives because they don't have a clear statement of these
objectives, because they fail to define the business requirements for the system or
because other political or organisat:lOn factors influence the system procurement.
Although this is not discussed explicitly, a feasibility study should be part of the
Inception phase in the Rational Unified Process, as discussed in Chapter 4.
Carrying out a feasibility study involves information assessment, information collection
and report writing. The infonnation assessment phase identifies the information
that is required to answer the three questions set out above. Once the
infonnation has been identified, you should talk with infonnation sources to discover
the answers to these questions. Some examples of possible questions that may
be put are:
I. How would the organisation cope if this system were not implemented?
2. What are the problems with current processes and how would a new system
help alleviate these problems?
3. What direct contribution will the system make to the business objectives and
reqUl rements?
4. Can information be transferred to and from other organisational systems?
5. Does the system require technology that has not previously been used in the
organisation?
6. What must be supported by the system and what need not be supported?
In a feasibility study, you may consult information sources such as the managers
of the departments where the system will be used, software engineers who are familiar
with the type of system that is proposed, technology experts and end-users of
the system. Normally, you should try to complete a feasibility study in two or three
weeks.Once you have the information, you write the feasibility study report. You should
make a recommendation about whether or not the system development should continue.
In the report, you may propose changes to the scope, budget and schedule of
the system and suggest further high-level requirements for the system.