explain the concept of a business case and how a business ...€¦ · conduct a swot analysis and...
TRANSCRIPT
Chapter Objectives
Explain the concept of a business case and how a business case affects an IT project
Describe the strategic planning process and why it is important to the IT team
Conduct a SWOT analysis and describe the four factors involved
1
Chapter Objectives
Explain the purpose of a mission statement
Describe the SDLC, and explain how it
serves as a framework for systems
development and business modeling
List the reasons for information systems
projects and the factors that affect such
projects
2
Chapter Objectives
Explain the initial review of systems requests
and the role of the systems review committee
Define operational feasibility, technical
feasibility, economic feasibility, and schedule
feasibility
Describe the steps in a preliminary
investigation and the end product of an
investigation
3
Introduction
The term business case refers to the reasons,
or justification, for a proposal
A strong business case suggests that the
company should pursue the alternative,
above other options, because it would be in
the firm’s best interest to do so
Systems development typically starts with a
systems request, followed by a preliminary
investigation, which includes a feasibility
study
4
Strategic Planning – A Framework for
IT Systems Development
Strategic planning is the process of
identifying long-term organizational goals,
strategies, and resources
Strategic Planning Overview
– SWOT analysis
Figure 2-2 For more information about
strategic planning visit
scsite.com/sad8e/more,
locate Chapter 2, and then
click the Strategic Planning
link. 5
Strategic Planning – A Framework for
IT Systems Development
From Strategic Plans to Business
Results
– Mission statement
– Stakeholders
– Goals
– Objectives
Figure 2-4 Figure 2-3 For more information about
mission statements visit
scsite.com/sad8e/more,
locate Chapter 2, and then
click the Mission Statements
link. 6
Strategic Planning – A Framework for
IT Systems Development
A CASE Tool Example
– You are a systems analyst
– You research the Visible Analyst CASE tool
– Planning statements can include
assumptions, goals, objectives, and critical
success factors, and many other types of
statements
Figure 2-5
7
Strategic Planning – A Framework for
IT Systems Development
The Role of the IT Department in Project
Evaluation
– Management leadership and information
technology are linked closely, and remarkable
changes have occurred in both areas
– Today, systems development is much more
team oriented
– Although team-oriented development is the
norm, some companies see the role of the IT
department as a gatekeeper
8
Strategic Planning – A Framework for
IT Systems Development
The Future
– If you could look into the future, here is
what you might see: new industries,
products, and services emerging from
amazing advances in information
technology, customers who expect world-
class IT support, a surge in Internet-based
commerce, and a global business
environment that is dynamic and incredibly
challenging
9
What Is a Business Case?
Should be comprehensive, yet easy to
understand
Should describe the project clearly, provide
the justification to proceed, and estimate the
project’s financial impact
ProSci’s BPR Online Learning Center offers
a Business Case Tutorial Series
Figure 2-6
10
Main Reasons for Systems Projects
– Systems request
– Improved service
– Support for new products and services
– Better performance
– More information
Information Systems Projects
Figure 2-7
11
Information Systems Projects
Main Reasons for Systems Projects
– Stronger controls
• Encryption and biometric devices
– Reduced cost
Factors that Affect Systems Projects
– Internal and external factors affect every
business decision that a company makes, and
IT systems projects are no exception
Figure 2-9 Figure 2-8 For more information about
biometric devices visit
scsite.com/sad8e/more,
locate Chapter 2, and then
click the Biometric Devices
link. 12
Information Systems Projects
Internal Factors
– Strategic plan
– Top managers
– User requests
– Information technology department
– Existing systems and data
13
Information Systems Projects
External Factors
– Technology
• Electronic product code (EPC)
– Suppliers
• Critically important
• Just-in-time (JIT)
Figure 2-10 For more information about
JIT Systems visit
scsite.com/sad8e/more,
locate Chapter 2, and then
click the JIT Systems link. 14
Information Systems Projects
External Factors
– Customers
• Customer Relationship Management (CRM)
• Electronic proof of delivery (EPOD)
– Competitors
– The economy
– Government
Figure 2-11 For more information about
CRM Systems visit
scsite.com/sad8e/more,
locate Chapter 2, and then
click the CRM Systems link. 15
Information Systems Projects
Project Management
– If the project is approved, it can be planned,
scheduled, monitored and controlled, and
reported upon
– Individual analysts or IT staff members often
handle small projects, but companies usually
designate a project manager to coordinate
the overall effort for complex projects
Figure 2-12
16
Evaluation of Systems Requests
Systems review committee or a computer
resources committee evaluate systems
requests
Systems Requests Forms
– A properly designed form streamlines the
request process and ensures consistency
– Occasionally a situation will arise that
requires an immediate response
Figure 2-13
17
Evaluation of Systems Requests
Systems Review Committees
– Most large companies use a systems review
committee to evaluate systems requests
– Many smaller companies rely on one person
to evaluate system requests instead of a
committee
– The goal is to evaluate the requests and set
priorities
18
Overview of Feasibility
A systems request must pass several tests,
called a feasibility study, to see whether it is
worthwhile to proceed further
Operational Feasibility
– Operational feasibility means that a proposed
system will be used effectively after it has
been developed
– Depends on several vital issues
Figure 2-14
19
Overview of Feasibility
Technical Feasibility
– Technical feasibility refers to technical
resources needed to develop, purchase,
install, or operate the system
20
Overview of Feasibility
Economic Feasibility
– Total cost of ownership (TCO)
– Tangible benefits
– Intangible benefits
Schedule Feasibility
For more information about
TCO visit
scsite.com/sad8e/more,
locate Chapter 2, and then click
the TCO link. 21
Evaluating Feasibility
The first step in evaluating feasibility is to
identify and weed out systems requests that
are not feasible
Even if the request is feasible, it might not be
necessary
Feasibility analysis is an ongoing task that
must be performed throughout the systems
development process
22
Setting Priorities
Factors that Affect Priority
– Will the proposed system reduce costs?
Where? When? How? How much?
– Will the system increase revenue for the
company? Where? When? How? How
much?
23
Setting Priorities
Factors that Affect Priority
– Will the systems project result in more
information or produce better results? How?
Are the results measurable?
– Will the system serve customers better?
– Will the system serve the organization
better?
24
Setting Priorities
Factors that Affect Priority
– Can the project be implemented in a reasonable time period? How long will the results last?
– Are the necessary financial, human, and technical resources available?
– Whenever possible, the analyst should evaluate a proposed project based on tangible costs and benefits that represent actual (or approximate) dollar values
25
Setting Priorities
Discretionary and Nondiscretionary Projects
– Projects where management has a choice in
implementing them are called discretionary
projects
– Projects where no choice exists are called
nondiscretionary projects
26
Preliminary Investigation Overview
Preliminary investigation
Interaction with Managers and Users
– Let people know about the investigation and
explain your role
– Employee attitudes and reactions are important
and must be considered
– Be careful in your use of the word problem
– Question users about additional capability they
would like to have
Figure 2-15 27
Preliminary Investigation Overview
Planning the Preliminary Investigation
– During a preliminary investigation, a
systems analyst typically follows a series of
steps
– The exact procedure depends on the nature
of the request, the size of the project, and the
degree of urgency
Figure 2-16 Figure 2-17
28
Preliminary Investigation Overview
Step 1: Understand the Problem or
Opportunity
– A popular technique for investigating causes
and effects is called a fishbone diagram, or
Ishikawa diagram
– Pareto chart
Figure 2-18 For more information about
fishbone diagram visit
scsite.com/sad8e/more,
locate Chapter 2, and then click
the Fishbone Diagram link.
Figure 2-19
29
Preliminary Investigation Overview
Step 2: Define the Project Scope and
Constraints
– Project scope
– Project creep
– Constraint
30
Preliminary Investigation Overview
Step 2: Define the Project Scope and
Constraints
– Present versus future
– Internal versus external
– Mandatory versus desirable
– Regardless of the type, all constraints should
be identified as early as possible to avoid
future problems and surprises
Figure 2-20
31
Preliminary Investigation Overview
Step 3: Perform Fact-Finding
– Fact-finding involves various techniques
– Depending on what information is needed to
investigate the systems request, fact-finding
might consume several hours, days, or weeks
– Analyze Organization Charts
• Obtain organization charts to understand how the
department functions and identify individuals
you might want to interview
Figure 2-21
32
Preliminary Investigation Overview
Step 3: Perform Fact-Finding
– Conduct interviews
1. Determine the people to interview
2. Establish objectives for the interview
3. Develop interview questions
4. Prepare for the interview
5. Conduct the interview
6. Document the interview
7. Evaluate the interview
Figure 2-22
33
Preliminary Investigation Overview
Step 3: Perform Fact-Finding
– Review documentation
– Observe operations
– Conduct a user survey
34
Preliminary Investigation Overview
Step 4: Analyze Project Usability, Cost,
Benefit, and Schedule Data
– Before you can evaluate feasibility, you must
analyze this data carefully
– What information must you obtain, and how
will you gather and analyze the information?
– What sources of information will you use,
and what difficulties will you encounter in
obtaining information?
35
Preliminary Investigation Overview
Step 4: Analyze Project Usability, Cost,
Benefit, and Schedule Data
– Will you conduct interviews? How many people will you interview, and how much time will you need to meet with the people and summarize their responses?
– Will you conduct a survey? Who will be involved? How much time will it take people to complete it? How much time will it take to prepare it and tabulate the results?
36
Preliminary Investigation Overview
Step 4: Analyze Project Usability, Cost,
Benefit, and Schedule Data
– How much will it cost to analyze the
information gathered and to prepare a report
with findings and recommendations?
37
Preliminary Investigation Overview
Step 5: Evaluate Feasibility
– Start by reviewing the answers to the
questions you asked
– Operational feasibility
– Technical feasibility
– Economic feasibility
– Schedule feasibility
38
Preliminary Investigation Overview
Step 6: Present Results and
Recommendations to Management
– The final task in the preliminary
investigation is to prepare a report to
management
– The format of the preliminary investigation
report varies from one company to another
Figure 2-23
39
Preliminary Investigation Overview
Step 6: Present Results and
Recommendations to Management
• Introduction
• Systems request summary
• Findings
• Case for action
• Project Roles
• Time & cost estimates
• Expected benefits
• Appendix
40
Chapter Summary
Systems planning is the first phase of the
systems development life cycle
Effective information systems help an
organization support its business process,
carry out its mission, and serve its
stakeholders
41
Chapter Summary
Strategic planning allows a company to
examine its purpose, vision, and values and
develops a mission statement, which leads to
goals, objectives, day-to-day operations, and
business results that affect company
stakeholders
Systems projects are initiated to improve
performance, provide more information,
reduce costs, strengthen controls, or provide
better service
42
Chapter Summary
Various internal and external factors affect systems projects, such as user requests, top management directives, existing systems, the IT department, software and hardware vendors, technology, customers, competitors, the economy, and government
During the preliminary investigation, the analyst evaluates the systems request and determines whether the project is feasible from an operation, technical, economic, and schedule standpoint
43
Chapter Summary
Analysts evaluate systems requests on the basis of their expected costs and benefits, both tangible and intangible
The steps in the preliminary investigation are to understand the problem or opportunity; define the project scope and constraints; perform fact-finding; analyze project usability, cost, benefit, and schedule data; evaluate feasibility; and present results and recommendations to management
44
Chapter Summary
The last task in a preliminary investigation is
to prepare a report to management
The report must include an estimate of time,
staffing requirements, costs, benefits, and
expected results for the next phase of the
SDLC
45
Test Yourself
1. The series of questions that top managers
ask during strategic planning is called
_______?
46
Test Yourself
1. The series of questions that top managers
ask during strategic planning is called
_______?
SWOT Analysis
S = Strengths
W= Weaknesses
O= Opportunities
T= Threats
47
Test Yourself
2. True/False: Goals are exactly the same as
objectives.
48
Test Yourself
2. True/False: Goals are exactly the same as
objectives.
False
49
Test Yourself
3. True/False: Critical success factors are vital
objectives that must be achieved.
50
Test Yourself
3. True/False: Critical success factors are vital
objectives that must be achieved.
True
51
Test Yourself
4. List the reasons why a new systems project
may be initiated.
52
Test Yourself
4. List the reasons why a new systems project
may be initiated.
Improved service
Support for new products and services
Better performance
More information
Stronger controls
Reduced cost
53
Test Yourself
5. ______ uses RFID tags to identify and
monitor the movement of each individual
product.
54
Test Yourself
5. Electronic product code (EPC) technology
uses RFID tags to identify and monitor the
movement of each individual product.
55
Test Yourself
6. A systems review committee
a) tests for operational, technical, and
economic feasibility.
b) produces the company’s strategic plan by
using SWOT analysis.
c) is a group of key managers and users who
evaluate systems requests.
56
Test Yourself
6. A systems review committee
a) tests for operational, technical, and
economic feasibility.
b) produces the company’s strategic plan by
using SWOT analysis.
c) is a group of key managers and users who
evaluate systems requests.
57
Test Yourself
7. What 4 measures, used in a feasibility study,
help predict a system’s success?
58
Test Yourself
7. What 4 measures, used in a feasibility study,
help predict a system’s success?
Operational feasibility
Technical feasibility
Economic feasibility
Schedule feasibility
59
Test Yourself
8. A new Web site that enhances the
company’s image is an example of a
tangible/intangible benefit to the company.
60
Test Yourself
8. A new Web site that enhances the
company’s image is an example of a
intangible benefit to the company.
61
Test Yourself
9. Name 4 of the 6 steps in the preliminary
investigation.
62
Test Yourself
9. Name 4 of the 6 steps in the preliminary
investigation.
1. Understand the problem or opportunity
2. Define the project scope and constraints
3. Perform fact-finding
4. Analyze project usability, cost, benefit, and
schedule data
5. Evaluate feasibility
6. Present results and recommendations to
management
63
Test Yourself
10. Match the type of constraints in the left
column to the proper example in the right
column.
1. present
2. Internal
3. mandatory
a. The order entry system
must run in a UNIX environment
b. The inventory system must be
operational by next week
c. The human resources system
interface with the current
accounting system
64
Test Yourself
10. Match the type of constraints in the left
column to the proper example in the right
column.
1. present
2. internal
3. mandatory
b. The inventory system must be
operational by next week
c. The human resources system
interface with the current
accounting system
a. The order entry system
must run in a UNIX environment
65
Systems Analysis & Design
8th Edition
End Chapter 2