Systems Analysis & Design 1

10th Edition

CHAPTER 8
Systems Implementation
 Phase Description
2

 PLANNING
 ANALYSIS
 Requirements Modeling
 Data & Process Modeling
 Development Strategies
 DESIGN
 Output & User Interface Design
 Data Design
 System Architecture (not covered in syllabus)
 IMPLEMENTATION
 SYSTEMS OPERATION, SUPPORT &
SECURITY
 Content
3

 Application Development
 Testing
 Documentation
 Training
 Data conversion
 System changeover
 Post-implementation evaluation
 Final Report to Management
 Application Development
4

 Constructing programs and code modules

 Coding – turn program logic into
executable computer instructions
 Testing
5

1. Compile (syntax errors)

2. Desk checks (logic error)
• Structured walkthrough, code review
• Errors, quality standards, verification
3. Design walkthrough (interface review)
4. Unit Testing
5. Integration Testing
6. System Testing
 Unit Testing
6

 Test individual program or module

 Eliminate execution errors & logic errors
 Test data – correct & erroneous data
 Stub testing – simulate program outcome
 Test plan – detailed procedures
describing how, when, who and what
 Integration Testing
7

 Link testing
 Testing 2 or more programs that depends
on each other
 To ensure data is correctly passed
 System Testing
8

• Acceptance testing
• Sample of actual data and produce report
• Objectives:
o Perform final test of all programs
o Ensure & demonstrate:
 system will handle all input data properly
 IT staff has the documentation and instructions needed
 users can interact with the system successfully
 system components are integrated properly
 information system can handle predicted volumes of data
 Unit, Integration & System
Testing
9
 Documentation
10

 Describes an IS and helps users,

managers and IT staff who must interact
with it.

 Purpose:
o Support system’s users
o To assist IT staff in modifying and maintaining
the system
 Documentation Types
11

 Program documentation
 System documentation
 Operations documentation
 User documentation
Program & System
Documentation
 Program documentation
o Input, output & processing logic

 System documentation
o Functions & implementation
o Data dictionary, DFD, object models, screen
layouts, source document, system request
o Support & maintenance

12
Operations Documentation
 Used by centralized operations IT support group
 Information for distributing and processing online &
printed output
 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
 Special forms required, including online forms
 Error and informational messages to operators and restart
procedures
 Special instructions, such as security requirements

13
User Documentation
 Instructions and information for users
 User manual, help screens and tutorials
 Technical writer

14
User Documentation
 System overview – features, capabilities, and limitations
 Description of source document content,
 Overview of menu and data entry screen options
 Report examples
 Security and audit trail information
 Responsibility for specific input, output, or processing
requirements
 Change request & problem reporting procedures
 Examples of exceptions and error situations
 Frequently asked questions (FAQs)
 Explanation of how to get help

15
User Documentation

16
Operational & Test
Environment

Develop and maintain Actual system

programs operation
Changes must be Production operation
tested and approved
Limited access even to
before transfer to OE
IT staff
17
 Training

How to perform
day-to-day
operations

System overview
Ensure users trained
Support properly

System functions
Support business req
User skills needed
18
Training

 Vendor training
 Webinars & Podcasts
 Outside Training Resources
 In-House Training

19
Data Conversion

 Load data into new system

 Conversion process needs to be tested
 Strategies:
 Automatic data conversion – export data
 Develop data extraction & conversion programs
 Manual data entering (if replace manual
system)
 Security & control:
 Protect data from unauthorized access
 Prevent erroneous input

20
System Changeover
 Put new system
online, retire the old
system

21
 Direct Cutover
22

 Changes occur immediately

 Least expensive – operate 1 system only
 Involves more risk
 Unable to compare output
 Cannot revert to old system
 Usually for: commercial software packages
, non-critical systems, incompatibility
 Parallel Operation
23

 Both new & old systems operate fully

 Same input data, compare output
 Lower risk
 Able to revert
 Easier to verify
 Most costly
 Pilot Operation
24

 Implement complete new system at a

selected location only
 Pilot site
 Less expensive than parallel
 Phased Operation
25

 Implemented in modules
System Changeover

26
Post-Implementation
Evaluation
 Assesses overall quality of IS
 Helps improve IT development practices
 Includes:
 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
 Effectiveness of database implementation
27
Post-Implementation
Evaluation

28
Final Report to Management

 Final versions of all system documentation

 Planned modifications and enhancements
to the system
 Recap of all systems development costs
and schedules
 Comparison of actual costs and schedules
to the original estimates
 Post-implementation evaluation, if it has
been performed

29
 Chapter Summary
30

• The systems implementation phase consists of

application development, testing, installation,
and evaluation of the new system
• Analysts and technical writers also prepare
operations documentation and user
documentation
• Develop a training program
• A post-implementation evaluation assesses
and reports on the quality of the new system
and the work done by the project team
 Chapter Summary
31

• The final report to management includes

the final system documentation,
describes any future system
enhancements that already have been
identified, and details the project costs
• The report represents the end of the
development effort and the beginning of
the new system’s operational life
• Chapter 8 complete