CHAPTER 5.

SYSTEM
IMPLEMENTATION
AND SUPPORT

1
Learning Outcome
At the end of this chapter, student should be
able to :
5.3 Explain System implementation
◦ List main steps in system implementation
◦ Explain system installation and evaluation

5.4 Understand System support and security

◦ Identify user support
◦ Explain various types of maintenance
◦ Identify tools for system maintenance
◦ Explain system security and backup

2
SYSTEM IMPLEMENTATION
 System implementation is the development,
installation and testing of system components
and delivery of that system into production.
 The purpose of system implementation is to
build a system, install it, replace and old systems,
preparing system and user documentation and
train users.

3
SYSTEM IMPLEMENTATION
 Implementation is a process of
◦ Coding
◦ Testing
◦ Installation
◦ Documentation
◦ Training and Support

 These steps are based on the design specification.

 All the requirements of the system, such as input,

processing, output equipment etc. are provided by
design specification.
4
MAIN STEPS IN SYSTEM
IMPLEMENTATION

5
6
7
8
9
10
11
12
13
14
 SYSTEM INSTALLATION &
EVALUATION

 Remaining steps in systems implementation:

◦ Prepare a separate operational and test
environment.
◦ Provide training for users, managers, and IT staff.
◦ Perform data conversion and system changeover.
◦ Carry out post-implementation evaluation of the
system.
◦ Present a final report to management

15
OPERATIONAL AND TEST
ENVIRONMENTS

16
 OPERATIONAL AND TEST
ENVIRONMENTS
 The operational environment includes hardware
and software configurations and settings, system
utilities, telecommunications resources, and any
other components that might affect system
performance.

 If you have to build or upgrade network

resources to support the new system, you must
test the platform rigorously before system
installation begins.

17
 TRAINING
 Training Plan
◦ The three main groups for training are users, managers,
and IT staff.
◦ You must determine how the company will provide
training.

 Vendor Training
o Often gives the best return on your training dollars
o If the system includes the purchase of software or
hardware, then vendor-supplied training is one of the
features you should investigate in the RFPs (requests
for proposal) and RFQs (requests for quotation) that
you send to potential vendors.
o Often gives the best return on your training dollars. 18
TRAINING

19
 TRAINING
 Outside Training Resources
◦ Many training consultants, institutes, and firms are
available that provide either standardized or customized
training packages

 Training Tips
o Train people in groups, with separate training programs
for distinct groups.
o Select the most effective place to conduct the training.
o Provide for learning by hearing, seeing, and doing.
o Prepare effective training materials, including interactive
tutorials.
o Rely on previous trainees. 20
 DATA CONVERSION

 Data Conversion Strategies

◦ The old system might be capable of exporting data in
an acceptable format for the new system or in a
standard format such as ASCII or ODBC.
◦ If a standard format is not available, you must develop
a program to extract the data and convert it.
◦ Often requires additional data items, which might
require manual entry.

21
 DATA CONVERSION

 Data Conversion Security and Controls

◦ You must ensure that all system control measures are
in place and operational to protect data from
unauthorized access and to help prevent erroneous
input.
◦ Some errors will occur.
◦ It is essential that the new system be loaded with
accurate, error-free data.

22
 SYSTEM CHANGEOVER

 System changeover is the process of putting

the new information system online and retiring
the old system.
 Changeover can be rapid or slow, depending
on the method.
 The four changeover methods:
◦ direct cutover
◦ parallel operation,
◦ pilot operation
◦ phased operation

23
24
 SYSTEM CHANGEOVER

 Direct Cutover
◦ Changeover from the old system to the new system to
occur immediately when the new system becomes
operational.
◦ Direct cutover usually is the least expensive changeover
method because the IT group has to operate and
maintain only one system at a time.
◦ Involves more risk than other changeover methods.
◦ Companies often choose the direct cutover method for
implementing commercial software packages.
◦ Cyclical information systems usually are converted using
the direct cutover method at the beginning of a quarter,
calendar year, or fiscal year.
25
 SYSTEM CHANGEOVER

 Parallel Operation
◦ Changeover method requires that both the old and the
new information systems operate fully for a specified
period.
◦ Data is input into both systems, and output generated by
the new system is compared with the equivalent output
from the old system.
◦ When users, management, and the IT group are satisfied
that the new system operates correctly, the old system is
terminated.

26
 SYSTEM CHANGEOVER

 Pilot Operation
