Course Name: Information Systems
Strategy - MS2
Module: 5
Module Title: Systems implementation,
testing, and support
Lectures and handouts by:
Brian Friedrich, MEd, CGA, FCCA(UK)
Laura Friedrich, MSc, CGA, FCCA(UK)
2007-8
Module 5 - Table of Contents
Part
Content
1
2
Systems installation and conversion (5.1)
3
Systems maintenance, enhancement, and
reengineering (5.4 - 5.5)
4
Legacy systems issues and Measuring system
benefits (5.6 - 5.7)
5
Assignment Tips
Testing in systems implementation and Quality
assurance in systems development (5.2 - 5.3)
2
Part 1 - Systems installation
and conversion (5.1)
Six activities of systems development (from Topic 3.1)
Topics 4.2 - 4.5
Topic 4.6
Topic 5.1
Topic 5.2
Topic 5.1
Topic 5.4
3
1
Part 1 - Systems installation
and conversion (5.1)
Systems implementation
•
Programming and coding - writing the applications
based on the logical models
•
Installation - putting the hardware and software in
place based on the physical models
•
Conversion- switching from the old system to the
new system
4
Part 1 - Systems installation
and conversion (5.1)
Choose and defend a strategy for converting from an
existing system to a new system, based on
situational factors (Level 1).
Assess the advantages and disadvantages of the four
different conversion strategies (Level 1).
Four strategies for system conversion
•
Parallel
•
Pilot
•
Phased
•
Direct cutover
5
Part 1 - Systems installation
and conversion (5.1)
Parallel conversion
•
Old system continues to be used at the same time
the new system is introduced
•
Both systems run in parallel for a predetermined
amount of time
•
Results from old and new systems are monitored
for differences
•
People gradually increase the amount of time that
they use the new system until eventually the old
system is discontinued
6
2
Part 1 - Systems installation
and conversion (5.1)
Pilot conversion
•
New system is introduced in a single unit or
location for a set period of time before it is installed
in other parts of the organization
•
New system is tested in a controlled way.
7
Part 1 - Systems installation
and conversion (5.1)
Phased conversion
•
New information system is broken down into
smaller functional components
•
Components are brought into operation one at a
time, with each one adding more improvements
and functionality to the overall system
•
Conversion is gradual and incremental
8
Part 1 - Systems installation
and conversion (5.1)
Direct cutover
•
Also called “Abrupt cutover” or “Plunge”
•
Old system is discarded and the new system takes
over all at once
9
3
Part 1 - Systems installation
and conversion (5.1)
Four approaches for system conversion
Parallel, Pilot, Phased, and Direct cutover
10
Part 1 - Systems installation
and conversion (5.1)
Parallel conversion
Advantages
•
•
Allows for a comparison between the new
system and the old:
-
easier to verify accuracy of new system
-
can benchmark to quantify improvements
Redundancy minimizes the risks of operational
and data processing failures
11
Part 1 - Systems installation
and conversion (5.1)
Disadvantages
• The duplication of effort associated with running
two systems is very costly
• Some users will continue to rely fully on the old
system, which will delay the benefits of the new
system
Comments and Risk level
• Considered the least risky conversion approach
• More difficult with large, complex systems
• May be necessary if zero downtime is critical
12
4
Part 1 - Systems installation
and conversion (5.1)
Pilot conversion
Advantages
•
Allows an organization to test out a new system
in a controlled way
•
Limits the amount of disruption and harm a new
system can produce in an organization
•
Success can be used to overcome user
resistance and sell the new system to the rest of
the organization
13
Part 1 - Systems installation
and conversion (5.1)
Disadvantages
•
Creates additional burdens for the IS staff in the
maintenance and support of two different
systems
•
Runs the risk of delaying the full implementation
of a new system because the pilot is constantly
being improved
14
Part 1 - Systems installation
and conversion (5.1)
Comments and Risk level
•
Considered a middle of the road method
designed to minimize risk
•
If you select the easiest site with very positive
conditions for adoption of the system, you may
hide some potential problems - the inverse is
also true
15
5
Part 1 - Systems installation
and conversion (5.1)
Phased conversion
Advantages
•
Easier to manage the risks and costs in the short
term
•
Conversion will be gradual, incremental, and easier
to manage than the other installation approaches
16
Part 1 - Systems installation
and conversion (5.1)
Disadvantages
•
The old and the new systems must be able to work
together seamlessly
•
Completion point can be difficult to define since it
takes place over such a long period of time
Comments and Risk level
•
Considered a middle of the road method designed
to minimize risk by spreading it out over time
•
Works well if new system is an enhancement to old
system
17
Part 1 - Systems installation
and conversion (5.1)
Direct-cutover conversion
Advantages
•
Can be the least expensive of the different
methods and can occur in the quickest time
•
Allows the benefits of the new system to be
realized without delay
•
Users and management have a high interest in
making the new system work because by design
there is no turning back
18
6
Part 1 - Systems installation
and conversion (5.1)
Disadvantages
• The greatest risk is the impact that errors and
failures would have on the organization
Comments and Risk level
• The riskiest strategy for new systems installation
• May be the only option if the old and new
systems cannot co-exist in any form or if
deadlines are immovable
19
Part 2
Testing in systems
implementation and
Quality assurance in
systems development
Topics 5.2 - 5.3
20
Part 2 - Testing in systems implementation and
Quality assurance in systems development (5.2 - 5.3)
Distinguish between the different methods of testing in
systems implementation and formulate strategies to
mitigate the limitations of testing (Level 1).
Two basic phases of testing
1. Program testing
2. Acceptance testing
21
7
Part 2 - Testing in systems implementation and
Quality assurance in systems development (5.2 - 5.3)
Program testing
•
Unit testing - Individual modules of the system are
tested for any potential errors in the code
•
Integration testing - Used to check interoperability
•
System testing - Used to test how all of the
components of the new systems will work under
various conditions including normal and peak loads
22
Part 2 - Testing in systems implementation and
Quality assurance in systems development (5.2 - 5.3)
Acceptance testing
•
•
Involves the actual users of the completed system
and how well it meets their expectations and
requirements
Two sub-phases:
–
Alpha testing - simulated data is used
–
Beta testing - actual data of the completed
system is used; final stage before installation
23
Part 2 - Testing in systems implementation and
Quality assurance in systems development (5.2 - 5.3)
•
Acceptance testing includes:
– Recovery testing examines how the system
responds when it has been made to fail
– Security testing focuses on whether the security
policies have been implemented as intended in
the final system
– Stress testing tries to break the system by
explicitly not following the rules and procedures
as laid out. Stress testing also considers the
performance of the system under heavy usage
conditions
– Performance testing examines the use of the
system in different environments
24
8
Part 2 - Testing in systems implementation and
Quality assurance in systems development (5.2 - 5.3)
Limitations to testing
•
It’s impossible to test a program for every
conceivable condition (see Example 5.2-1)
•
No matter how exhaustive your test, you can’t
guarantee a bug-free system
•
Testing can be a never-ending proposition - there
needs to be a “good enough” point in any testing
program
•
Mitigate through ongoing testing throughout
product life, and through quality assurance to avoid
problems in the first place
25
Part 2 - Testing in systems implementation and
Quality assurance in systems development (5.2 - 5.3)
Distinguish between quality assurance and quality
control (Level 1).
Quality assurance
•
Concerned with the quality of the environment in
which products (information systems) are
developed
Quality control
•
Concerned with the quality of the products
(information systems) themselves
26
Part 2 - Testing in systems implementation and
Quality assurance in systems development (5.2 - 5.3)
Summarize the different characteristics of quality
assurance (Level 1).
Nine characteristics of quality assurance
1.
Completeness - the system meets all the
performance specifications and provides all the
functions specified
2.
Correctness - the system performs the required
functions accurately
27
9
Part 2 - Testing in systems implementation and
Quality assurance in systems development (5.2 - 5.3)
3.
Reliability - the system can handle normal and
peak loads
4.
Consistency - operations are carried out in the
same manner each time they are requested
5.
Efficiency - the amount of computer resources
required by the system is reasonable
6.
Integrity - access to software or data by
unauthorized persons can be controlled
28
Part 2 - Testing in systems implementation and
Quality assurance in systems development (5.2 - 5.3)
7.
Testability - the system is designed so that it can
be tested to ensure it performs the intended
functions
8.
User-friendliness - the system is easy to use, and
users can understand interactive dialogue
9.
Maintainability - programming is structured and well
documented, changes can be made easily, and
errors can be corrected with relative ease
29
Part 2 - Testing in systems implementation and
Quality assurance in systems development (5.2 - 5.3)
Ensuring quality
•
Involve the right people in the project
and in the testing
•
Consider using an independent
testing team
•
Don’t cut corners on testing!
30
10
Part 3
Systems maintenance,
enhancement, and
reengineering
Topics 5.4 - 5.5
31
Part 3 - Systems maintenance, enhancement,
and reengineering (5.4 - 5.5)
Six activities of systems development
32
Part 3 - Systems maintenance, enhancement,
and reengineering (5.4 - 5.5)
Explain the basic tasks of systems maintenance
(Level 2).
Systems maintenance includes corrections to:
•
program bugs
•
design bugs
•
documentation errors
•
operating procedure errors
•
test data errors
33
11
Part 3 - Systems maintenance, enhancement,
and reengineering (5.4 - 5.5)
Systems maintenance consists of five activities:
1. Define and validate the problems. The exact
nature of problems must be identified.
2. Benchmark the programs and applications. The
system should be tested to establish a
benchmark.
3. Understand the application and its programs.
You must study the programs to understand how
they interact.
34
Part 3 - Systems maintenance, enhancement,
and reengineering (5.4 - 5.5)
4. Edit and test the programs. Once you fully
understand the corrective actions required,
changes are made to the appropriate programs.
5. Update documentation. It is important to
document your changes so that someone else
can maintain the system in the future.
Documentation provides a record of the issues
raised and what changes were made to the
system.
35
Part 3 - Systems maintenance, enhancement,
and reengineering (5.4 - 5.5)
Defend the need for sufficient systems maintenance
(Level 2).
•
Systems maintenance can consume up to 80% of
an IS budget.
•
Systems support tends to be given higher priority
than developing new systems.
•
It is recommended to have separate support and
development budgets.
36
12
Part 3 - Systems maintenance, enhancement,
and reengineering (5.4 - 5.5)
Assess a non-IT manager’s role in evaluating systems
enhancements (Level 2).
•
•
Three types of systems enhancements: mandatory,
strategic, and “nice-to-haves”
Your role in systems enhancements and
reengineering:
– assess the implications especially around
business rules
– anticipate changes
– make cost-benefit assessments
37
Part 3 - Systems maintenance, enhancement,
and reengineering (5.4 - 5.5)
5 steps for implementing systems enhancements:
1. Analyze the enhancement request
2. Write simple, new programs
3. Restructure files or databases
4. Analyze program libraries and maintenance
costs
5. Reengineer and test programs
38
Part 4
Legacy systems issues
and
Measuring system benefits
Topic 5.6
39
13
Part 4 - Legacy systems issues and Measuring
system benefits (5.6 - 5.7)
Relate the issues that surround legacy systems to the
challenges of replacing them (Level 1).
Problems with legacy systems
•
Obsolete programming languages
•
Poor system documentation
•
Lost program documentation
40
Part 4 - Legacy systems issues and Measuring
system benefits (5.6 - 5.7)
•
Risk of replacing a working system with an
unproven, new system
•
Interface issues between new systems and
legacy systems
Management implications
• Determine the appropriate level of “current” and
build this into IS plan
• Have separate development and maintenance
budgets
41
Part 4 - Legacy systems issues and Measuring
system benefits (5.6 - 5.7)
Assess the possible benefits of a new system and
evaluate some strategies for measuring those
benefits (Level 1).
Benefits of new systems
•
Help create or sustain competitive advantage
(reduce costs, create alliances, differentiate
products and services, etc.)
•
Achieve business transformation
•
Support strategic planning and globalization, etc.
42
14
Part 4 - Legacy systems issues and Measuring
system benefits (5.6 - 5.7)
• Inventory and personnel
reduction
• Productivity improvement
• Order mgmt improvement
• Financial close cycle
reduction
• Cost reductions
(procurement, T/LOG etc.)
• Cash mgmt improvements
• Revenue increases
• Maintenance reduction
• On-time delivery
improvements
• Information visibility
• Improved processes
• Customer responsiveness
• Increased integration,
standardization, and
flexibility
• Globalization
• Improved performance
• Supply chain management
Source: Mullin, Rick. ERP Users Say Payback is Passé,
Chemical Week (Feb 24, 1999)
43
Part 4 - Legacy systems issues and Measuring
system benefits (5.6 - 5.7)
Strategies for identifying and measuring benefits
•
Proxies for intangible benefits
•
Parallel implementation
•
Obtain information from managers or users
•
Obtain customer or supplier feedback
44
Part 5
Assignment tips
45
15
Part 5 - Assignment tips
Assignment 2 tips
Q1 MCQs - come from a variety of topics;
use your textbook and Module Notes
Q2 Presentation - see Online Lecture for Module 3,
Part 5
• Presentation is to a new subsidiary’s IT
department.
• Topic is the major activities in IT acquisition,
including the RFP/RFQ process, and the
benefits of such a process.
46
Part 5 - Assignment tips
Q2 continued: Possible slide plan:
•
Title slide (slide 1)
•
Introduction - outline/highlight the activities for
selecting and acquiring IT (slide 2).
•
One slide each to discuss the six activities
(slides 3-8)
•
A conclusion - why follow these activities (slide 9)
•
Close by listing some relevant websites (slide 10)
Speaker’s notes for each slide should give enough
detail to use if you were giving the presentation
(remember to include introductory and closing
comments).
47
Part 5 - Assignment tips
Assignment 2 tips
Q3 Memo - see Online Lecture for Module 2, Part 6
• Benefits and challenges of a small company
following the larger parent-company’s analysis
and design standards and procedures
• Balance your answer and address both sides
• Remember proper format, proper opening and
closing comments
48
16
Part 5 - Assignment tips
Assignment 2 tips
Q4 Case study - Cisco Systems: Implementing ERP
• General report tips - see Online Lecture for
Module 1, Part 6
• Use the last paragraph in the case for
guidance
• Discuss why the ERP implementation
succeeded, and whether this success could
be repeated (i.e., where were they smart and
where were they lucky?)
49
Part 5 - Assignment tips
Assignment 2 tips
Q4 Case study - Cisco Systems continued
• Follow the format given (Executive summary,
Introduction…)
• Issue identification
– Key issues or decisions that led to the
success of the implementation
– Key things that could have been done better
– Review Topic 3.1 - common reasons why
projects succeed or fail
50
Part 5 - Assignment tips
Assignment 2 tips
Q4 Case study - Cisco Systems continued
• Analysis - consider positive and negative
aspects of issue identified (good and bad points
of decisions made)
• Recommendation - summarize keys to success
and recommend changes for next time to make
sure success could be repeated
• Conclusion - limitations and/or future
considerations
51
17