Lecture # 8

INTRODUCTION TO
SYSTEMS ANALYSIS & DESIGN
7. Systems Coding & Testing
8. Implementation & Evaluation
Phase Description
 Systems Implementation is the fourth of five phases in
the systems development life cycle (SDLC)
 Includes application development, testing,
documentation, training, data conversion, system
changeover, and post-implementation evaluation of
the results
Chapter Objectives
 Explain the importance of software quality assurance
and software engineering
 Describe the application development process
 Explain the coding process and how code is
generated
 Explain unit testing, integration testing, and system
testing
Chapter Objectives
 Differentiate between program, system, operations,
and user documentation
 List the main steps in system installation and
evaluation
 Develop an overall training plan with specific
objectives for each group of participants, compare
in-house and outside training providers, and
describe effective training techniques
Chapter Objectives
 Identify and describe changeover methods
 Explain post-implementation evaluation
 Describe the final report to management
Introduction
 The system design specification serves as a blueprint
for constructing the new system
 The initial task is application development
 Before a changeover can occur, the system must be
tested and documented carefully, users must be
trained, and existing data must be converted
 A formal evaluation of the results takes place as part
of a final report to management
Software Quality Assurance
 In today’s competitive business environment,
companies are intensely concerned with the quality of
their products and services
 Rigorous testing catches errors in the implementation
stage
Software
 InternationalQuality
OrganizationAssurance
for Standardization
(ISO)
 Many firms seek assurance that software systems will
meet rigid quality standards
 In 1991, ISO established a set of guidelines called ISO
9000-3
 ISO requires a specific development plan, which
outlines a step-by-step process for transforming user
requirements into a finished product
Overview of Application
Development
 Application development
 Objective is to translate the logical design into
program and code modules that will function properly
 Creation of the System Design
 The tasks involved in system design produced an overall
design and a plan for physical implementation
Overview of Application
Development
 Application Development Steps
 Module
 Start by reviewing documentation from prior SDLC
phases and creating a set of program designs
 After the design is created, coding can begin
Structured Application Development
 Top-down approach
 Partitioning
 Modular design
 Must proceed carefully, with constant input from
programmers and IT management to achieve a
sound, well-integrated structure
 Must ensure that integration capability is built into
each design and thoroughly tested
Coding
 Coding
 Programming Environments
 Each IT departments has its own programming
environment and standards
 Integrated development environments (IDEs)
 Generating Code
 Can generate editable program code directly from
macros, keystrokes, or mouse actions
Testing the System
 After coding, a programmer must test each program to
make sure that it functions correctly
 Syntax errors
 Desk checking
 Structured walkthrough, or code review
 Design walkthrough
Documentation
 System Documentation
 Includes data dictionary entries, data flow diagrams,
object models, screen layouts, source documents, and
the systems request that initiated the project
 During systems implementation, an analyst must review
system documentation to verify that it is complete,
accurate, and up-to-date, including any changes made
during the implementation process
Documentation
 Operations Documentation
 Includes the following information:
 Program, systems analyst, programmer, and system
identification
 Scheduling information for printed output, such as report run
frequency and deadlines
 Input files and where they originate; and output files and
destinations
 E-mail and report distribution lists
Documentation
 User Documentation
 Programmers or systems analysts usually create
program and system documentation
 You need someone with expert skills in this area
doing the development, just as you need someone
with expert skills developing the software
 Systems analysts usually are responsible for
preparing documentation to help users learn the
system
Documentation
 User Documentation
 Includes the following:
 A system overview that clearly describes all major system
features, capabilities, and limitations
 Description of source document content, preparation,
processing, and samples
 Overview of menu and data entry screen options,
contents, and processing instructions
 Examples of reports that are produced regularly or
available at the user’s request, including samples
Documentation
 User Documentation
 Includes the following:
 Security and audit trail information
 Explanation of responsibility for specific input, output, or
processing requirements
 Procedures for requesting changes and reporting problems
 Examples of exceptions and error situations
 Frequently asked questions (FAQs)
 Explanation of how to get help and procedures for updating
the user manual
Management Approval
 After system testing is complete, you present the
results to management
 If system testing produced no technical, economical,
or operational problems, management determines a
schedule for system installation and evaluation
Training
 A successful information system requires training
for users, managers, and IT staff members
 The entire systems development effort can depend
on whether or not people understand the system
and know how to use it effectively
Training
 Training Plan
 The first step is to identify who should receive training
and what training is needed
 The three main groups for training are users, managers,
and IT staff
 You must determine how the company will provide
training
System Changeover
 System changeover is the process of putting the new
information system online and retiring the old system
 The four changeover methods are direct cutover,
parallel operation, pilot operation, and phased
operation
System Changeover
 Direct Cutover
 Involves more risk than other changeover methods
 Companies often choose the direct cutover method
for implementing commercial software packages
 Cyclical information systems usually are converted
using the direct cutover method at the beginning of a
quarter, calendar year, or fiscal year
System Changeover
 Parallel Operation
 Easier to verify that the new system is working
properly under parallel operation than under direct
cutover
 Running both systems might place a burden on the
operating environment and cause processing delay
 Is not practical if the old and new systems are
incompatible technically
 Also is inappropriate when the two systems perform
different functions
System Changeover
 Pilot Operation
 The group that uses the new system first is called the
pilot site
 The old system continues to operate for the entire
organization
 After they system proves successful at the pilot site, it
is implemented in the rest of the organization,
usually using the direct cutover method
 Is a combination of parallel operation and direct
cutover methods
System Changeover
 Phased Operation
 You give a part of the system to all users
 The risk of errors or failures is limited to the
implemented module only
 Is less expensive than full parallel operation
 Is not possible, however, if the system cannot be
separated easily into logical modules or segments
Post-Implementation Tasks
 Post-Implementation Evaluation
 Includes feedback for the following areas:
 Accuracy, completeness, and timeliness of information system
output
 User satisfaction
 System reliability and maintainability
 Adequacy of system controls and security measures
 Hardware efficiency and platform performance
Post-Implementation Tasks
 Post-Implementation Evaluation
 Includes feedback for the following areas:
 Effectiveness of data base implementation
 Performance of the IT team
 Completeness and quality of documentation
 Quality and effectiveness of training
 Accuracy of cost-benefit estimates and development
schedules
Post-Implementation Tasks
 Post-Implementation Evaluation
 When evaluating a system, you should:
 Interview members of management and key users
 Observe users and computer operations personnel actually
working with the new information system
 Read all documentation and training materials
Post-Implementation Tasks
 Post-Implementation Evaluation
 When evaluating a system, you should:
 Examine all source documents, output reports, and
screen displays
 Use questionnaires to gather information and opinions
form a large number of users
 Analyze maintenance and help desk logs
 Whenever possible, people who were not directly
involved in developing the system should conduct
the post-implementation evaluation
Post-Implementation
 Final Report to Management
Tasks
 Your report should include the following:
 Final versions of all system documentation
 Planned modifications and enhancements to the system
that have been identified
 Recap of all systems development costs and schedules
Post-Implementation Tasks
 Final Report to Management
 Your report should include the following:
 A comparison of actual costs and schedules to the original
estimates
 Post-implementation evaluation, if it has been performed.
 Marks the end of systems development work