5/23/2021
• Activities that occur before the system is
turned over to its users
• Involves project closedown
• Considered to be expensive and time‐
consuming
Its purpose is to:
• Build a properly working system
• Install it in the organization
• Replace the old systems and work methods
• Finalize system and user documentation
• Train users
• Prepare support systems to assist users
1
5/23/2021
PLANNING
MAINTENANCE
ANALYSIS
IMPLEMENTATION
DESIGN
TESTING
CODING
The process of moving from the current information
system to the new one.
Constraints when installing new system and making it
operational:
• Cost
• Customer relations
• Employee relations
• Logistical complexity
• Overall exposure to risk
Other important issues to consider when planning
installation:
• Incurring costs operating both systems in parallel
• Detecting and correcting errors in the new system
• Potentially disrupting the company and its IS operations
• Training personnel and familiarizing customers with new
procedures
2
5/23/2021
DIRECT INSTALLATION
Changing over from the old information
system to a new one by turning off the old
system when the new one is turned on
• Advantage: Simplicity • Disadvantage: Risk
DIRECT INSTALLATION
Typically used under one or both of the following
conditions:
• The new system is not replacing an older system
(automated or manual).
• Downtime of days or weeks can be tolerated
DIRECT INSTALLATION TIMELINE
CURRENT
SYSTEM
INSTALL
NEW SYSTEM
NEW SYSTEM
3
5/23/2021
PARALLEL INSTALLATION
Running the old information system and the new
one at the same time until management decides
the old system can be turned off.
The time allotted is often determined ahead and
limited to minimize the cost of dual operation.
PARALLEL INSTALLATION
Advantage:
• Relatively low risk of system failure and the negative
consequences that might result from that failure
Disadvantage:
• Cost
PARALLEL INSTALLATION TIMELINE
CURRENT SYSTEM
INSTALL
NEW SYSTEM
NEW SYSTEM
4
5/23/2021
PHASED INSTALLATION
Installs a new system and makes it operational in a
series of steps or phases.
This can be combined with parallel installation.
PHASED INSTALLATION
Advantage: Reduced risk
Disadvantage: Increased complexity
Useful mainly when a system is large, complex, and
composed of relatively independent subsystems
DIRECT INSTALLATION TIMELINE
CURRENT CURRENT SYSTEM CURRENT SYSTEM WITHOUT
SYSTEM WITHOUT MODULE 1 MODULE 1 & 2
INSTALL INSTALL
MODULE 1 MODULE 2
NEW MODULE 1
NEW MODULE 2
5
5/23/2021
• Provides information to users on how a system is
operated and maintained
• Provides information required for future
modifications or re‐implementation
• Is an important activity but often overlooked in
implementation
Types of Documentation
System Documentation
• Records detailed information about a system’s
design specifications, its internal workings, and
its functionality
• Provide information to designers and
developers who will maintain or re‐implement
the system
Types of Documentation
System Documentation
• Can be divided into two types:
• Internal documentation
• External documentation
• Should be managed actively for it to remain effective
• Mirrors the system itself
• Should be updated whenever changes are made in
the system
6
5/23/2021
Types of Documentation
User Documentation
• Provides an ongoing support for end users of
the system:
• Written or other visual information about an
application system
• How it works
• How to use it
Types of Documentation
User Documentation Topics Covered
• Software startup and shutdown
• Keystroke, mouse, or command sequences required to
perform specific functions
• Program functions required to implement specific
business procedures(e.g., steps followed to enter a new
customer order)
• Common errors and ways to correct them
Types of Documentation
User Documentation
Contains the following:
• Table of contents
• General description of the purpose and function of the
program or system
• Glossary
• Index
7
5/23/2021
Example of Electronic User Documentation
Types of Documentation
Reasons why organizations fail to make comprehensive
high‐quality user documentation:
A. The assumption that trained programmers can examine
source code, figure out how the system works, and train
users as considered necessary.
B. The assumption that the users trained during system
implementation will informally pass on their knowledge
to future users
Types of Documentation
Reasons why organizations fail to make comprehensive
high‐quality user documentation:
C. The lack of resources and special skills needed to
develop documentation and keep it up‐to‐ date
8
5/23/2021
USER TRAINING AND SUPPORT
➢ Two aspects of an organization’s computing infrastructure:
• Training • Support
➢ Computer Infrastructure
• All of the resources and practices necessary to aid people
adequately use computer systems to do their primary work
➢ Classification of users:
• End users
• System operators
USER TRAINING AND SUPPORT
➢ Some of the typical activities done by end users:
• Create records or transactions
• Modify database contents
• Generate reports
• Query database
• Import or export data
USER TRAINING AND SUPPORT
➢ Typical activities done by system operators:
• Start and stop the system
• Query system status
• Back up data to archive
• Recover data from archive
• Install or update software
9
5/23/2021
USER TRAINING AND SUPPORT
➢ Characteristics of audience that affect training are as
follows:
• Frequency and duration of system use
• Need to understand the system’s business context
• Existing computer skills and general proficiency
• Number of users
USER TRAINING AND SUPPORT
➢ Methods for user support:
• On‐line documentation and troubleshooting
• Resident experts
• Help Desk
• Technical support
10