◦ The group that uses the new system first is called the
pilot site.
◦ The old system continues to operate for the entire
organization.
◦ After the system proves successful at the pilot site, it is
implemented in the rest of the organization, usually using
the direct cutover method.
◦ Is a combination of parallel operation and direct cutover
methods.

27
 SYSTEM CHANGEOVER

 Phased Operation
◦ Changeover method allows you to implement the new
system in stages, or modules.
◦ You give a part of the system to all users.
◦ The risk of errors or failures is limited to the
implemented module only.
◦ Is less expensive than full parallel operation.
◦ Is not possible, however, if the system cannot be
separated easily into logical modules or segments.

28
 SYSTEM SUPPORT AND
SECURITY
 User Support
◦ User training
◦ Help desk

29
 SYSTEM OPERATION AND
MAINTENANCE
 System operation and maintenance is the last
phase in System Development Life Cycle – SDLC.
 It starts when system operates and goes through
the system life cycle.
 When system operates it need to be maintain to
fulfil the business requirement that always change.

30
 MAINTENANCE
 Maintenance is changes that are made towards a system to
increase its functionality.

 Maintenance activity includes program modification,

procedure or documentation to produce a good and
correct system.

 Adapt with the changes made to a system. After system

installation, analyst should help and maintain a system so
that it operates well. Is a continuous process.

 There are 4 types of maintenance:

◦ Corrective maintenance
◦ Adaptive maintenance
◦ Perfection maintenance
◦ Preventive maintenance
31
 Corrective Maintenance

 Changes are made to a system to correct

mistakes in design, program or implementation.
 Test and correct errors in operating system.
 Usually needed to solve issues about changes in
maintenance.

32
 Adaptive Maintenance

 Changes are made to a system to add new

features and to increase its capabilities or
achievements.
 Usually needed when business environment
changes, example product or new services, new
production techniques or help about new web base
operation.

33
 Perfective Maintenance

 Changes are made to increase system

functionality base on changes in business
requirements towards technology to ensure the
system is efficient, trustable and established.

34
 Preventive Maintenance

 Changes are done to a system, which operates to

lessen problems, which might occur in future.
 Need analysis towards place on where the
problem might occur.
 To increase the user satisfaction.

35
36
 SYSTEM MAINTENANCE
TOOLS
 You can use automated tools that provide valuable
assistance during the operation and support phase.
 Many CASE tools include system evaluation and
maintenance features, including the following
examples:
◦ Performance monitor that provides data on program
execution times.
◦ Program analyzer that scans source code, provides data
element cross-reference information, and helps evaluate the
impact of a program change.
◦ Interactive debugging analyzer that locates the source of a
programming error.
◦ Reengineering tools.
◦ Automated documentation.
◦ Network activity monitor.
◦ Workload forecasting tool
37
 SYSTEM SECURITY AND BACKUP
 Security is a vital part of every information
system.
 Security protects the system, and keeps it safe,
free from danger, and reliable.
 In a global environment that includes many types
of threats and attacks, security is more important
than ever.
 This section includes a discussion of system
security concepts, risk management, and common
attacks against the system.

38
 SYSTEM SECURITY CONCEPTS

Prevents unauthorized users

from creating, modifying, or
deleting information

Ensures that authorized users

have timely and reliable access
to necessary
information.

Protects information from

unauthorized disclosure and
safeguards privacy. 39
 SYSTEM SECURITY AND BACKUP

 Backup refers to copying data at prescribed intervals, or

continuously.
 Recovery involves restoring the data and restarting the
system after an interruption.
 An overall backup and recovery plan that prepares for a
potential disaster is called a disaster recovery plan.
 Backup policy, which contains detailed instructions and
procedures.
 An effective backup policy can help a firm continue
business operations and survive a catastrophe.
 The backup policy should specify backup media, backup
types, and retention periods.

40
 SYSTEM SECURITY AND BACKUP

 BACKUP MEDIA
 Backup media can include tape, hard drives, optical
storage, and online storage.

 BACKUP TYPES
 Backups can be full, differential, incremental, or continuous

 RETENTION PERIODS
◦ Backups are stored for a specific retention period after
which they are either destroyed or the backup media is
reused.
◦ Retention periods can be a specific number of months or
years, depending on legal requirements and company
policy.
◦ Stored media must be secured, protected, and inventoried
periodically.
41
42