| |
Feasibility Study Phase will commence after the project request phase
to assess the feasibility of providing an IT solution for the request and to quantify the requirements,
scope, costs, benefits and other implications of the proposed solution. The findings and recommendations
should be documented in a Feasibility Study report, which comprises two parts -
Management Summary and
Technical Specification
with the following coverage:
Feasibility Study Management Summary
| A. |
Approval Sought |
Highlight the major recommendations of the Feasibility Study.
|
| B. |
System Objectives |
State study objectives and intended usage of the proposed system. |
| C. |
Background |
Describe the background picture and other relevant information of
the proposed system.
|
| D. |
Present Situation |
Describe briefly the current operations, environment and
functions of the system under study
|
| E. |
Problem/Improvement Areas |
Describe the problems encountered or anticipated and improvement
areas identified.
|
| F. |
Proposed System |
Describe in high level terms the proposed system and define the
scope of the subsequent SA&D study.
|
| G. |
Resource Implications |
Estimate the resource requirements and other implications of the
proposed system.
|
| H. |
Costs |
Estimate the non-recurrent and recurrent costs of the proposed
system.
|
| I. |
Benefits |
Estimate the tangible and intangible benefits of the proposed
system. Realisable benefits, such as reduction in expenditures, increases in revenue, and staff
savings resulting from deletion of posts, should be expressed in financial terms. Where notional
or intangible benefits are quoted, the study should include appropriate productivity and performance
indicators for measuring these improvements subsequently.
|
| J. |
Cost-benefits Analysis |
Evaluate the cost effectiveness of the proposed system with
indications of the funding requirements and timing for realisation of the identified benefits.
|
| K. |
Implementation Plan |
Schedule an implementation plan which should be in the format
of the project technical plan in PRINCE with proper staging be considered.
|
| L. |
Recommendations |
Make study recommendations and propose the way forward.
|
Feasibility
Study Technical Specification
| 1. |
Current Environment Description |
- Describe current operations and environment;
- Describe current functions and data
|
| 2. |
Project Definition |
Describe the user requirements; Describe the proposed system, in
terms of its functions, data, workload and user impact; Describe the implementation approach
and, if any, development strategy; Define the implementation plan and
its cost/resource implications with detailed backing
information (e.g. Function Point calculation, sizing,
etc)
|
|
|