IE 302 SYSTEMS ANALYSIS AND DESIGN

LECTURE 9_CHAPTER 10
SYSTEMS IMPLEMENTATION AND OPERATION

DR. HUSAM KAID

Copyright © 2015 Pearson Education, Inc. Publishing as Prentice Hall
1
Lesson Overview
▪ Systems implementation and operation is the
last phase of the systems development life
cycle.
▪ As Figure 10–1 shows, this phase consists of
coding, testing, installation, documentation,
training, support, and maintenance.
▪ Specifically, this lecture identifies where
coding and testing fits in the overall scheme
of implementation, stresses the view of
implementation as an organizational change
process, discusses the importance and types
of documentation and training, overviews the
types of testing, and introduces four types of
installation. 2
Systems Implementation and Operation
▪ Seven major activities
✓Coding
✓Testing
✓Installation
✓Documentation
✓Training
✓Support
✓Maintenance
▪ 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
The Processes of Coding, Testing and Installation

▪ Coding
✓Physical design specifications are
turned into working computer code

▪ Testing
✓Tests are performed using various
strategies
✓Testing can be performed in parallel
with coding

▪ Installation
✓Process during which the current
system is replaced by the new system
Copyright © GiHup, Dzone, and Wide Eye Digital Signage
The Processes of Coding, Testing, and Installation: Deliverables
The Processes of Documenting the System, Training
Users, and Supporting Users

▪ Two audiences for documentation

✓ The information systems personnel

who will maintain the system
throughout its productive life

✓ The people who will use the system as

part of their daily lives

▪ Deliverables are shown in Table 10-2

The Process of Maintaining Information Systems
▪ Process of returning to the beginning of the SDLC and
repeating development steps focusing on system change
until the change is implemented

▪ Four major activities:

1.Obtaining maintenance requests
2.Transforming requests into changes
3.Designing changes
4. Implementing changes

▪ Deliverables and Outcomes

✓Development of a new version of the software,
✓ New versions of all design documents
✓tTraining materials created or modified during the Copyright © Bubble

maintenance effort
The Process of Maintaining Information Systems

▪ Figure 10–2 shows the

maintenance activities

in relation to the SDLC

phases.
Software Application Testing

▪ A test plan is developed during the analysis phase

▪ During the design phase, a unit test plan and a system test
plan are developed

▪ The actual testing is done during implementation

▪ Test plans provide improved communication among all

parties involved in testing
› Serve as checklists
Software Application Testing

▪ Types of Testing

1) Inspection
› A testing technique in which participants examine program code for predictable language-
specific errors
2) Walkthrough
› A peer group review of any product created during the systems development process; also
called a structured walkthrough
3) Desk Checking
› A testing technique in which the program code is sequentially executed manually by the
reviewer
4) Unit Testing
› Each module is tested alone in an attempt to discover any errors in its code, also called
module testing
Software Application Testing (continued)

▪ Types of Testing (continued)

5) 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

6) System Testing
› The bringing together of all the programs that a system comprises for testing purposes;
programs are typically integrated in a top-down, incremental fashion

7) Stub Testing
› A technique used in testing, 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
Software Application Testing: The Testing Process
▪ The purpose of the testing is to confirm
that the system satisfies requirements
▪ Testing must be planned
▪ Test Case
› A specific scenario of
transactions, queries, or
navigation paths that represent a
typical, critical, or abnormal use
of the system
› Test cases and results should be
thoroughly documented so they
can be repeated for each revision
of an application
Software Application Testing: The Testing Process
▪ The process whereby actual users test a completed information system, the end result of which is the users’
acceptance of it
▪ Acceptance testing includes both alpha testing and beta testing.
1) Alpha testing includes
✓ User testing of a completed information system using simulated data
✓ Recovery testing
• Forces the software (or environment) to fail in order to verify that recovery is properly performed
✓ Security testing
• Verifies that protection mechanisms built into the system will protect it from improper
penetration
✓ Stress testing
• Tries to break the system
✓ Performance testing
• Determines how the system performs on the range of possible environments in which it may be
used

2) Beta Testing
✓ User testing of a completed information system using real data in the real user environment
Installation

▪ The organizational process of

changing over from the current
information system to a new one
▪ Four approaches
✓Direct Installation
• Changing over from the old information
system to a new one by turning off the old
system when the new one is turned on
✓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
Installation (continued)

▪ Four approaches (continued)

