Introduction to Business Systems Analysis
Student Study Guide
Section Four Implementation
Section Overview
1. List of Objectives

System Implementation
This is the stage when things are done rather than analyzed or designed. There are
various separate but related tasks to be accomplished. Programs are written and
tested, hardware is acquired and installed, staff are trained, the system is tested, and
historic data from the old manual system or computer system is loaded into the files
or database. Many of these tasks are carried out simultaneously. It is important that
they are all completed before completing changeover to the new system.

Software Application Testing
As mentioned previously, systems analysts prepare system specifications that are
passed on to programmers for coding. However, as software application testing is an
activity analysts plan (beginning in the analysis phase) and sometimes supervise, it is
a good idea for you to understand the essentials of the software application testing
process. In addition, analysts are responsible for communicating the status of the
testing process to project stakeholders.

Installation
Installation is the stage at which the new computer system will be brought into
operation. How and when this is done will depend on management confidence in the
project plan. Essentially, all employees who use the system must give up their
reliance on the current system and begin to rely on the new system. Four approaches
to installation have emerged over the years and are considered here (see Figure 4-6).
They are not mutually exclusive. Each has its benefits and limitations. They have
varying degrees of safeguards against the effects of system malfunctions on the
organization.

Documenting the System
Historically, preparing documentation has not rated near the top of favorite tasks.
Many analysts come from programming background, where they develop a distinct
preference for the programming process itself rather than for the accompanying
paperwork. However, as the computing industry grows more sophisticated, it
becomes increasingly clear to management that documentation is a critical element in
the development of a systems project. The reasons are many. As a student of business
systems analysis you should understand the importance of developing the
documentation elements early, as the information needed is captured. People can find
many ways to rationalize not documenting. But those who fail to document systems
do so at their peril. There are numerous irrefutable arguments in favor of
documentation.

