1. SYSTEMS ANALYSIS & DESIGN Preliminary Investigation
PHASE 1
SYSTEMS PLANNING
and
Preliminary Investigation

2. Systems Planning Systems Planning Objectives
Learn how projects get started
Learn how projects are evaluated initially

3. Preliminary Investigation
Objectives
Describe the strategic planning process, and why it is important to IS managers
Explain the purpose of a mission statement
Explain why and how systems projects are initiated
Explain how systems projects are evaluated

4. Preliminary Investigation
Objectives
List the objectives of the preliminary investigation
Describe what activities occur during the preliminary investigation
Carry out fact-finding procedures to evaluate the systems request
Describe what takes place at the completion of the preliminary investigation

5. Introduction Systems planning tasks Examine the systems request
Conduct a preliminary investigation
Determine whether further development
is warranted

6. Introduction Systems planning topics
Why and how systems projects originate
Objectives and scope of the preliminary investigation
Fact-finding tasks
Activities that complete the systems planning phase

7. Strategic Planning Process
Strategic planning is the process of identifying
long-term organizational goals, strategies, and
resources
Strategic Planning Overview
SWOT analysis

8. Strategic Planning Process
From Strategic Plans to Business Results
Mission statement
Stakeholders
Goals
Objectives

9. Strategic Planning Process
Stakeholders are people affected by the company’s performance
Stakeholders include:
Customers
Employees
Suppliers
Stockholders
Members of the community

10. Strategic Planning Process
The impact of technology
Rapid expansion of information technology is creating entirely new industries, such as
E-commerce
Online stock trading
Change will be constant
Global competition
Rapidly changing markets
Explosive growth of information technology

11. Origination Systems Projects
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.
Starting point is a systems request

12. The reasons for systems requests
by the type of improvement required
Improved service
Better performance
More information
Support for New Products and Services
Stronger controls
Reduced cost

13. Systems Request Reduced cost Stronger controls Improved service
Better performance
Systems
Request
Stronger controls
Support for New Products and Services
More information

14. Sources of systems projects
Who initiates 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

15. Internal and external factors that affect IT systems projects.
Strategic Plan
Technology
Top Managers
Technology
Technology
User requests
Suppliers
Customers
Information
Technology
Department
Existing Systems
and Data
Competitors
The Economy
Government
Internal and external factors that affect IT systems projects.

16. Request form and procedure
Streamlines the
process
Ensures consistency
Must be easy to
understand and use
Must include clear
instructions

17. Evaluation of system requests
Responsibility for evaluating systems
requests
A group of key managers and users
Systems review committee
Steering committee
Computer resources committee
Computer policy committee
A single individual
Typical in smaller companies
Must consult with users & managers

18. Evaluation of projects Systems review committee tasks :
Evaluate requests
Set priorities
Assess feasibility

19. request can be successfully implemented.
Overview of 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

20. Technical feasibility Technical feasibility depends on:
Does the organization have resources to develop/purchase and operate the system?
Technical feasibility depends on:
Technical expertise within the organization
Availability of necessary equipment
Hardware and software reliability
Adequate performance that will meet specifications
Capacity for future needs/projected growth

21. Operational feasibility Operational feasibility depends on:
Is the system a practical and
effective approach?
Operational feasibility depends on:
Management and user support
User involvement in planning
Impact on performance, customers, and
company image
Reasonable schedules

22. Economic feasibility Economic feasibility depends on:
Do the projected benefits outweigh the
estimated costs of development,
installation, and operation?
Economic feasibility depends on:
Costs — one time and continuing costs
Benefits — tangible and intangible benefits
Timing of various costs and benefits
Cost of not developing the system

23. Determining feasibility
First step is a determination of feasibility
Goal is to identify nonfeasible projects as soon as possible
Feasibility can change over time
Nonfeasible projects can be resubmitted
Initially feasible projects can be rejected later

24. Criteria used to evaluate systems requests
Reduce costs
Increase revenue
Produce more information or better results
Serve customers and the organization better
Reasonable time frame and lasting results
Resources available
Necessary or discretionary (รอบคอบระมัดระวัง)
Tangible or intangible factors

25. Preliminary investigation objectives
Purpose
To decide whether to continue the project
Objectives for Preliminary investigation
Understand the problem
Define the project scope and constraints
Identify the benefits
Estimate the costs
Report to management

26. Understand the problem
Identify the true nature of the problem and the reason for the systems request
Stated problem may not be the real problem
Clear statement defines the investigation scope

27. Define the project scope and constraints
Define the range or extent of the project
Set project boundaries
Constraints
Identify conditions, restrictions(การควบคุม), or
requirements
Present vs. future
Internal vs. external
Mandatory vs. desirable

29. Identify the benefits Tangible benefits Can be stated in dollars
Based on increased revenue or reduced
cost
Intangible benefits
Difficult to measure in dollars
Can involve job satisfaction or
company image

30. Estimate the time and costs
Determine what information is needed
Identify the sources of information
Decide whether to use interviews, if so how
many, and what time needed
Decide whether to use surveys, if so who to
complete it, and what time needed
Estimate the cost of gathering, analyzing, and reporting the information to management

31. Report to management Final task in the preliminary investigation
Key elements
Evaluation of systems request
Estimate of costs and benefits
Recommendations

32. Planning the Preliminary Investigation
During a preliminary investigation, a systems analyst typically follows a series of steps

33. Understand the problem or opportunity.
Define the project scope and constraints.
Perform fact-finding.
- Analyze organization charts.
- Conduct Interviews.
- Review documentation.
- Observe operations.
- Conduct a user survey.
Analyze project usability, cost, benefit, and schedule data.
Evaluate feasibility
- Operational
- Technical
- Economic
- Schedule
Present results and recommendations to
Management.
Six steps in a preliminary investigation.

34. Obtain authorization to proceed
Projects can create concern or opposition
Need clear authorization from
management
Good communication is important
Initial meeting with managers and users
Explain the project
Describe your responsibilities
Invite questions

35. Identify the necessary information
Review the preliminary investigation
objectives
List all information needed for these
Prepare a schedule of activities for this
phase

36. Perform fact-finding to gather the required information
Analyze organization charts
Conduct interviews
Review current documentation
Observe current operations to obtain
information
Conduct a brief survey of people who use
the system

37. Organization charts

38. Analyze the information
Identify alternatives
Include costs and benefits
Recommend an action
Possible actions
Take no further action
Apply some other solution
Proceed to systems implementation phase
Proceed to next SDLC phase — systems analysis

39. Preliminary investigation completion
Present your results and recommendations
to management
- Typical report sections
Introduction
Systems request summary
Findings
Recommendations
Time and Cost estimates
Expected Benefits
Appendix
Oral presentation also might be required