1

Introduction to Information Systems

Essentials for the Internetworked E-Business Enterprise

Eleventh Edition

James A. OBrien

Chapter
10
Developing
e-Business
Solutions
Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 Chapter 10

Development Methods
Project Management
Change Management
 James A. OBrien Introduction to Information Systems Eleventh Edition 3

Chapter Objectives
Use the systems development process to
simple business problems.
Identify the activities involved in the
implementation of new information
systems.
Identify several change management
solutions for end user resistance to the
implementation of new e-business
applications.

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 James A. OBrien Introduction to Information Systems Eleventh Edition 5

Key Terms
Project Management
On Demand or Self-service
Value on Investment

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 Project Definition

Temporary undertaking to create a unique

product or service with a defined start and end
point and specific objectives that, when attained,
signify completion.
Project Management Terms, J. Leroy Ward, ESI International, Arlington Virginia, 2000
 James A. OBrien Introduction to Information Systems Eleventh Edition 7

3 Approaches
Systems Approach
Prototyping (RAD)
End User Development

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 James A. OBrien Introduction to Information Systems Eleventh Edition 8

Systems Approach to Problem Solving

Define
the
Problem

Develop
Monitor and Evaluate
Alternative
Solutions
Results
Select
the
Solution

Design
the
Solution

Implement
the
Solution
Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 James A. OBrien Introduction to Information Systems Eleventh Edition 9

Traditional Systems Development Life Cycle

Understand the Systems Investigation
Business Product:
Problem or Feasibility Study
Opportunity
Develop an Systems Analysis
Information Product:
System Functional Requirements
Solution
Systems Design
Product:
System Specifications

Implement Systems Implementation

the Information Product:
System Operational System
Solution
Systems Maintenance
Product:
Improved System

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 James A. OBrien Introduction to Information Systems Eleventh Edition 10

Prototyping Process
Identify an End
User's Information
Requirements

Develop
Information System
Prototypes
Prototyping
Cycle

Revise the Prototypes

to Better Meet End
User Requirements

Maintenance
Cycle
Use and Maintain
the Accepted
System

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 James A. OBrien Introduction to Information Systems Eleventh Edition 11

End User Development

Controls
What controls
are needed?

Processing
Input Output
What operations
What data What information
on the input
is required? is needed?
is required?

Storage
Will the
application need
to store data?

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 Projects
Typically address a significant change in business
requirements or in system architecture
Address a new business need, or needs which have
changed significantly
Typically result in the purchase or development of new
hardware and/or software, and may involve
replacement of existing systems
Require more than 40 business hours to perform
May require separate funding and resource scheduling
 PROJECT or CHANGE REQUEST?

New Business Y Budget $$$ Y

Start Need ? Required ?

N N
Decision Tree

Y >40 Y
Change ? PROJECT
ManHours?

CHANGE N Multi-Discipline Y
REQUEST Support ?
 Project Phases
I. Project Initiation
II. Requirements (Functional)
III. Logical Design (Technical)
IV. Physical Design (Technical)
V. Build (Development)
VI. Test (Quality Assurance)
VII. Implement
VIII. Post-Implementation
 Project Responsibilities
Start

N N
Project
Project Y Reqmnts Y Y Single Y Y Y
Initiation
Approved? Kick-Off
Clear
Approved
Solution
Approved Develop A
Mtg

N N N N

Purchase/
Require- Logical
ments Design
Config/ B
Test Install
B

Build
Physical Y Y Acceptance Y Implemen- Y
A Design
Approved & Approved
Test
Approved
tation
Approved C
Test

N N N N

Post
Determine Recovery
C Implemen- End Action Procedure
tation

Legend: Cust&IMT Customer IMT Sponsor & IMT Cabinet

 I - Project Initiation
Submit Project Request
Log Request
Accept/Reject Request
Prioritize Project
Assign Project
Perform Cost Estimate
Start Project Schedule
Request Go-Forward Approval from IMT Cabinet
& Executive Sponsor

LSV
 II - Requirements
Conduct Kick-Off Meeting
Capture Requirements
Define Business Terms
Assemble Project Team
Estimate Phase-on-Deck
Provide Project Estimate at Completion (EAC)
Revise Project Schedule
Request Go-Forward Approval from IMT Cabinet
& Executive Sponsor

LSV
 James A. OBrien Introduction to Information Systems Eleventh Edition 18

Systems Analysis

Organizational

Key
Areas of
Systems
Analysis

Present Functional
System Requirements

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 III Logical Design
Review Requirements with Team
Establish Technical Parameters
Conduct Existing Systems Architecture Impact Analysis
Conduct Future Systems Architecture Impact Analysis
(Capacity Planning)
Prepare Solution Options
State Solution Recommendation
Review/Adjust Team Membership
Estimate Phase-on-Deck
Adjust Estimate At Completion (EAC)
Revise Project Schedule
Request Go-Forward Approval From IMT Cabinet & Executive
Sponsor
LSV
 James A. OBrien Introduction to Information Systems Eleventh Edition 20

