ISOM221+Lecture+3+-+Project+Identification+and+Selection

ISOM221+Lecture+3+-+Project+Identification+and+Selection -...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
ISOM221 Information Systems Analysis and Design Lecture 3: Project Identification and Selection 1 Systems Development Life Cycle Planning Analysis Design Implementation 2
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Agenda Understand the importance of linking the information system to business needs Be able to create a system request Understand how to assess technical, economic, and organizational feasibility Understand how projects are selected in some organizations 3 Project Identification and Initiation Projects are driven by business needs Identified by business people E.g., to support a new marketing campaign, reach a new type of customers, and improve interactions with supplier suppliers Identified by IT people E.g., to leverage the capabilities of emerging technologies (such as the Internet and smart cards) to gain the first-mover advantage Identified jointly by business and IT (the ideal case) 4
Background image of page 2
Project Sponsor The project sponsor is someone who recognizes the strong business need for a system The project sponsor believes in the system The project sponsor believes in the system and wants to see it succeed Normally this is a business person (e.g., marketing, accounting, or finance) Should have the authority to move it forward 5 Project Sponsor (cont.) The project sponsor will work throughout the SDLC to make sure that the project is moving in the right direction from the perspective of the business Serves as the primary point of contact for the Serves as the primary point of contact for the system The size or scope of the project determines the kind of sponsor needed, e.g., Small departmental system b a single manager Large organizational system b senior management team / CEO 6
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Business Requirements Business need drives the high-level business requirements for the system Business requirements are what features and capabilities the information system will have to include For example, for an e-commerce system (e.g., Amazon), business requirements may include Ability to collect customer orders online Ability for suppliers to receive inventory information as orders are placed 7 Business Value Tangible Value Can be quantified and measured easily Example: 2% reduction in operating costs Intangible Value Results from an intuitive belief that the system provides important, but hard-to-measure, benefits to the organization Example: improved customer service 8
Background image of page 4
Agenda Understand the importance of linking the information system to business needs Be able to create a system request Understand how to assess technical, economic, and organizational feasibility Understand how projects are selected in some organizations 9 System Request The document that describes the business reasons for building a system and the value that system is expected to provide The project sponsor usually completes this form as part of a formal system selection process
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 23

ISOM221+Lecture+3+-+Project+Identification+and+Selection -...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online