View
218
Download
0
Category
Preview:
Citation preview
7/29/2019 CC5001 Week 17 Installation 2013
1/38
Installation:
Systems installationData migration
DeploymentBusiness changeTraining
Documentation
1
7/29/2019 CC5001 Week 17 Installation 2013
2/38
Technical issues: installing IS components
hardware
software
network / communications
data-migration / set-up
Installation issues
2
7/29/2019 CC5001 Week 17 Installation 2013
3/38
Social (or human) issues
training users
educating people (selling the system)
business change
Overall deployment strategy
Installation issues
3
7/29/2019 CC5001 Week 17 Installation 2013
4/38
Client/server architecture
Clientconnects to serverforrequired remote processing
e.g. data access
Local processing
on the Client(user workstation)
Remote
processing
on the
Server
Processing is sharedbetween the clientand the server.
4
7/29/2019 CC5001 Week 17 Installation 2013
5/38
Categories of computer software
Chaffey (2003) categorises software as follows:
Systems software
Operating systems (O/S) client O/S, server O/S, network O/S
Utility programs
Development programs
Applications software
General-purpose software
Application-specific software
5
7/29/2019 CC5001 Week 17 Installation 2013
6/38
Technical installation/configuration
May need to install and configure hardware
the server(s)
the client(s)
May need to install (part of) a network
(for many IS projects, some/all hardware and network may be in place)
Will need to install: the server application software
the database
the client application software
6
7/29/2019 CC5001 Week 17 Installation 2013
7/38
Software modules
Application-specific software often developed in a
modular fashion, so for an accounting system:
Purchase Ledger module
Sales Ledger module
Nominal Ledger module
etc. May be possible to implement/install somemodules
without installing all modules
7
7/29/2019 CC5001 Week 17 Installation 2013
8/38
Software migration
How is software migrated to an operational
environment?
Different software environments - typically
Migrating software through these different
environments is Configuration Management;
control of this process is Change Control
Development Test Production
8
7/29/2019 CC5001 Week 17 Installation 2013
9/38
Data migration and set-up
Where does initial application data come from?
Existing paper records
Existing information systems
New data, e.g. new coding scheme devised for new IS
Data may be converted from existing IS, using a conversion
program - maybe using ETL (extract-transform-load) software
One-off data conversion or regular interface?
Existing
system TransformationNew
System
9
7/29/2019 CC5001 Week 17 Installation 2013
10/38
Data migration and set-up
What might transformation involve?
Extract data from another database
change structure
change format
add new attribute(s)
remove existing attribute(s)
change sequence (attributes in different order)
10
7/29/2019 CC5001 Week 17 Installation 2013
11/38
Data migration and set-up
Staff details: old record
Staff details: new record
Staff
id
Name Address DoB Grade Marital
status
01015 Jones,Betty
195 Long Lane, E14 7XD 12.10.60 SEO Married
Staff
id
Last
name
First
name
Address Post
code
DoB Grade Site
01015 Jones Betty 195 LongLane
E14 7XD 12/Oct/1960 4 HeadOffice
11
7/29/2019 CC5001 Week 17 Installation 2013
12/38
Data migration and set-up
Staff
id
Name Address DoB Grade Marital
status
01015 Jones,
Betty
195 Long Lane, E14 7XD 12.10.60 SEO Married
Staffid
Lastname
Firstname
Address Postcode
DoB Grade Site
01015 Jones Betty 195 LongLane
E14 7XD 12/Oct/1960 4 HeadOffice
change of structure: name
12
7/29/2019 CC5001 Week 17 Installation 2013
13/38
Data migration and set-up
Staff
id
Name Address DoB Grade Marital
status
01015 Jones,
Betty
195 Long Lane, E14 7XD 12.10.60 SEO Married
Staffid
Lastname
Firstname
Address Postcode
DoB Grade Site
01015 Jones Betty 195 LongLane
E14 7XD 12/Oct/1960 4 HeadOffice
change of structure: address
13
7/29/2019 CC5001 Week 17 Installation 2013
14/38
Data migration and set-up
Staff
id
Name Address DoB Grade Marital
status
01015 Jones,
Betty
195 Long Lane, E14 7XD 12.10.60 SEO Married
Staffid
Lastname
Firstname
Address Postcode
DoB Grade Site
01015 Jones Betty 195 LongLane
E14 7XD 12/Oct/1960 4 HeadOffice
change of format: date of birth
14
7/29/2019 CC5001 Week 17 Installation 2013
15/38
Data migration and set-up
Staff
id
Name Address DoB Grade Marital
status
01015 Jones,
Betty
195 Long Lane, E14 7XD 12.10.60 SEO Married
Staffid
Lastname
Firstname
Address Postcode
DoB Grade Site
01015 Jones Betty 195 LongLane
E14 7XD 12/Oct/1960 4 HeadOffice
change of format: grade
15
7/29/2019 CC5001 Week 17 Installation 2013
16/38
Data migration and set-up
Staff
id
Name Address DoB Grade Marital
status
01015 Jones,
Betty
195 Long Lane, E14 7XD 12.10.60 SEO Married
Staffid
Lastname
Firstname
Address Postcode
DoB Grade Site
01015 Jones Betty 195 LongLane
E14 7XD 12/Oct/1960 4 HeadOffice
remove existing attribute: marital status
16
7/29/2019 CC5001 Week 17 Installation 2013
17/38
Data migration and set-up
Staff
id
Name Address DoB Grade Marital
status
01015 Jones,
Betty
195 Long Lane, E14 7XD 12.10.60 SEO Married
Staffid
Lastname
Firstname
Address Postcode
DoB Grade Site
01015 Jones Betty 195 LongLane
E14 7XD 12/Oct/1960 4 HeadOffice
add new attribute: site
17
7/29/2019 CC5001 Week 17 Installation 2013
18/38
Data migration and set-up
Staff
id
Name Address DoB Grade Marital
status
01015 Jones,
Betty
195 Long Lane, E14 7XD 12.10.60 SEO Married
Staffid
Lastname
Firstname
DoB Address Postcode
Grade Site
01015 Jones Betty 12/Oct/1960 195 LongLane
E14 7XD 4 HeadOffice
change sequence: DoB before address details
18
7/29/2019 CC5001 Week 17 Installation 2013
19/38
Deployment options
Time
Existing system Live date New system
Direct changeover / Immediate cut-over
Based on Chaffey (2003) 19
7/29/2019 CC5001 Week 17 Installation 2013
20/38
Deployment options
Time
Existing system Live date New system
Parallel running
Based on Chaffey (2003) 20
7/29/2019 CC5001 Week 17 Installation 2013
21/38
Deployment options
Time
Existing system Live date New system
Modules
A
B
C
Phased: Modules
Based on Chaffey (2003) 21
7/29/2019 CC5001 Week 17 Installation 2013
22/38
Deployment options
Time
Existing system Live date New system
Pilot
Areas/regions
1
2
3
Phased: Geographic
Based on Chaffey (2003) 22
7/29/2019 CC5001 Week 17 Installation 2013
23/38
Deployment options
Time
Existing system Live date New system
Pilot running
Based on Chaffey (2003)Pilot of new system 23
7/29/2019 CC5001 Week 17 Installation 2013
24/38
Deployment options
Time
Existing system Live date New system
Modules
Pilot
Areas/regions
A
B
C
1
2
3
Parallel running
Phased: Modules
Phased: Geographic
Based on Chaffey (2003)
Pilot running
Pilot of new system
Direct changeover / Immediate cut-over
24
7/29/2019 CC5001 Week 17 Installation 2013
25/38
Deployment options
Consider the impact in terms of: staffing
workload
cost
time
inconsistencies
corroboration
correction updates
discontinuing one of the systems
when selecting deployment options25
7/29/2019 CC5001 Week 17 Installation 2013
26/38
Business issues duringinstallation
Business continuity
Cannot stop all work to install new system
loss of business
loss of customers
loss of goodwill
Establishing success of the installation
Reconciliation of converted data
Key process testing
Backup (contingency) plan
what to do if things go wrong...
Business and organisational change26
7/29/2019 CC5001 Week 17 Installation 2013
27/38
Business and organisational change
Any new system causes disruption to staff:
changesto patterns of work
newroles
new/additionalresponsibilities
riskof redundancy
feelthreatenedby new technology
however good the new system, users will get it wrongsometimes (make mistakes)
need for training(fit into work schedule)
the new system wont be perfecteither!
27
7/29/2019 CC5001 Week 17 Installation 2013
28/38
Phases of change
Denial
Resistance Exploration
Confidence
Launch Communication Education Exploitation
Resistance to change:
Managing change:
Source: Cadle and Yeates, 2001 28
7/29/2019 CC5001 Week 17 Installation 2013
29/38
Phases of change
Denial
Resistance Exploration
Confidence
Launch Communication Education Exploitation
Resistance to change:
Managing change:
Source: Cadle and Yeates, 2001 29
7/29/2019 CC5001 Week 17 Installation 2013
30/38
Phases of change
Denial
Resistance Exploration
Confidence
Launch Communication Education Exploitation
Resistance to change:
Managing change:
Source: Cadle and Yeates, 2001 30
7/29/2019 CC5001 Week 17 Installation 2013
31/38
Phases of change
Denial
Resistance Exploration
Confidence
Launch Communication Education Exploitation
Resistance to change:
Managing change:
Source: Cadle and Yeates, 2001 31
7/29/2019 CC5001 Week 17 Installation 2013
32/38
Change programme
Systems development
Support
Get users involved early... throughout systemsdevelopment - requirements, design, testing, etc.
A business change programme should run alongside the
systems development project and continue after it has
been completed
32
7/29/2019 CC5001 Week 17 Installation 2013
33/38
Change programme
Launch Communication Education
Project management
Involve key user(s) in managing the project...identify a user project manager to co-ordinate
business change management
Identify championsand change agents
Education: skilling the end-users and selling the system
.....................
.......................Exploitation
33
7/29/2019 CC5001 Week 17 Installation 2013
34/38
Training
Need to consider:
Whoto train?
Identify the users What do the usersneedto know?
Whatto train?
Different users have different requirements
Tailor training for specific user groups
34
7/29/2019 CC5001 Week 17 Installation 2013
35/38
Training
Planningthe training
Who? How? Where?
Development team?
Professional trainers? Classroom training away from work environment
On the job training
Computer-based training
CD, DVD, on-line, in-built tutorial, FAQs?
Conductingthe training Roll out across the organisation
Train the trainers, etc.
Timing when is the system going live? 35
7/29/2019 CC5001 Week 17 Installation 2013
36/38
Documentation
Document the system
For maintenance
Why was this done?
How was this this done?
Why was it done this way?
(speed, efficiency, elegance of solution, ease of maintenance,
recursion versus iteration, memory versus processing...)
For end-users How do I get the system to do ...?
What does this error message mean?
36
7/29/2019 CC5001 Week 17 Installation 2013
37/38
Summary
Need to consider Technical aspects
Hardware
Software
Data
Documentation
Human aspects
Impact on staff
Workload
(especially if running new & old systems in parallel)
Training
Documentation
Impact on business37
7/29/2019 CC5001 Week 17 Installation 2013
38/38
Further reading
Beynon-Davies, P., 2002, Information Systems, Palgrave
Cadle J. & Yeates D., 2001, Project Management forInformation Systems, 3rd ed., FT Prentice Hall
Chaffey, D. (ed.), 2003, Business Information Systems, 2nded., FT Prentice Hall
Curtis, G., 1998, Business Information Systems, 3rd ed.,Addison-Wesley
and see references page 508 Chaffey (2003)
Recommended