Systems Investigation

Economic Organizational
Feasibility Feasibility
Can we afford it? Is it a good fit?

Technical Operational
Feasibility Feasibility
Does the Will it be accepted?
capability exist?

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 IV Physical Design
Prepare Technical Specifications
Create Test Plan
Begin Implementation Plan
Review/Adjust Team Membership
Estimate Phase-on-Deck
Adjust Estimate At Completion (EAC)
Revise Project Schedule
Request Go-Forward Approval from IMT Cabinet &
Executive Sponsor

LSV
 Guiding Principles
Information Architect - Interoperability
Stewardship
View solution offerings as an opportunity
to converge data and/or technologies
Commitment to Open Standards
Web browser based end user interface
Cross platform support
 James A. OBrien Introduction to Information Systems Eleventh Edition 23

Evaluating Hardware and Software

Hardware Evaluation Software Evaluation
Factors Factors
Performance Quality
Cost Efficiency
Reliability Flexibility
Compatibility Security
Technology Connectivity
Ergonomics Language
Connectivity Documentation
Scalability Hardware
Software Efficiency
Support
Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 James A. OBrien Introduction to Information Systems Eleventh Edition 24

Evaluating IS Services
IS Evaluation Factors
Performance
Systems Development
Maintenance
Conversion
Training
Backup
Accessibility
Business Position
Hardware
Software

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 V Build & Test
Build Solution
Test Solution
Identify Customer Acceptance Test Team
Estimate Phase-on-Deck
Adjust Estimate At Completion (EAC)
Revise Project Schedule
Request Go-Forward Approval From IMT Cabinet
& Executive Sponsor

LSV
 James A. OBrien Introduction to Information Systems Eleventh Edition 26

The Implementation Process

Implementation
Activities

Development
System End User
Acquisition and
Testing Training
Modification

System
Docu- Conversion
mentation

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 James A. OBrien Introduction to Information Systems Eleventh Edition 27

Implementing New Systems

Implementation Activities

Acquisition
Software Development
Training
Testing
Documentation
Conversion

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 James A. OBrien Introduction to Information Systems Eleventh Edition 28

Installation Conversion Methods

Old System
Parallel
New System

Old System New System Pilot

Old System New System Phased

Old System New System Plunge

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 VI Customer Acceptance Test
Conduct Customer Acceptance Test
Estimate Phase-on-Deck
Adjust Estimate At Completion (EAC)
Revise Project Schedule
Request Go-Forward Approval From IMT Cabinet
& Executive Sponsor

LSV
 VII - Implementation
Finalize Implementation Plan
Create End-User Documentation
Formalize System Documentation
Train Support Group(s)
Train Customer(s)
Communicate, Communicate, Communicate
Deploy Solution/System
Notify Customers of System Availability

LSV
 VIII - Post-Implementation
Perform any clean-up necessary
The Project Lead will conduct meetings with the
requestor & team to discuss/document areas of future
opportunity and to highlight those things that went well

Close Project
Sponsorship sign-off
Close Project Account
Prepare Project Summary
Lessons Learned
Measurable and can be Implemented
Project Costs
LSV
 James A. OBrien Introduction to Information Systems Eleventh Edition 32

Managing Organizational Change

Executive
Vision
Change Organizational
Management Design

Organization
Mission
and Role

Measurement Core
and Competencies
Rewards Development
Work
Redesign

Irwin/McGraw-Hill Copyright 2002, The McGraw-Hill Companies, Inc. All rights reserved.
 Close Initiate
Request Request

Information & Media Technology

CHANGE
Satisfy Log
Request MANAGEMENT Request

Prioritize Approve
Request Request
 Objectives
Coordination Of Change Management Activities
Communication Of Planned Changes
Notification Of Scheduled/Failed Changes
Use Of Standardized Methods And Procedures
Auditing Mechanisms And Processes For
Reviewing Changes After They Have Taken Place
Management Reporting
 Change Request - Definition
A written submission from an IMT client, or staff
member, to alter a Production IMT system/service
Enterprise Resource Planning system (i.e. IFAS)
Including any functionality integrated with ERP
Network Systems
Servers
Telecom Systems
Etceteras
Usually performed by a single IMT work group
Estimated effort less than 40 hours
AOP Budget Dollars Approved
 James A. OBrien Introduction to Information Systems Eleventh Edition 36

Chapter Summary
Business professionals and IS specialists use
a systems approach to help them develop
information system solutions to meet e-
business needs.
The application development capabilities built
into many end user software packages have
made it easier for end users to develop their
own e-business applications.
Business professionals should know how to
evaluate IT products for acquisition. IT vendor
proposals should be based on specifications
developed during the design phase.

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