Information Systems: Implementing and
Outsourcing Enterprise & Project Management
0
Please note that these slides are not intended as a substitute
to reading the recommended text for this course.
Outline the elements of a testing strategy and the stages of testing
Describe the limitations of testing
Examine the different training options for a new system
Describe the changeover options from an old system to a new
Discuss the option of outsourcing
Objectives
1
Implementation activities are needed to transform a newly developed information system into a operational system for end users.
– Acquisition / installation – acquire/install necessary hardware (physical structure) and
software (apps) resources
• Documentation 1 - record detailed system specifications/requirements
• Software Development - develop necessary computer programs and make necessary
modifications to software packages – ‘off-the-shelf’ / bespoke
– Testing - test and make necessary corrections to programs, procedures, and hardware
• Documentation 2 – test results / changes / errors
– Training - educate and train management, end users, etc.
– Conversion - convert present system to new and/or improved system
– Changeover / Maintenance - keep up-to-date
Implementing IS
2
Acquisition – Evaluate and acquire
necessary hardware and software resources and information systems services.
Screen vendor proposals. – The firm can evaluate a
companies product or service by submitting a RFP (request for proposal)
Evaluation Factors – Some hardware factors:
performance, cost compatibility, connectivity, vendor support.
– Some software factors:
features/functions, language, integration compatibility, cost, documentation, other company successful use.
– Some service factors:
systems development, conversion, training, backup, accessibility.
Acquisition / Evaluation
3
Development
– Internal development of application software (competencies / capabilities / time criticality)
– or the acquisition of this software from vendors.
Documentation – User guides
– Business procedures
– Input forms, filled in for sample cases
– Sample output reports
– Frequently-asked questions
Development / Documentation
4
IS personal must be certain that end users are trained to operate the new system or the implementation process will fail.
– Can take several weeks to train all new users
• Individual tuition
• Classroom course
• Computer-based Training (CBT)
Training
5
Individual tuition
Classroom course
Computer-based Training (CBT)
Case Studies & Exercises
Software reference material
Training
6
Paper Files Existing
Computer Files
Manual & Computer
Data incomplete
File Conversion scenarios
7
Parallel: both old and new systems are operated until IS team and management agrees to convert
Pilot: one department or work site serves as a tester.
Phased: only parts of the new system or only a few departments, offices, or plant locations at a time are converted
Plunge/Direct: direct abandonment of old system and conversion to new system.
Major Forms of Conversion
8
When to use
– Customer communication must not be wrong
– New system is direct replacement of old system
– Fail-safe option is needed
– To check end-of-period processing e.g. month end
• Month-end processing on old system
• Month-end processing on new system
• Results compared to ensure exactly the same
Parallel running - when to use
9
Advantages: Errors can be found in
new system before changeover without risking the end product / result.
Old system is immediately available if the new system fails.
Staff have time to get used to and become fully trained in the new system before changeover.
Disadvantages:
Everything needs to be done twice.
High cost in terms of resources and staff training.
Parallel Running – Advantages & Disadvantages
10
When to use
– Many similar areas to implement, geographically spread
– System is entirely new and not replacing existing system
– New hardware or network configuration needs to be proven
– There is a business imperative to implement one part of the system while other departments prepare
• For example launching a new product
Pilot followed by roll-out - when to use
11
Advantages
Allows a small scale complete system to be tested while only risking a limited volume of data or some end products.
The other systems or parts remain unaffected if new system fails.
Disadvantages
Slow implementation and the old system for this system or part is not immediately available.
Is not using full data.
Pilot running
12
Advantages: Allows staff to get used
to one part before trying the next.
Allows tight monitoring of a new system with low costs in terms of resources and staff training (as compared with parallel running).
Allows the bugs in the new system to be ironed out without them causing any serious problems.
Disadvantages:
Slow implementation.
The two systems may not compatible.
Phasing
13
When to use
– No existing system to replace
– All users have been trained and ready
– System has been completely tested and found acceptable
– All system functionality needed at same time
• Phased implementation not a viable business option
Direct changeover - when to use
14
Advantage:
Fast implementation.
Disadvantage:
Staff have no time to get used to the new system.
Extremely difficult to revert back to the old system if the new system fails.
Any new data files have to be operational before the changeover is made.
Big Bang / Plunge / Direct Changeover
15
Post-implementation review is a part of IS maintenance where the new system is evaluated to be certain that the newly implemented system meets the system objectives established for them.
IS Review and Maintenance
16
Maintain Convert Train
Document
TEST
Develop Acquire
Testing In Detail
17
“Testing is the process of establishing confidence that a program or system does what it is supposed to.” Hetzel 1973
“Testing is the process of executing a program or system with the intent of finding errors.” Myers 1979
What is Testing?
18
Test Plan
Test Design
Perform Tests
Document
Re-Test
Test Strategy
19
Overarching Strategic Approach
System Logic
– Logic behind and flow of the program
Program Testing
– Process the data through the program
– Unit (one) testing / unit integration (multiple) testing
System Testing
– Complete system test before and after implementation
User Acceptance Testing (UAT)
Stages of Testing
20
Acceptance testing is a formal testing conducted to determine whether a system satisfies its acceptance criteria
– User Acceptance Testing (UAT)
• It is conducted by the customer to ensure that system satisfies the contractual acceptance criteria before being signed-off as meeting user needs.
User Acceptance Testing (UAT)
21
Realistic
– Actual users and data transactions
Contrived
– Purposefully inputting incorrect data
Volume
– Large number of transactions
UAT
22
There is no definitive answer to this question
– Every time a user executes the software, the program is being tested
– Testing usually stops when a project is running out of time, money, or both
– One approach is to divide the test results into various severity levels or ranked according to defects (H/M/L)
When is Testing Complete?
23
Limitations of Testing
24
Several activities to implement system
– Install system as appropriate
– Populate relevant databases - migrate or input
– User guide and other documentation
– User training
– Include new system functions in business procedures
Deliverable: working system now operational
Milestones: system development completed
– System up and running
– Users trained
– System functions integrated into business processes
In Summary: Traditional life cycle - Implementation
25
Test strategy designed at end of requirements stage
– System testing ensures that components link together
– End-to-end testing ensures that input is correctly transformed into outputs and is delivered to right places
– User acceptance testing ensures that realistic test cases are correctly processed and give required results
– Tests processes, interface, reports, configuration
Deliverable: test logs at relevant levels
Milestone: testing sign-off
– System performs as expected and required
– Users accept developed system
In Summary: Traditional life cycle - Test stage
26
Outsourcing -
– the strategic use of outside resources to perform activities traditionally handled by internal staff and resources
Why Outsource?
– Provide services that are scalable, secure, and efficient, while improving overall service and reducing costs
What is Outsourcing?
27
Traditional role - reaction to problem
– Reduction and control of costs
– Avoid large capital investment costs
– Insufficient resources available
Modern role – business strategy
– Allows company to focus on their core competencies
– Keeping up with cutting-edge technology
– Creating value for the organization and its customers
– Building partnerships
Reasons for Outsourcing
28
system integration
data network
mainframe data center
voice network, internet/intranet
maintenance/repair
applications development
e-commerce
end-user support system
What Can be Outsourced?
29
