Slide 1 Systems Analysis and Design with UML Version 2.0 Chapter 3: Project Initiation.

Slides:



Advertisements
Similar presentations
DOCUMENTATION COMMITTEE I.INTRODUCTORY PAGE A. NAME AND ADDRESS OF BUSINESS (include LOGO and Tagline) B. NAME(S) AND ADDRESS(ES) OF PRINCIPALS webpage.
Advertisements

PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Systems Analysis and Design
© Copyright 2011 John Wiley & Sons, Inc.
The Systems Development Life Cycle
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
1 California State University, Fullerton Chapter 13 Developing and Managing Information Systems.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
The Analyst as a Project Manager
Feasibility Analysis Chapter 3
Understanding product feasibility and business planning.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Systems.
Project Identification and Selection
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Initiating and Planning Systems Development projects
Systems Analysis and Design with UML Version 2
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 1 Chapter 5 Initiating and Planning Systems Development.
ZEIT2301 Design of Information Systems Project Initiation School of Engineering and Information Technology Dr Kathryn Merrick.
Information Systems Planning
Systems Analysis and Design Fourth Edition
1-1 CHAPTER 1 An Overview of Financial Management.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 3 Systems Planning and Selection 3.1.
Lecture 2: Project Initiation Phase 1: Planning
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
Alter – Information Systems © 2002 Prentice Hall 1 The Process of Information System Planning.
Phase 1: Preliminary Investigation or Feasibility study
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Feasibility Study.
The Business Plan: Creating and Starting the Venture
4-1 © Prentice Hall, 2004 Chapter 4: Project Management and Planning Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S.
Slide 1 Systems Analysis and Design with UML Version 2.0 An Object-Oriented Approach, Second Edition Chapter 3: Project Initiation Alan Dennis, Barbara.
Slide 1 Systems Analysis and Design with UML Version 2.0 An Object-Oriented Approach, Second Edition Chapter 3: Project Initiation Alan Dennis, Barbara.
5. Planning Phase System Analysis And Design Program: BSCS II (Advent Semester – 2014) Lecturer: Rebecca Asiimwe
Systems Analysis and Design 5th Edition Chapter1: The Systems Analyst and Information Systems Development Prof. Salim Arfaoui 1-0© Copyright 2011 John.
Slide 1 Software Construction Software Construction Lecture 3.
Selecting Projects IT Project Management. Project Initiation: Strategic Planning First step in initiating projects: look at the big picture, organization’s.
Slide 1 Systems Analysis and Design with UML Version 2.0 An Object-Oriented Approach, Second Edition Chapter 3: Project Initiation.
Systems Analysis and Design 5th Edition Chapter1: The Systems Analyst and Information Systems Development Roberta Roth, Alan Dennis, and Barbara Haley.
Systems Analysis and Design 5th Edition Chapter1: The Systems Analyst and Information Systems Development Roberta Roth, Alan Dennis, and Barbara Haley.
CJA 234 MART The power of possibility/cja234martdotcom BIS 375 Entire Course FOR MORE CLASSES VISIT BIS 375 Week 1 Discussion Question.
Entrepreneurship.
Name: Date: Author: Version:
Chapter 5 Initiating and Planning Systems Development Projects
© Copyright 2011 John Wiley & Sons, Inc.
Strategic Information Initiatives
C. What is a Feasibility report
TIM 58 Continuing Ch 2: Project Management
Systems Analysis and Design
Systems Analysis and Design in a Changing World, 4th Edition
Opportunity Recognition
Principles of Information Systems Eighth Edition
Project Initiation Chapter 2.
CIS 210 Systems Analysis and Development
Opportunity Recognition
Unit – iii Sources of product for business
Feasibility and Business Planning
FEASIBILITY STUDY Feasibility study is a means to check whether the proposed system is correct or not. The results of this study arte used to make decision.
Systems Analysis and Design
Chapter 5 Initiating and Planning Systems Development Projects
Opportunity Recognition
Systems Analysis and Design with UML Version 2
Systems Analysis and Design Chapter1: Introduction
Rekayasa Perangkat Lunak
Opportunity Recognition
Chapter 5 Initiating and Planning Systems Development Projects
Chapter 22, Part
Systems Development An Overview of Systems Development
Accounting Discipline Overview
Presentation transcript:

Slide 1 Systems Analysis and Design with UML Version 2.0 Chapter 3: Project Initiation

Slide 2 Key Ideas Projects being when someone sees an opportunity to create business value from using information technology. Feasibility analysis is used to aid in the decision of whether or not to proceed with the IS project.

Slide 3 Key Ideas The project sponsor is a key person proposing development or adoption of the new information technology. The approval committee reviews proposals from various groups and units in the organization and decides which to commit to developing.

Slide 4 System Request A system request is a document that describes the business reasons for building a system and the value that the system is expected to provide. The completed system request is submitted to the approval committee for consideration.

Slide 5 System Request Most system requests include five elements: Project sponsor Business need Functionality Expected value Special issues or constraints

Slide 7 Applying the Concepts at CD Selections CD Selections is a chain of fifty music stores located in California, with headquarters in Los Angeles. Margaret Mooney, Vice President of Marketing, has recently become both excited by and concerned with the rise of Internet sites selling CDs. The Internet has great potential, but Margaret wants to use it in the right way. Rushing into e-commerce without considering things like its effect on existing brick-and- mortar stores and the implications on existing systems at CD Selections could cause more harm than good. CD Selections currently has a Web site that provides basic information about the company and about each of its stores. (See page 63).

Slide 9 FEASIBILITY ANALYSIS

Slide 10 Feasibility Analysis Feasibility analysis guides the organization in determining whether to proceed with a project. Feasibility analysis also identifies the important risks associated with the project that must be addressed if the project is approved.

Slide 11 Feasibility Analysis Detailing Expected Costs and Benefits Technical feasibility Economic feasibility Organizational feasibility

Slide 12 Technical Feasibility: Can We Build It? The extent to which the system can be successfully designed, developed, and installed by the IT group. Technical feasibility analysis is in essence a technical risk analysis that strives to answer the question: “Can we build it?”

Slide 13 Technical Feasibility Factors: Familiarity with application Knowledge of business domain. Familiarity with technology Extension of existing firm technologies. Project size Number of people, time, and features. Compatibility: The harder it is to integrate the system with the company’s existing technology.

Slide 14 Economic Feasibility Should We Build It? An economic feasibility analysis (also called a cost–benefit analysis) identifies the financial risk associated with the project. Economic feasibility is determined by identifying costs and benefits associated with the system, assigning values to them, and then calculating the cash flow and return on investment for the project. This attempts to answer the question: “Should we build the system?”

Slide 15 Economic Feasibility Factors: Development costs Annual operational costs Annual benefits Intangible costs and benefit

Example Costs and Benefits

Assign Values to Costs and Benefits

Slide 18 Cash Flow Method for Cost Benefit Analysis

Slide 19 Organizational Feasibility If we build it, will they come? Organizational feasibility of the system determining how well the system ultimately will be accepted by its users and incorporated into the ongoing operations of the organization.

Slide 20 Organizational Feasibility If we build it, will they come? Project champion(s) The champion is a high-level non-IS executive who is usually but not always the person who created the system request. Organizational management management should encourage people to use the system and to accept the changes that the system will likely create. System users

Applying the Concepts at CD Selections A senior systems analyst, Alec Adams, was assigned to help Margaret conduct a feasibility analysis because of his familiarity with CD Selections’ sales and distribution systems. Alec and Margaret worked closely together over the next few weeks on the feasibility analysis. (See page 75) Slide 21

Slide 22 Summary Project initiation involves creating and assessing goals and expectations for a new system The system request describes an overview of the proposed system. The feasibility study is concerned with insuring that technical, economic, and organizational benefits outweigh costs and risks