ch 12 instructor ppt slides

8/10/2019 Ch 12 Instructor PPT Slides

1/39

Developing Business/IT Solutions

Chapter

12

McGraw-Hill/Irwin Copyright 2010 by The McGraw-Hill Companies, Inc. All rights reserved.


2/39

Use the systems development processoutlined in this chapter and the model of IScomponents from Chapter 1 as problem-solving frameworks to help you proposeinformation systems solutions to simple

business problems Describe and give examples to illustrate

how you might use each of the steps of theinformation systems development cycle todevelop and implement a businessinformation system

Learning Objectives

12-2


3/39

Learning Objectives

12-3

Explain how prototyping can be used asan effective technique to improve theprocess of systems development for endusers and IS specialists

Understand the basics of projectmanagement and their importance to asuccessful system development effort

Identify the activities involved in the

implementation of new informationsystems


4/39

Learning Objectives

12-4

Compare and contrast the four basicsystem conversation strategies

Describe several evaluation factors thatshould be considered in evaluating theacquisition of hardware, software, and ISservices


5/39

IS Development

Information Systems Development

Applying the Systems Approach to ISDevelopment

Also called Application Development

12-5


6/39

The Systems Approach

Problem solving technique

Interrelated activities

Recognize and define a problem or opportunityusing systems thinking

Develop and evaluate alternative system solutions Select the solution that best meets your

requirements

Design the selected system solution

Implement and evaluate the success of the system

12-6


7/39

What is Systems Thinking?

Seeing the forest andthe trees in any situation

Seeing interrelationshipsamong systemsrather than linear cause-and-effect chains

Seeing processesof change among systems

rather than discrete snapshots of change

Seeing the systemin any situation

Find the input, processing, output, feedback

and control components

12-7


8/39


9/39

Systems Analysis and Design (SA&D)

Overall process

Identification of business problems

Design

Implementation

Two most common approaches

Object-oriented analysis and design

Life cycle

12-9


10/39

Systems Development Lifecycle (SDLC)

12-10


11/39

Systems Development Process

Systems Investigation

First step

Consider multiple proposals

Preliminary feasibility study

Information needs of prospective users

Resource requirements

Costs

Benefits Legal environment

Feasibility study may be unnecessary

Government mandate 12-11


12/39

Types of Feasibility Studies

Operational

Fix the problem, fit the organization

Economic

Cost/Benefit Analysis

Technical Components and time available

Human Factors

Right people and roles available

Legal/Political

Government, patent, or license restrictions

12-12


13/39

Systems Analysis

Produces the functional requirements

Basis for the design of the new system

In-depth study

Information needs

Company

End users

Business stakeholders

Existing system Activities, resources, and products

12-13


14/39

Types of Analysis

Organizational

Structure, people, activities

Present System

Hardware, software, network, input, output,

processing Logical

What the current system does

Not concerned with how it works

12-14


15/39

Functional Requirements

Goal: what needs to be done, not how

One of the most difficult steps

Determine what type of information eachbusiness activity requires

Determine the information processingcapabilities required for each system activity

12-15


16/39

Functional Requirements

12-16


17/39

Systems Design

Focuses on three areas

12-17


18/39

Prototyping Life Cycle

12-18


19/39

User Interface Design

Supports interactions between end users andcomputer-based applications

Get help from end-users

Designers create attractive and efficient forms

Frequently a prototyping process

Produces detailed design specifications

12-19


20/39

System Specifications

Components of formal design

User interface methods and products

Database structures

Processing procedures

Control procedures

Examples of System Specifications

User interface specifications

Database specifications Software specifications

Hardware and network specifications

Personnel specifications12-20


21/39

End User Development

12-21


22/39

Encouraging End User Web Development

Look for tools that make sense

Spur creativity

Set some limits

Give managers responsibility

Make users comfortable

12-22


23/39

Object-Oriented Analysis and Design

Object anything a programmer needsmanipulated

Object-Oriented Programming (OOP)techniques:

Inheritance Modularity

Polymorphism

Encapsulation

Object-Oriented Analysis (OOA)

Model of object interaction, not solution

Object-Oriented Design (OOD)

Solution based on constraints


24/39

Implementation Process

12-24


25/39

Sample Implementation Process

12-25


26/39

RWC 2: Difficult Path to Software Upgrades

System upgrades are daunting

Failures are costly

Loss of immediate revenue

Loss of customer loyalty

Three to six month recovery Contingency plans

Backup website

Extra operators in call center

Packet implementation helps

Basic install

Additional features

12-26


27/39

Project Management

The skills and knowledge necessary to be agood project manager will translate intovirtually any project environment

Sought after by most organizations

12-27


28/39

What is a Project?

Every project has

A set of activities with a clear beginning and end

Goals

Objectives

Tasks Limitations or constraints

A series of steps or phases

Managing a project effectively requires

Process

Tools

Techniques

12-28


29/39

Phases of Project Management

12-29


30/39

Evaluating Hardware, Software, Services

Establish minimum physical and performance

characteristics Formalize in an RFP or RFQ

Send RFQ to appropriate vendors

Evaluate bids when received All claims must be demonstrated

Obtain recommendations from other users

Search independent sources for evaluations Benchmark test programs and test data

12-30


31/39

Hardware Evaluation Factors

Performance

Cost

Reliability

Compatibility

Technology Ergonomics

Connectivity

Scalability

Software Support

12-31


32/39

Software Evaluation Factors

Most Hardware Evaluation Factors Apply

Quality

Efficiency

Flexibility

Security Connectivity

Maintenance

Documentation

Hardware

Overall Rating Software that is slow, hard to use, bug-filled, or poorly

documented is not a good choice at any price12-32


33/39

IS Services

Examples of IS services

Developing a company website

Installation or conversion of hardware/software

Employee training

Hardware maintenance

System design and/or integration

Contract programming

Consulting services

12-33


34/39

IS Service Evaluation Factors

IS evaluation factors include Performance Systems development

Maintenance

Conversion

Training Backup facilities and services

Accessibility to sales and support

Business position and financial strength Hardware selection and compatibility Software packages offered

12-34


35/39

Other Implementation Activities

Testing

Data conversion

Documentation

Training

12-35


36/39

Major System Conversion Strategies

12-36

(Plunge)


37/39

Post-Implementation Activities

System Maintenance

Corrective: fix bugs and logical errors

Adaptive: add new functionality

Perfective: improve performance

Preventive: reduce chances of failure

Post Implementation Review

Correct Errors

Periodic review/audit

Single most costly activity

12-37


38/39

How do global companies keep their

consumer sites updated in the locallanguage or localizing the content withoutspending a lot of time and money?

PayPal redesigned software Allow simultaneous refreshes for 15 locales

ranging from France to Poland.

Result

Net total payment volume $14 billion 12 percent of U.S. e-commerce

8 percent of global e-commerce.

12-38

RWC 3: PayPal Going Global


39/39

RWC 4: Project Backlog

Demand for IT is increasing

Requests for IT projects are piling up.

Budget is not increasing.

Backlog is number-one barrier to effectiveness

Two types of backlog

Backlog of desire

Applications that users are yearning for

Backlog of commitment Projects that are approved but not started

CIOs need to pay attention to both types of abacklogs.

12 39

ch 12 instructor ppt slides

Documents