Documentation 1 Installation issues Technical issues: installing - - PowerPoint PPT Presentation

▶
documentation
SMART_READER_LITE
LIVE PREVIEW

Documentation 1 Installation issues Technical issues: installing - - PowerPoint PPT Presentation

Jul 24, 2023 187 likes •574 views

Installation: Systems installation Data migration Deployment Business change Training Documentation 1 Installation issues Technical issues: installing IS components hardware software network / communications

slide-1
SLIDE 1

Installation:

Systems installation Data migration Deployment Business change Training Documentation

1

slide-2
SLIDE 2
  • Technical issues: installing IS components

– hardware – software – network / communications – data-migration / set-up

Installation issues

2

slide-3
SLIDE 3
  • Social (or human) issues

– training users – educating people (“selling” the system) – business change

  • Overall deployment strategy

Installation issues

3

slide-4
SLIDE 4

Client/server architecture

Client connects to server for required remote processing e.g. data access Local processing

  • n the Client

(user workstation) Remote processing

  • n the

Server Processing is shared between the client and the server.

4

slide-5
SLIDE 5

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

slide-6
SLIDE 6

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

slide-7
SLIDE 7

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 some modules

without installing all modules

7

slide-8
SLIDE 8

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

slide-9
SLIDE 9

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 Transformation New System

9

slide-10
SLIDE 10

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

slide-11
SLIDE 11

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 Long Lane E14 7XD 12/Oct/1960 4 Head Office

11

slide-12
SLIDE 12

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 Staff id Last name First name Address Post code DoB Grade Site 01015 Jones Betty 195 Long Lane E14 7XD 12/Oct/1960 4 Head Office

change of structure: name

12

slide-13
SLIDE 13

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 Staff id Last name First name Address Post code DoB Grade Site 01015 Jones Betty 195 Long Lane E14 7XD 12/Oct/1960 4 Head Office

change of structure: address

13

slide-14
SLIDE 14

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 Staff id Last name First name Address Post code DoB Grade Site 01015 Jones Betty 195 Long Lane E14 7XD 12/Oct/1960 4 Head Office

change of format: date of birth

14

slide-15
SLIDE 15

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 Staff id Last name First name Address Post code DoB Grade Site 01015 Jones Betty 195 Long Lane E14 7XD 12/Oct/1960 4 Head Office

change of format: grade

15

slide-16
SLIDE 16

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 Staff id Last name First name Address Post code DoB Grade Site 01015 Jones Betty 195 Long Lane E14 7XD 12/Oct/1960 4 Head Office

remove existing attribute: marital status

16

slide-17
SLIDE 17

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 Staff id Last name First name Address Post code DoB Grade Site 01015 Jones Betty 195 Long Lane E14 7XD 12/Oct/1960 4 Head Office

add new attribute: site

17

slide-18
SLIDE 18

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 Staff id Last name First name DoB Address Post code Grade Site 01015 Jones Betty 12/Oct/1960 195 Long Lane E14 7XD 4 Head Office

change sequence: DoB before address details

18

slide-19
SLIDE 19

Deployment options

Time Existing system Live date New system

Direct changeover / Immediate cut-over Based on Chaffey (2003)

19

slide-20
SLIDE 20

Deployment options

Time Existing system Live date New system

Parallel running Based on Chaffey (2003)

20

slide-21
SLIDE 21

Deployment options

Time Existing system Live date New system

Modules A B C Phased: Modules Based on Chaffey (2003)

21

slide-22
SLIDE 22

Deployment options

Time Existing system Live date New system

“Pilot” Areas/regions 1 2 3 Phased: Geographic Based on Chaffey (2003)

22

slide-23
SLIDE 23

Deployment options

Time Existing system Live date New system

Pilot running Based on Chaffey (2003)

Pilot of new system

23

slide-24
SLIDE 24

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

slide-25
SLIDE 25

Deployment options

  • Consider the impact in terms of:

– staffing – workload – cost – time – inconsistencies – corroboration – correction – updates – discontinuing one of the systems

when selecting deployment options

25

slide-26
SLIDE 26

Business issues during installation

  • 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 change

26

slide-27
SLIDE 27

Business and organisational change

  • Any new system causes disruption to staff:

– changes to patterns of work – new roles – new/additional responsibilities – risk of redundancy – feel threatened by new technology – however good the new system, users will get it wrong sometimes (make mistakes) – need for training (fit into work schedule) – … the new system won’t be perfect either!

27

slide-28
SLIDE 28

Phases of change

Denial Resistance Exploration Confidence

Launch Communication Education Exploitation

Resistance to change: Managing change:

Source: Cadle and Yeates, 2001

28

slide-29
SLIDE 29

Phases of change

Denial Resistance Exploration Confidence

Launch Communication Education Exploitation

Resistance to change: Managing change:

Source: Cadle and Yeates, 2001 29

slide-30
SLIDE 30

Phases of change

Denial Resistance Exploration Confidence

Launch Communication Education Exploitation

Resistance to change: Managing change:

Source: Cadle and Yeates, 2001 30

slide-31
SLIDE 31

Phases of change

Denial Resistance Exploration Confidence

Launch Communication Education Exploitation

Resistance to change: Managing change:

Source: Cadle and Yeates, 2001 31

slide-32
SLIDE 32

Change programme

Systems development Support

Get users involved early... throughout systems development - requirements, design, testing, etc. A business change programme should run alongside the systems development project… and continue after it has been completed

32

slide-33
SLIDE 33

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 champions and change agents Education: “skilling the end-users” and “selling” the system

..................... ....................... Exploitation

33

slide-34
SLIDE 34

Training

  • Need to consider:

– Who to train?

  • Identify the users
  • What do the users need to know?

– What to train?

  • Different users have different requirements
  • Tailor training for specific user groups

34

slide-35
SLIDE 35

Training

– Planning the 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?

– Conducting the training

  • Roll out across the organisation
  • Train the trainers, etc.
  • Timing – when is the system going live?

35

slide-36
SLIDE 36

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

slide-37
SLIDE 37

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 business

37

slide-38
SLIDE 38

Further reading

  • Beynon-Davies, P., 2002, Information Systems, Palgrave
  • Cadle J. & Yeates D., 2001, Project Management for

Information Systems, 3rd ed., FT Prentice Hall

  • Chaffey, D. (ed.), 2003, Business Information Systems, 2nd

ed., FT Prentice Hall

  • Curtis, G., 1998, Business Information Systems, 3rd ed.,

Addison-Wesley

  • … and see references page 508 Chaffey (2003)

38