1. Phase 1: Preliminary Investigation or Feasibility study
The first phase of the system development life cycle: the
preliminary investigation. During this phase, the system
analyst determines whether the development of the requested
system is justified. First, we look at why and how ideas for
system projects originate. Then, we examine the criteria used
to evaluate system projects. Next, we study the preliminary
investigation itself - first by discussing its objectives and then
by studying the activities that take place during this
investigation. Finally, we look at the activities that complete
the preliminary investigation phase.

2. Reasons For System Projects
- A goal is an end that the organization is striving
to attain.
- An objective is a task that will help achieve a
goal.
- A system request is a formal request for the
services of information system department.
The reasons for systems requests by the type of
improvement required. The five types of desired
improvement are service, performance, information,
controls, and economy

3. Sources of systems projects
We can trace the origination of systems projects to the
five sources.
- End user requests
- Top-management directives
- Existing systems
- Information systems department
- External forces

4. Request form and procedure

5. Evaluation of system requests
Systems review committee
Some organizations assign responsibility for evaluating
systems requests to one manager. This manager might be
the director of information system or a high-ranking
executive in another area of the company. Other
organizations use the committee method to evaluate
system requests. This committee is often called system
review committee. Or an advisory committee.

6. Evaluation of projects
The systems review committee faces the task of evaluating
all requests for services, rejecting some, and selecting and
establishing priorities for those requests that appear to offer
the greatest benefit to the organization.
Feasibility
A systems requests has feasibility if the request can be
successfully implemented. When you analyze feasibility,
you must consider three separate types:
- Technical feasibility
- Operational feasibility
- Economic feasibility

7. Technical feasibility
A systems request is technically feasible if the
organization has or can obtain the equipment and personnel
to develop (or purchase), install, and operate the system.
Operational feasibility
A systems request is operationally feasible if it is
highly likely that the system will be used once it has been
developed and implemented. If the end users resist a new
system, the system might not be used to its full potential. In
that case, the benefits the organization hopes to achieve will
not occur.

8. Economic feasibility
A systems request is economically feasible if the
project benefit of the proposed system outweigh the
estimated costs involved in developing (or purchasing),
installing, and operating it.

9. Determining feasibility
The first step in the evaluation of a systems requests is an
initial determination of feasibility. Those requests that do not
meet an initial feasibility test should immediately be
rejected, and the systems request form should be returned to
the requester with an explanation of the reasons for rejection.
Criteria used to evaluate systems requests
After rejecting infeasible systems requests, the committee
must then establish priorities for the remaining feasible
systems requests. Under normal circumstances, the rule is to
favor those projects that provide the greatest benefit to the
company at the lowest cost in the shortest period of time.

10. Preliminary investigation objectives
Understand the problem
- the true nature of the problem
- the reason for the system request
Define the project scope and constraints
- project scope is the range, or extent, of the project
- constraint is a condition, restriction, or requirement
Identify the benefits
- Tangible benefits
- Intangible benefits
Estimate the costs
Report to management

11. Preliminary investigation activities
Step 1: Obtain an authorization for the preliminary investigation.
Step 2: Identify the information that you need to gather.
Step 3: Obtain organization charts for those departments
undergoing study to determine who should be interviewed.
Step 4: Conduct interviews to obtain information.
Step 5: Review current system documentation and observe
current operations to obtain information.
Step 6: Analyze the gathered information.
Step 7: Present your results and recommendations to
management.

12. Step 1: Obtain an authorization for the preliminary investigation.
Step 2: Identify the information that you need to gather.
Step 3: Obtain organization charts for those departments undergoing study to determine who should be interviewed.
Step 4: Conduct interviews to obtain information.

13. Preliminary investigation activities
Step 5: Review current system documentation and observe current operations to obtain information.
Step 6: Analyze the gathered information.
Step 7: Present your results and recommendation to management.
Preliminary investigation activities

14. Preliminary investigation completion
Report
- the organization of a preliminary investigation report
1. Introduction
2. Systems request summary
3. Findings
4. Recommendations
5. Time and Cost estimates
6. Expected Benefits
7. Appendix
Presentation