Organizational Issues in Systems Implementation
In earlier material you studied organizational feasibility issues in systems
implementation, including scenarios involving significant risk. All sorts of problems
develop during the implementation phase. Sometimes old psychological problems
resurface, as novice users worry about actually coming to grips with a new computer
system. The fears can be manifested in the form of avoidance or even sabotage.
Analysts have problems, too. The implementation can be very intense so it is good for
you to be informed about the reasons why systems implementation efforts fail.
2. Chapter Summary
This chapter introduces you to many of the activities carried out during implementation,
including coding, testing, installation, documentation, user training, and support for a
system after it is installed. While most systems development texts do not include much
material on implementation, we have tried to remedy this situation by providing material
on relevant management issues, including change management, organizational politics,
and implementation success. We also include a discussion of implementation failure,
something few systems development texts discuss, despite the high rate of information
systems failure. The discussion of failure is presented in the context of factors the analyst
(and project manager) can control in an attempt to ensure success.
One of our goals in Section 4 is to show you that implementation is neither simple nor
mechanical. We have tried to emphasize all along that systems development is a change
process. For many users, the most obvious evidence of change comes during
implementation. Once a new system has been coded, tested, and installed, the systems
development team does not simply walk away. The organization members left with the
new system, the users, will need a solid understanding of how the new system fits into
their work lives and how the system can support them in their day–to–day work
activities. User documentation, training, and continuing support are all parts of providing
this solid understanding to users. In some organizations, other specialists in the IS
department, such as technical communicators, trainers, local experts, and help desk
employees, will be available to help the analyst complete this part of the implementation
process. In other organizations, the analyst may have to do most of this work alone. In the
latter case, the importance of user documentation, training, and support should not be
overlooked. The success of a system implementation effort depends on what the users
think of the system and their inclination to use it well. The training and support effort will
have a definite effect on user attitudes and inclinations.
3. Short Essay Questions
1.1 Discuss each system installation strategy--direct, parallel, single location, or phased.
Answer: Refer to textbook pages 119-121.
1.2 Use Tables 4.5 and 4.6 and Figure 4.8 to demonstrate the differences between system
and user documentation. Think about being a user, not a developer or IS specialist, in
whom one’s focus is on doing the job, not using the software. You might refer to a
“user’s manual” for a common product (e.g., a TV, VCR, microwave oven) and
analyze the features of this manual that make it a good or bad manual.
1.3 Explain the testing process for code.
Answer: The testing process involves testing code for errors and functionality. The
testing process, guided by a detailed testing plan, can begin as soon as modules are
coded and proceed in parallel with the rest of the coding process. Modules are tested
individually and then as parts of larger programs and parts of larger systems.
1.4 What are the four approaches to installation? Which is the most expensive? Which is
the most risky? How does an organization decide which approach to use?
Answer: The four approaches to installation are direct, parallel, single location, and
phased. With the direct approach, the old system is turned off, and the new one is
turned on. In the parallel approach, both systems are run until management decides
the old system can be turned off. In single location, the system is tried out in a pilot
project at one location and then implemented elsewhere if the pilot is successful.
With the phased approach, the new system is brought on–line gradually, usually
function by function.
1.5 Explain Lucas’s model of implementation success.
Answer: Lucas identified two methods for determining if an implementation has
been successful: the user’s satisfaction with the system and the extent to which the
system is used. Lucas further identified six factors that influence the extent to which
a system is used; these are user’s personal stake, system characteristics, user
demographics, organization support, performance, and satisfaction. Figure 4-9
illustrates the relationships these factors have to each other. An analyst will have
more control over certain factors (system characteristics and level of support);
however, the analyst will not have direct control over the demographics of the user,
personal stake in the system, management support, or problem urgency. This model
points out that the analyst should balance the factors that he/she cannot change with
those factors that he/she can change.
4. End of Chapter Questions
1.1 Define the term walkthrough.
Answer: A walkthrough is a peer group review of any product created during the systems
development process.
1.2 Define the term stub testing.
Answer: Stub testing is a technique used in testing modules, especially modules written
and tested in top-down fashion, where a few lines of code or stubs are used to substitute
for subordinate modules.
1.3 What is the difference between system documentation and user documentation?
Answer: System documentation is the detailed information about a system’s design
specifications, its internal workings, and its functionality, whereas user documentation
consists of written or other visual information about an application system, how it works,
and how to use it.
1.4 What is the conventional wisdom about implementation success?
Answer: The conventional wisdom that has emerged over the years is that there are at
least two conditions necessary for a successful implementation effort: management
support of the system under development and the involvement of users in the
development process.
Multiple Choice Questions
1.5 After maintenance, which of the following is the most expensive and most timeconsuming phase of the entire system development life cycle?
a. implementation
b. physical design
c. logical design
d. analysis
1.6 Which of the following affect the implementation process?
a. the work habits of an organization’s members
b. the personal goals of an organization’s members
c. the beliefs of an organization’s members
d. all of the above
1.7 The purpose of coding, testing, and installation is to:
a. transform the logical specifications of the system into technology specific details
from which all programming and system construction can be done
b. convert the final physical system specifications into working and reliable
software and hardware
c. systematically repair and improve the information system
d. study and propose alternative replacement systems
1.8 Who is responsible for ensuring that coding, testing, and installation are properly
planned and executed?
a. programmers
b. management
c. systems analysts
d. end-users
1.9 The process whereby the physical design specifications created by the analysis team
is turned into working computer code is referred to as:
a. coding
b. testing
c. implementation
d. code conversion
1.10
Which of the following statements is true regarding testing?
a. The coding process should be completed, and then the testing process can begin.
b. Once coding has begun, the testing process can begin and proceed in parallel.
c. The testing process is performed first, then the coding process begins.
d. none of the above
1.11 The process in which the current system is replaced by the new system best
describes:
a. the systems development life cycle
b. installation
c. physical design
d. set-up
1.12
A master test plan is developed during:
a. implementation
b. analysis
c. logical design
d. physical design
1.13
The type of testing that does not execute the code is called:
a. static testing
b. dynamic testing
c. referential testing
d. manual testing
1.14
The results of running the code are not an issue for this particular type of test:
a. static testing
b. dynamic testing
c. referential testing
d. none of the above
1.15
The type of testing that involves the execution of code is called:
a. code testing
b. static testing
c. dynamic testing
d. execution
1.16 A testing technique in which participants examine program code for predictable
language-specific errors defines:
a. walkthrough
b. inspections
c. desk checking
d. syntax checking
1.17
The type of testing responsible for determining what the code does is:
a. walkthrough
b. inspection
c. system testing
d. syntax checking
1.18 A testing technique in which the program code is sequentially executed mentally
by the reviewer is referred to as:
a. inspection
b. system testing
c. desk checking
d. syntax checking
1.19 Testing each module alone in an attempt to discover any errors that may exist in
the module’s code is referred to as:
a. unit testing
b. system testing
c. stub testing
d. singular testing
1.20 The process of bringing together all of the modules that compose a program for
testing purposes is referred to as:
a. unity testing
b. integration testing
c. system testing
d. implementation
1.21 The bringing together of all the programs that compose a system for testing
describes:
a. unity testing
b. integration testing
c. system testing
d. implementation
1.22
The purpose of acceptance testing is:
a. to determine if new requirements must be added to the newly completed system
b. to determine if the system meets user requirements
c. to determine if the system meets its objectives
d. none of the above
1.23
The most complete acceptance testing will include:
a. alpha testing
b. beta testing
c. a system audit
d. all of the above
1.24 The process whereby actual users test a completed information system, the end
result of which is the users’ acceptance of it, this description defines:
a. acceptance testing
b. alpha testing
c. beta testing
d. system testing
1.25
Users testing of a completed information system using simulated data refers to:
a. acceptance testing
b. alpha testing
c. beta testing
d. system testing
1.26 Users testing of a completed information system using real data in the real user
environment refers to:
a. acceptance testing
b. alpha testing
c. beta testing
d. system testing
1.27 Tests performed during alpha testing that are designed to try to break the system
are:
a. stress testing
b. performance testing
c. recovery testing
d. security testing
1.28 Changing over from the old information system to a new one by turning off the
old system as the new one is turned on best describes:
a. phased installation
b. single location installation
c. parallel installation
d. direct installation
1.29
Which of the following is a basic type of documentation?
a. design documentation
b. system documentation
c. user documentation
d. both b and c
1.30
Which of the following is not a type of system documentation?
a. internal documentation
b. external documentation
c. user documentation
d. none of the above (all are types of system documentation)
1.31
All of the following are types of user documentation except:
a. release description
b. reference guide
c. acceptance sign-off
d. management plan
1.32
System documentation is intended primarily for:
a. maintenance programmers
b. end users
c. systems analysts
d. system operators
1.33 Written or other visual information about an application system, how it works,
and how to use it best defines:
a. system documentation
b. user documentation
c. internal documentation
d. external documentation
1.34 Which of the following consists of an exhaustive list of the system’s functions
and commands, usually in alphabetic order?
a. reference guide
b. user’s guide
c. release description
d. system administrator’s guide
1.35 Most user documentation is now delivered:
a. online, in hypertext format
b. through paper manuals
c. by calling technical support numbers
d. through help desks