The organization often wants a proposed system to alleviate problems that the client BELIEVES exist in the current

situation

The
Is

current system

too slow Contains errors Costs too much Stores redundant data Is disliked or not used by users and/or customers Doesnt supply the information or functions that the client wants

1 Problems of Data Capture 2 Problems of Data Storage 3 Problems of Data Processing 4 Problems in the Distribution and Access to Data and Information 5 Problems in the Presentation of Information Any technological solution for organizations should be aligned to its processes and usable by its people

Software Database Software Database Network

Software Process People

of more clerks that results to higher cost and longer elapsed time per transaction because of a manual system Customers complain about long lines and sometimes leave without completing the transaction Delays occur when several clerks perform the same transaction at the same time
Requirement

are common especially in computational transactions Validity and correctness of data and information are not effectively verified or not verified at all Customers do not receive immediate feedback regarding unsettled and faulty transactions
Mistakes

 The

company does not take advantage of direct mail marketing in order to increase revenues Data and information summaries and reports are costly to prepare and of questionable accuracy

business functions are supported by the system? What strategic objectives and business requirements must be supported by the new system? What are the benefits of the proposed system? What transactions will the system process?
What

information do users and managers need from the system? What procedures could be eliminated by Business Process Reengineering? What security issues exist? What risks are acceptable? What budget and timetable constraints will affect the system development?
What

There is a difference between asking what is being done and what could or should be done

The systems analyst first must understand the current situation

WHO?

WHAT?

WHERE?

WHEN?

HOW?

WHO?

WHAT?

WHERE?

WHEN?

HOW?

WHO?

WHAT?

WHERE?

WHEN?

HOW?

Who performs each of the

procedures within the system? Why?

Are the correct people performing

the activity?

Could other people perform the

tasks more effectively?

WHO?

WHAT?

WHERE?

WHEN?

HOW?

What is being done? What procedures are being followed? Why is that process necessary?

WHO?

WHAT?

WHERE?

WHEN?

HOW?

Where are operations being

performed? Why?

Where could they be performed? Could they be performed elsewhere?

WHO?

WHAT?

WHERE?

WHEN?

HOW?

When is a procedure performed? Why is it being performed at this

time? Is this the best time?

WHO?

WHAT?

WHERE?

WHEN?

HOW?

How is a procedure performed? Why is it performed in that manner? Could it be performed better, more
efficiently or less expensively in some other manner?

CURRENT SYSTEM
Who does it? Why does this person do it? What is done? Why is it done? Where is it done? Why is it done there? When is it done? Why is it done then? How is it done? Why is it done this way?

PROPOSED SYSTEM Who should do it? What should be done? Where should it be done? When should it be done? How should it be done?

the existing situation Identify improvements in the current system Define requirements for the new system
Understand

 The

system may cost more than projected The system may be delivered later than promised The system may not meet the users expectations and that dissatisfaction may cause them not to use it

in production, the costs of maintaining and enhancing the system may be excessively high The system may be unreliable and prone to errors and downtime
Once

 The

reputation of the IT staff on the team is tarnished because any failure, regardless of who is at fault, will be perceived as a mistake by the team

Consistent The

requirements are not conflicting or ambiguous requirements describe all possible system inputs and responses requirements can be satisfied based on the available resources and constraints

Complete The

Feasible The

 Required

The requirements are truly needed and fulfill the purpose of the system The requirements are stated correctly The requirements directly map to the functions and features of the system

Accurate

Traceable

 Verifiable

The requirements are defined so they can be demonstrated during testing

the organization in determining whether to proceed with a project or not Identifies the important risks associated with the project that must be addressed if the project is approved
Guides

 Is

it a practical approach that will solve a problem or take advantage of an opportunity to achieve company goals? Are the necessary technical resources and people available for the project?

 Is

the problem worth solving, and will the request result in a sound business investment? Can the proposal be accomplished within an acceptable time frame?

Operational Feasibility Technical Feasibility Schedule Feasibility Economic Feasibility

that the proposed system will be used effectively after it has been developed A measure of the users attitude towards the system and how well the solution will work in the organization
Means

 If

users have a difficulty with a system, it will not produce the expected benefits

Is the problem worth solving or will the solution to the problem work?

 Does

management support the project? Do users see the need for change? Will the new system result in a workforce reduction? Will the new system place any new demands on users or require any operating changes?

any information be less accessible or produced less frequently? Will customers experience adverse effects in any way? Do legal or ethical issues need to be considered?
Will

to the technical resources needed to develop, purchase, install, or operate the system Analysis of technical risks like familiarity with the application or technology, project size, and compatibility
Refers

Do we have the technical abilities and resources to be able to build the system?

 Can

the company acquire the necessary hardware, software, and network resources without difficulty? Does the company have the needed technical expertise? Does the proposed platform have sufficient capacity for future needs?

the hardware and software environment interface properly with external systems operated by customers and suppliers? Do clear expectations and performance specifications exist?
Will

 Means

that the projected benefits of the proposed system outweigh the estimated costs, which includes ongoing support and maintenance costs, as well as acquisition costs

Can we support the systems development and operational costs?

 Development

Costs

Development team salaries Consultant fees Development training Hardware and software Vendor installation Office space and equipment Data conversion costs

 Operational

Costs

Software upgrades Software licensing fees Hardware repairs Hardware upgrades Operational team salaries Communications charges User training

 Tangible

Benefits

Increased sales Reductions in staff Reductions in inventory and elimination of production delays Reductions in IT costs Better supplier prices

 Intangible

Benefits

Increased market share Increased brand recognition Enhanced company image Higher quality products Improved employee job satisfaction Improved customer service Better supplier relations

that a project can be implemented in an acceptable time frame Determine whether the deadlines are mandatory or desirable The interaction between time and costs should be considered
Means

Can the system be finished on time?

 Can

the company or the IT team control the factors that affect schedule feasibility? Has management established a firm timetable for the project? What conditions must be satisfied during the development of the system?

an accelerated schedule pose any risks? Will project management techniques be available to coordinate and control the project? Will a project manager be appointed?
Will

System requests that are not currently feasible can be resubmitted as new hardware, software, or expertise becomes available

An initially feasible project can be rejected later

Even if the request is feasible, it might not be necessary

For all those reasons, feasibility analysis is an ongoing task that must be performed throughout the systems development process