System Implementation
1
Introduction
Systems development life cycle with the
implementation phase highlighted
2
System Implementation
Six major activities:
Coding
Testing
Installation
Documentation
Training
Support
3
System Implementation (Cont.)
Purpose:
To convert final physical system specifications
into working and reliable software
To document work that has been done
To provide help for current and future users
4
The Process of Coding, Testing,
and Installation
Coding
Physical design specifications are turned into working computer code.
Testing
Tests are performed using various strategies.
Testing is performed in parallel with coding.
Installation
The current system is replaced by a new system.
5
The Process of Coding, Testing, and
Installation
6
Types of Tests
Static or dynamic techniques
Static testing means that the code being tested is not executed.
Dynamic testing involves execution of the code.
Test is automated or manual
Automated means computer conducts the test.
Manual means that people complete the test.
Inspection a testing technique in which participants examine program
code for predictable language-specific errors
7
Types of Tests (Cont.)
Desk checking: a testing technique in which the program code is sequentially
executed manually by the reviewer
Unit testing: each module is tested alone in an attempt to discover any errors in its
code
Integration testing: the process of bringing together all of the modules that a program
comprises for testing purposes
Modules are typically integrated in a top-down incremental fashion.
8
Types of Tests (Cont.)
System testing: the bringing together of all of the programs that a system comprises
for testing purposes
Programs are typically integrated in a top-down, incremental fashion.
9
Acceptance Testing by Users
Acceptance testing: the process whereby actual users test a completed information
system, the end result of which is the users’ acceptance of it
Alpha testing: user testing of a completed information system using simulated data
Beta testing: user testing of a completed information system using real data in the
real user environment
10
Installation
Installation: the organizational process of changing over
from the current information system to a new one
Four installation strategies:
Direct Installation
Parallel Installation
Single-location installation
Phased Installation
11
Direct Installation
Direct installation: changing over from the old system to
a new one by turning off the old system when the new
system is turned on
.
12
Parallel Installation
Parallel installation: running the old information system and
the new one at the same time until management decides the old
system can be turned off
13
Phased Installation
Phased Installation: changing from the old information system to the new one
incrementally, starting with one or a few functional components and then gradually
extending the installation to cover the whole new system
14
Documenting the System
System documentation: detailed information about a system’s design
specifications, its internal workings, and its functionality
User documentation: written or other visual information about an application
system, how it works, and how to use it
Internal documentation: system documentation that is part of the program
source code or is generated at compile time
External documentation: system documentation that includes the outcome of
structured diagramming techniques such as data flow and E-R diagrams
15
Summary
In this chapter you learned how to:
Describe the process of coding, testing, and converting an
organizational information system and outline the deliverables and
outcomes of the process.
Apply four installation strategies: direct, parallel, single-location, and
phased installation.
16
