Chapter 2 Analyzing the Business case

Slides:



Advertisements
Similar presentations
System Planning (Preliminary Investigation Overview)
Advertisements

Chapter 2 Analyzing the Business Case.
The System Development Life Cycle
Systems Analysis and Design 9th Edition
Week Two: Systems Planning
Chapter 2.
Chapter 8 Information Systems Development & Acquisition
Discovering Computers Fundamentals, 2011 Edition Living in a Digital World.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
1 Info 1409 Systems Analysis & Design Module Lecture 5 - Feasibility HND Year /9 De Montfort University.
Fundamentals of Information Systems, Second Edition
Chapter 2.
Systems Development Life Cycle
Analyzing the Business Case
System Planning (Strategic Planning & Information Systems Projects)
Fact-Finding Fact-Finding Overview
System Planning Analyzing the Business Case
1 Lecture 6 The Systems Analyst (Role and activities) Systems Analysis & Design Academic Year 2008/9.
Introduction to Systems Analysis and Design
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 16-1 Accounting Information Systems 9 th Edition Marshall.
Acquiring Information Systems and Applications
Requirements Modeling
Systems Analysis and Design: The Big Picture
Chapter 2: Analyzing Business Case Phase 1: Systems Planning
Initiating and Planning Systems Development projects
System Planning- Preliminary investigation
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Case Justification System Planning
Chapter 14 Information System Development
Lecture 4 1 Introduction to Systems Planning Lecture 4 2 Objectives n Describe the strategic planning process n Explain the purpose of a mission statement.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 3 Systems Planning and Selection 3.1.
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
2  Mission Statement.  Company’s overall purpose and direction, products, services and values.  Goals.  That accomplish the mission. E.g. 5 year plan.
Prof. Mohammad Moizuddin
Systems Analysis Lecture 2 Analysing the Business Case Feasibility Scope 1 BTEC HNC Systems Support Castle College 2007/8.
Systems Analysis and Design in a Changing World, 5 rd Edition Chapter 3: The Analyst as a Project Manager.
Phase 1: Preliminary Investigation or Feasibility study
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 3 Identification and Selection of Development Projects.
System Planning (Preliminary Investigation Overview)
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Topic 2 Analyzing the Business Case.  Describe the strategic planning process and why it is important to the IT team  Explain the purpose of a mission.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Lecture 21 Introduction to System Development Life Cycle - Part 1.
1 Systems Analysis & Design 7 th Edition Chapter 2.
Systems Analysis & Design 7 th Edition Chapter 2.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Phase 1 Systems Planning
CHAPTER ELEVEN Information System Development and Programming Languages Copyright © Cengage Learning. All rights reserved.
MANAGEMENT INFORMATION SYSTEM
CHAPTER 2 SYSTEM PLANNING DFC4013 System Analysis & Design.
Systems Development Life Cycle
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design in a Changing World, 4th Edition
Principles of Information Systems Eighth Edition
Fundamentals of Information Systems, Sixth Edition
Business System Development
IMPORTANCE OF STRATEGIC PLANNING
Chapter 4 Systems Planning and Selection
Systems Analysis and Design 10th Edition
Analyzing the Business Case
Introduction to Projects
Chapter 13: Systems Analysis and Design
Systems Analysis and Design
Analyzing the Business Case
Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
Presentation transcript:

Chapter 2 Analyzing the Business case

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 3

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 3

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

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 4

Strategic Planning – A Framework for IT Systems Development From Strategic Plans to Business Results Mission statement Stakeholders Goals Objectives

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

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

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

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

Information Systems Projects Main Reasons for Systems Projects Systems request Improved service Support for new products and services Better performance More information Stronger controls Encryption and biometric devices Reduced cost

Information Systems Projects Factors that Affect Systems Projects Internal and external factors affect every business decision that a company makes, and IT systems projects are no exception

Information Systems Projects Internal Factors Strategic plan Top managers User requests Information technology department Existing systems and data

Information Systems Projects External Factors Technology Electronic product code (EPC) Suppliers Critically important Just-in-time (JIT)

Information Systems Projects External Factors Customers Customer Relationship Management (CRM) Electronic proof of delivery (EPOD) Competitors The economy Government

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

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

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

Overview of Feasibility A systems request must pass several tests, called a feasibility study, to see whether it is worthwhile to proceed further Technical Economic Schedule Operational

Overview of Feasibility Operational Feasibility Operational feasibility means that a proposed system will be used effectively after it has been developed Depends on several vital issues Technical Feasibility Technical feasibility refers to technical resources needed to develop, purchase, install, or operate the system

Overview of Feasibility Economic Feasibility Total cost of ownership (TCO) assessing costs, which includes ongoing support and maintenance costs, as well as acquisition costs Tangible benefits E.g. decrease in expenses, an increase in revenues Intangible benefits E.g. Web site that improves a company's image Schedule Feasibility

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

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?

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?

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

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

Preliminary Investigation Overview An initial investigation to clearly identify the nature and scope of the business opportunity or problem 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

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

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

Preliminary Investigation Overview Step 2: Define the Project Scope and Constraints Project scope specific determination of a project's boundaries or extent Project creep project with very general scope, without specific authorization Constraint Condition/requirement that the system must satisfy or an outcome that the system must achieve

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

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

Preliminary Investigation Overview Step 3: Perform Fact-Finding Conduct interviews Determine the people to interview Establish objectives for the interview Develop interview questions Prepare for the interview Conduct the interview Document the interview Evaluate the interview

Preliminary Investigation Overview Step 3: Perform Fact-Finding Review documentation Observe operations Conduct a user survey

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?

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?

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?

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

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

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

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 49

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 49

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 49

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 49

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 49