for the Small Enterprise
Systems Analysis and Design
chapter15
section V
Implementation
system conversion
project review
project deliverable: the final report
programmed reviews
types of system maintenance
information system obsolescence
maintenance contacting
the cornucopia case
portfolio project
System Conversion
System conversion involves all six components of
an information system.
The data component presents special problems:
Although the analyst might find some of the
new system files already exist in machinereadable format, but they require modification
to add or delete fields or to change the file
organization or medium.
In addition, some new system files may not
exist at all or exist only within a manual
record-keeping system.
Chapter 15
Systems Analysis and Design
for the Small Enterprise
2
Conversion Options
There are several ways in which to convert
from the existing system to the new
system, each with different costs and
risks.
Chapter 15
Systems Analysis and Design
for the Small Enterprise
3
Figure 15-2: Conversion Options
Direct
Conversion
Phased
Conversion
Parallel
Conversion
Chapter 15
Systems Analysis and Design
for the Small Enterprise
4
Figure 15-3: Conversion Cost and Risk
Direct
Conversion
Chapter 15
Phased
Conversion
Systems Analysis and Design
for the Small Enterprise
Parallel
Conversion
5
Figure 15-4: Conversion Plan Outline
Chapter 15
Systems Analysis and Design
for the Small Enterprise
6
Project Review
The project review provides an opportunity for
the analyst and the user to evaluate the project
in terms of its success or failure to meet the
project specifications.
The summarized results of the project review
should be recorded and annotated with any
information that will help the analyst and the
user with future projects.
Chapter 15
Systems Analysis and Design
for the Small Enterprise
7
Project Deliverable: The Final Report
While there is no standard format for the final
report, it should contain several elements:
1. A cover page transmitting the
working product to the user
2. Brief summary of the overall effort
3. Suggested future enhancements
4. Description of the need for ongoing
system maintenance
Note: The final report is distinct from the product documentation manuals.
Chapter 15
Systems Analysis and Design
for the Small Enterprise
8
Figure 15-7: Contents of Final Report
Chapter 15
Systems Analysis and Design
for the Small Enterprise
9
Programmed Review
A programmed review is a systematic evaluation
of all facets of an operational information
system.
Its purpose is to determine how well the system
functions when compared to its own, or to
industry-established performance norms.
Programmed reviews should occur regularly
throughout the maintenance and review phase
of the SDLC.
Chapter 15
Systems Analysis and Design
for the Small Enterprise
10
Information System Programmed Review
Periodic programmed
reviews occur during the
maintenance and review
phase of the life cycle
Chapter 15
Systems Analysis and Design
for the Small Enterprise
11
Types of System Maintenance
There are several types of system
maintenance, each differing in terms of:
1. Positioning within the SDLC model
2. Associated complexity and cost
3. Impact on the information system
Chapter 15
Systems Analysis and Design
for the Small Enterprise
12
Types of Information System Maintenance
Chapter 15
Systems Analysis and Design
for the Small Enterprise
13
Preventive Maintenance Tasks
Chapter 15
Systems Analysis and Design
for the Small Enterprise
14
Information System Obsolescence
Eventually, every information system must be
replaced. Functional obsolescence describes a
system that can no longer satisfy the information
needs of the user.
As an information system approaches functional
obsolescence, maintenance costs begin to rise
steadily. These costs may continue to rise as analysts
try to keep the system operational or they may
actually level off, indicating a reluctance to devote
more resource to alter a product at the end of its
useful life.
Chapter 15
Systems Analysis and Design
for the Small Enterprise
15
Chapter Summary
• Many cutover phase activities begin well before
the system becomes operational
• The project should be evaluated and brought to
a definitive close by signing a user acceptance
form
• System maintenance is by far the longest period
of the SDLC and often has a tremendous
influence on the overall success of a product
• Obsolescence is a natural part of the SDLC
Chapter 15
Systems Analysis and Design
for the Small Enterprise
16