Feasibility Analysis, System Requirements and Systems Request

Development of a Payroll system for a store that didn't have the system never.

• Problem Statement:

The current payroll system at Park Cafe is outdated and inefficient. The problem that

we face is that we might be losing data and important documents by only keeping

paper documents. Without some of this information we will not be able to fill our

taxes correctly or be able to cooperate with other departments to the best of our

ability.

Needed parts of the project:

- Systems Request:

A document that describes the reasons for and the value added from building a

new system

- Contains 5 elements:

o Project sponsor: the primary point of contact for the project

o Business need: the reason prompting the project

o Business requirements: what the system will do

o Business value: how will the organization benefit from the project

o Special issues: Anything else that should be considered

- Feasibility Analysis.

Is this project feasible?

o What are the risks?

o Can these risks be overcome?

Major components:

o Technical feasibility (Can we build it?)

Identify risks in the following areas:

The functional area: Are analysts familiar with this portion of the

business?

The technology: Less familiarity generates more risk

Project size: Large projects have more risk

Compatibility: Difficult integration increases the risk

Economic feasibility (Should we build it?)

o Identify the costs and the benefits

o Assign values to the costs and benefits

o Determine the cash flow

o Determine the value using one or more methods:

o Net present value (NPV)

o Return on investment (ROI)

o Break-even point

Organizational feasibility (Will they use it?)

— Will the users accept the system?

— Is the project strategically aligned with the business?

— Conduct a stakeholder analysis

— Project champion(s)

— Organizational management

— System users

— Others

- System Requirements.

A statement of what the system must do or a characteristic it must have

Will later evolve into a technical description of how the system will be implemented

o Functional: relates to a process or data

o Non-functional: relates to performance or usability