✓Single location installation
• Trying out an information system at one
site and using the experience to decide if
and how the new system should be
deployed throughout the organization
✓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
Documenting the System
▪ Each system requires both system
documentation and user documentation.
✓System Documentation
• Detailed information about a system’s
design specifications, its internal
workings, and its functionality
✓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 entity-
relationship diagrams Copyright © cmarix, Written By: Atman Rathod
Documenting the System (continued)
▪ User Documentation
✓Written, or other visual
information, about an
application system, how it
works, and how to use it
✓Figure 10–7 shows an
example of online user
documentation for Microsoft
Word.
Documenting the System (continued)
▪ User Documentation
✓Figure 10–8 illustrates the
structure of an online
reference user’s guide for
Microsoft Excel.
Training Information System Users
▪ Potential Training Topics
✓Use of the system (e.g., how to enter a class
registration request)
✓General computer concepts (e.g., computer files
and how to copy them)
✓Information system concepts (e.g., batch
processing)
✓Organizational concepts (e.g., FIFO inventory
accounting)
✓System management (e.g., how to request
changes to a system)
✓System installation (e.g., how to reconcile
current and new systems during phased
installation)
▪ Training delivery occurs in several ways. Table 10–
5 summarizes these methods
Supporting Information System Users

▪ Support provides ongoing educational and problem-

solving assistance to information system users.
▪ Support is extremely important to users
✓ Need for support driven by
• Lack of standards
• Need to make equipment and software from
different vendors compatible
▪ Most organizations provide support by several
means:
✓ Automated issue tracker (a Web-based tool for
logging, tracking, and assigning system bugs)
✓ Automated support (online support forums (on
private websites) and voice-response systems)
Copyright © NATIC U
✓ Help desk (a single point of contact for all user
inquiries and problems )
Why Implementation Sometimes Fails

▪ Two conditions are necessary for a

successful implementation:

▪ Management support of the

system under development

▪ Involvement of users in the

development process

Copyright © Tenor
Project Closedown

▪ Evaluate team
✓Reassign members to other projects
▪ Notify all affected parties that the
development project is ending and that you
are switching to operation and
maintenance mode

▪ Conduct post project reviews

▪ Close out customer contract

Copyright © GIPHY
✓Formal signoff
Conducting System Maintenance: Types of Maintenance
▪ Corrective maintenance
✓Changes made to a system to repair
flaws in its design, coding, or
implementation
▪ Adaptive maintenance
✓Changes made to a system to evolve its
functionality to changing business needs
or technologies
▪ Perfective maintenance
✓Changes made to a system to add new
features or to improve performance
▪ Preventive maintenance
Copyright © GIPHY
✓Changes made to a system to avoid
possible future problems
Conducting System Maintenance: The Cost of Maintenance

▪ Many organizations allocate as much as 60 to 80 percent of

information systems budget to maintenance

▪ Factors that influence system maintainability:

✓Latent defects (the number of unknown errors existing in
the system after it is installed)
✓Number of customers for a given system (the greater the
number of customers, the greater the maintenance costs.)
✓Quality of system documentation (Without quality
documentation, maintenance effort can increase
exponentially)
✓Maintenance personnel (the best programmers are
assigned to maintenance)
✓Well-structured programs (Well-designed programs are
Copyright © Summit-Virtual-CFO by Anders
easier to understand and fix)
Conducting System Maintenance: Measures of Effectiveness

▪ Because maintenance can be so costly, it is important to measure its

effectiveness.
▪ To measure effectiveness, we must measure these factors:
1) Number of Failures
2) Time between Each Failure
3) Type of Failure
4) Mean Time between Failures (MTBF)
✓A measurement of error occurrences that can be tracked over time
to indicate the quality of a system
Controlling Maintenance Requests

▪ Managing maintenance requests

is an important maintenance
activity
▪ Determine type of request
✓Error
✓Adaptation
✓Enhancement
▪ Figure 10-10 shows a flowchart
for a request procedure
Configuration Management

▪ Configuration Management is the process of assuring that only authorized changes are made
to the system
▪ Baseline Modules
✓Software modules that have been tested, documented, and approved to be included in the
most recently created version of a system
▪ System Librarian
✓A person responsible for controlling the checking out and checking in of baseline modules
when a system is being developed or maintained
▪ Build Routines
✓Guidelines that list the instructions to construct an executable system from the baseline
source code
Questions?

28