CHAPTER - 3
Systems
Implementation
and Maintenance
3.1 Systems Implementation
3.2 Maintaining Information Systems
1
3.1 System Implementation
2
Introduction
The implementation phase of the SDLC is the
most expensive and time-consuming phase of
the entire life cycle.
During implementation, physical design
specifications must be turned into working
computer code.
Then the code is tested until most of the errors
have been detected and corrected, the system
is installed, user sites are prepared for the new
system, and users must come to rely on the
new system rather than the existing one to get
3
their work done.
System Implementation
• Six major activities:
– Coding
– Testing
– Installation
– Documentation
– Training
– Support
4
4
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.
5
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 performed in parallel with coding.
Installation
The current system is replaced by new system.
6
The Process of Documenting the System,
Training Users, and Supporting Users
Two audiences for final documentation
Information systems personnel who will
maintain the system throughout its
productive life.
People who will use the system as part of
their daily lives.
User Training
Application-specific.
7
Different 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.
11
Different Types of Tests (manual)
Inspection: a testing technique in which
participants examine program code for
predictable language-specific errors.
Desk checking: a testing technique in
which the program code is sequentially
executed manually by the reviewer.
12
Different Types of Tests (Cont.)
(Automated)
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.
Modulesare typically integrated in a top-down
incremental fashion.
13
Different 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.
14
Different Types of Tests (Cont.)
Stub testing: a technique used in testing
modules, especially where modules are
written and tested in a top-down fashion,
where a few lines of code are used to
substitute for subordinate modules.
15
The Testing Process
The purpose of testing is to confirm that
the system satisfies the requirements,
Testing must be planned.
Test case is a specific scenario of
transactions, queries or navigation paths.
16
Installation
Installation: the organizational process of
changing over from the current
information system to a new one.
Four installation strategies:
Direct Installation (direct cut over).
Parallel Installation.
Single-location installation (pilot).
Phased Installation.
17
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 a system
application, how it works, and how to use
it.
18
Documenting the System (Cont.)
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.
19
Types of training methods
Resident expert
Traditional instructor led classroom
training
E-learning – distance learning
Combination of the above (blended/hybrid)
Software help components
External sources, such as vendors
20
Supporting Information Systems
Users
Support is extremely important to users.
Providing support can be expensive and
time-consuming.
21
Support Issues for the Analyst
to Consider
User questions and problems.
Recovery and backup.
Disaster recovery.
PC maintenance.
Setting up user groups.
22
Organizational Issues in Systems
Implementation
Biggest measure of success: Will it be
used?
Major factors influencing likelihood of use:
Personal stake of users
System characteristics
User demographics
Organizational support
Performance
Satisfaction
23
Security Issues
Increasing important issue for
organizations and their management.
Malicious software (malware): includes
Trojan horses, worms, viruses, and other
kinds.
External sources of threats
24
3.2 Maintaining
Information Systems
25
The Process of Maintaining Information
Systems
• The process of maintaining an information system is the
process of returning to the beginning of the SDLC and
repeating development steps, focusing on the needs for
system change, until the change is implemented.
• Four major activities occur within maintenance:
1. Obtaining maintenance requests
2. Transforming requests into changes
3. Designing changes
4. Implementing changes
26
Cont…
Obtaining maintenance requests requires
that a formal process be established
whereby users can submit system change
requests.
When developing the procedures for
obtaining maintenance requests,
organizations must also specify an individual
within the organization to collect these
requests and manage their dispersal to
maintenance personnel.
27
Cont…
Once a request is received, analysis must
be conducted to gain an understanding of
the scope of the request.
It must be determined how the request will
affect the current system and the duration
of such a project.
28
Deliverables and Outcomes from
Maintaining Information Systems
• The deliverables and outcomes from the
process are the development of a new version
of the software and new versions of all design
documents and training materials developed
or modified during the maintenance process.
29
Types of Maintenance
30
Types of Maintenance
Corrective maintenance refers to changes
made to repair defects in the design, coding,
or implementation of the system.
Adaptive maintenance involves making
changes to an information system to evolve
its functionality to changing business needs
or to migrate it to a different operating
environment.
31
Types of Maintenance (cont…)
Perfective maintenance involves making
enhancements to improve processing
performance, interface usability, or to add
desired, but not necessarily required,
system features.
Preventive maintenance involves
changes made to a system to reduce the
chance of future system failure.
32
The Cost of Maintenance
Information systems maintenance costs
are a significant expenditure. For some
organizations, as much 60–80 percent of
their information systems budget is
allocated to maintenance activities.
33
-3
Ch
o f
n d
• E
34