Changeover

1
MIS 161 Systems Development Life Cycle
II Lecture 6System Changeover Issues
2
Changeover Process

• Scheduling process
• Weekends, nights, or holidays
• Notification to customers
• external
• internal
• Activity phase-down
• only priority transactions

3
Elements of a Scheduling
4
Scheduling Process

• What activities will be performed when and by
  whom
• Technical aspects
• Installing hardware and software
• Converting data
• Organizational aspects
• Training users on the system
• Motivating employees to use the new system to aid
  in their work
• Change management

5
Changeover Process

• File conversion
• download old system
• upload new system
• System changeover
• New system priming
• start feeding transactions

6
Parallel Cut-Over
For a time both old and new systems are used.
The old is abandoned when the new is proven
fully capable
OLD SYSTEM
NEW SYSTEM
Parallel Period
7
Direct (Crash) Changeover
The new system instantly replaces the old
OLD SYSTEM
NEW SYSTEM
Cut-over Date
8
Staged Changeover
The system is converted in stages
O L D
N E W
9
Changeover Factors

• Costs
• System criticality
• User computer experience
• System complexity
• User resistance
• Time

10
Institutionalization of the System

• Provide support
• Assistance in using the system
• Provide maintenance
• Repair or fix discovered bugs or errors
• Add minor enhancements to provide added value
• Assess the project
• Analyze what was done well
• Discover what activities need improvement in the
  future

11
Types of System Support

• On-demand training at time of user need
• Online support
• Frequently asked questions (FAQ)
• Help desk
• Phone service for known issues
• Level 2 Support

12
Training

• New system training must be performed
• Analysts must consider
• Who needs to be trained
• Who will train them
• Objectives of training
• Methods of instruction to be used
• Sites
• Materials

13
Sources of Training

• Possible sources of training for users of
  information systems include
• Vendors
• Systems analysts
• External paid trainers
• In-house trainers
• Other system users

14
Maintaining/Modifying the System

• Problem reports from the operations group
• Requests for enhancements from users
• Requests from other systems development projects
• Change requests from senior management

15
Project Assessment

• Important for continued project improvement
• Especially important for junior personnel to
  improve quickly

16
Project Team Review

• Each member prepares 2-3 page document regarding
  her or his actions during the project
• Focus on improvement not penalties
• Excellent behaviors are acknowledged and diffused
  to others
• Team leader summarizes and distributes lessons
  learned

17
System Review

• Examine the extent to which the costs and
  benefits of the system are realized
• Use this information to help in more accurately
  estimating costs and benefits for future projects