F451 - Feasibility study

A report to identify the possible solutions to the problem and how 'possible they are.

Economic or technical feasibility of the new system.

A typical feasibility study would look at the following options:

• Should we: Stick with the old system? Adapt the old system? Create a new computerised system?
• Should we: Buy an off-the-shelf package? Employ a programmer to create bespoke software? Write it in-house?

Technical:

Is the HW/SW available to solve this problem?

Economic:

Is the proposed solution cost effective?

Social:

Impact on jobs, skills, training of staff.

Analysis:

• In depth study of the problem.
• Flow charts.
• DFDs (Data Flow Diagram).
• Inputs & Outputs.
• End User Requirements (signed off document).

Importance of Analysis:

Problem must be accurate.

User may not understand potential of computer systems.

Developer not likely to understand the industry which the user is working in.

Developer must produce a solution that meets the users' specifications.

Clear communication between user and developer.

Data Flow Diagram:
A way of showing how data moves around a system.

It is not concerned with how the system processes the data - it just shows the flows.

It uses four symbols.