Professional Documents
Culture Documents
Information Systems
Fifth Edition
Chapter 13
Acquiring Information Systems And
Applications
Copyright © 2014 John Wiley & Sons, Inc. All rights reserved.
13-2
Introduction
Learning Objectives
Discuss the different cost/benefit analyses that
companies must take into account when formulating an
IT strategic plan.
Discuss the four business decisions that companies
must make when they acquire new applications.
Enumerate the primary tasks and the importance of
each of the six processes involved in the systems
development life cycle.
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-3
Introduction
Learning Objectives
Describe alternative development methods and the tools
that augment development methods.
Analyze the process of vendor and software selection.
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-4
Introduction
Chapter Outline
Planning for and Justifying IT Applications
Strategies for Acquiring IT Applications
The Traditional Systems Development Life Cycle
Alternative Methods and Tools for Systems
Development
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-5
Introduction
What’s in IT for Me?
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-6
Tweak or Trash
The Problem
When the time comes to upgrade information
technology equipment and systems, which is the better
strategy
To repair what you already have by patching and
tweaking systems
software to keep them operating, or to replace (a.k.a.
trash) your old technology
Start with an entirely new system
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-7
Tweak or Trash
The IT Solution
The process of revamping its IT infrastructure
Kicked off the replacement process;
Establishing a coherent IT strategy
Building its own independent IT capabilities
Shifted its focus to cloud computing
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-8
Tweak or Trash
The Results
To trash not tweak and then to employ cloud computing
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-9
Tweak or Trash
What We Learned from This Case
Competitive organizations move as quickly as they can
to acquire new information technologies or modify
existing ones when they need to improve efficiencies
and gain strategic advantage
Acquisition goes beyond building new systems in-house
IT resources involve far more than software and
hardware
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-10
Fig_13-1
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-13
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-16
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-17
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-19
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-26
Life Cycle
Systems development life cycle (SDLC)
The traditional systems development method
That organizations use for large-scale IT projects
Structured framework that consists of sequential processes
Systems investigation
Systems analysis
Systems design
Programming and testing
Implementation
Operation and maintenance
Fig_13-4
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
The Traditional Systems Development 13-29
Life Cycle
Development teams typically;
Users
Employees from all functional areas and levels who interact with the
system directly or indirectly
Systems analysts
IS professionals who specialize in analyzing and designing
Programmers
IS professionals who modify existing computer programs or write new
programs
Technical specialists
Experts on a certain type of technology
Systems stakeholders
Everyone who is affected by changes of IS Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
The Traditional Systems Development 13-30
Life Cycle
Early
stages of
SDLC
Fig_13-5
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
The Traditional Systems Development 13-31
Life Cycle
Advantages and
disadvantages;
SDLC
Prototyping
JAD
Integrated CASE
Rapid Application
Development
End-user Development
Object-oriented
Development
Table_13-2
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
The Traditional Systems Development 13-32
Life Cycle
Systems Investigation
Initial stage in a traditional SDLC;
Understanding the business problem to be solved
Specifying the technical options for the systems
Anticipating the problems
Addresses the business problem (or business opportunity) by
means of;
Feasibility study
The main task in the systems investigation stage
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
The Traditional Systems Development 13-33
Life Cycle
Systems Investigation
Three basic solutions
Do nothing and continue to use the existing system
unchanged
Modify or enhance the existing system
Develop a new system
Provides a rough assessment of the project’s are;
Technical
Economic
Behavioral feasibility
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
The Traditional Systems Development 13-34
Life Cycle
Systems Investigation
Technical feasibility
Determines to develop and/or acquire
Hardware, Software, and Communications components
Economic feasibility
Determines whether the project is an acceptable
Financial risk, and The necessary time and money
Behavioral feasibility
Addresses the human issues
A “go/no-go” decision is reached
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
The Traditional Systems Development 13-35
Life Cycle
Systems Analysis
The process where systems analysts examine the
business problem
The main purpose
To gather information about the existing system in order to
determine the requirements
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
The Traditional Systems Development 13-36
Life Cycle
Systems Design
Describes how the system will resolve the business
problem
Deliverable of the systems design phase is the set of
technical system specifications;
System outputs, inputs, and user interfaces
Hardware, software, databases, telecommunications,
personnel, and procedures
A blueprint of how these components are integrated
Scope creep
Endangers the project’s budget and schedule
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
The Traditional Systems Development 13-37
Life Cycle
Programming and Testing
Programming
Involves translating the design specifications into computer
code
Testing
The process that assesses whether the computer code will
produce the expected and desired results
Intended to detect errors, or bugs, in the computer code
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
The Traditional Systems Development 13-38
Life Cycle
Implementation
The process of converting from an old computer system
to a new one
Direct conversion
The old system is cut off
The new system is turned on
Least expensive
The most risky
The new system does not work
There is no support from the old system
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
The Traditional Systems Development 13-39
Life Cycle
Implementation
Pilot conversion
Introduces the new system in one part
If the assessment confirms
Then the system is implemented in other parts
Phased conversion
Introduces components or phase of the new system
Parallel conversion
The old and new systems operate simultaneously
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
The Traditional Systems Development 13-40
Life Cycle
Operation and Maintenance
Debugging
A process that continues throughout the life of the system
Updating
The system to accommodate changes in business conditions
Adds new functions
The existing system without disturbing its operation
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
Alternative Methods and Tools for 13-41
Systems Development
Joint Application Design A group-based tool for
collecting user
requirements and
creating system designs
Used within the systems
analysis and systems
design stages of the
SDLC
This process saves a
tremendous amount of
time
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
Alternative Methods and Tools for 13-42
Systems Development
Rapid Application Development
A systems-
development
method that can
combine JAD,
prototyping, and
integrated
computer-
assisted software
engineering
(ICASE) tools
Fig_13-6
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
Alternative Methods and Tools for 13-43
Systems Development
Rapid Application Development
Developers use JAD
sessions
Uses ICASE tools to
quickly structure
requirements and
develop prototypes
The prototypes are
developed and
refined
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
Alternative Methods and Tools for 13-44
Systems Development
Agile Development
A software-development methodology that delivers
functionality in rapid iterations
Focuses on
Rapid development
Frequent user contact
Uses scrum approach
Users can change their minds about what they want and need
Acknowledges development problem cannot be fully understood
Maximizing the team’s ability to deliver quickly and effectively
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
Alternative Methods and Tools for 13-45
Systems Development
Agile Development
The primary roles of Scrum;
The Scrum Master – maintains the processes
The Product Owner – represents the business stakeholders
The Team – cross-funtional
During each sprint
Typically a 2- to 4-week period
Planning meeting determines which backlog items
No one is allowed to change the sprint backlog
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
Alternative Methods and Tools for 13-46
Systems Development
End-User Development An approach in
which the
organization’s end
users develop their
own applications
with little or no
formal assistance
from the IT
department
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
Alternative Methods and Tools for 13-47
Systems Development
Tools for Systems Development
Prototyping approach
defines
An initial list of user
requirements
Builds a model of the
system
Refines the system in
several iterations based
on users’ feedback
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
Alternative Methods and Tools for 13-48
Systems Development
Tools for Systems Development
Integrated CASE Tools
Computer-aided software
engineering (CASE)
A group of tools that
automate many of the tasks
in the SDLC
Upper CASE tools
Used to automate the early
stages of the SDLC
Lower CASE tools
Used to automate later
stages in the SDLC
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
Alternative Methods and Tools for 13-49
Systems Development
Tools for Systems Development
Component-Based Development
Uses standard components to build applications
Reusable applications that generally have one specific
function;
A shopping cart
User authentication
A catalog
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
Alternative Methods and Tools for 13-50
Systems Development
Tools for Systems Development
Object-Oriented Development (OO)
Based on a different view of computer systems than the
perception that characterizes traditional development
approaches
Development process for an OO system
A feasibility study and an analysis of the existing system
Objects have properties or data values
Operations are also referred to as behaviors
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
Alternative Methods and Tools for 13-51
Systems Development
Tools for Systems Development
Object-Oriented
Development
Approach enables
OO analysts
Define all the relevant
objects needed for the
new system
Including their
properties and
operations
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.
13-52
Any Questions?
Copyright © 20113 John Wiley & Sons, Inc. All rights reserved.