System Implementation

Subject: Information Systems

Lecturer : Quratulain
Course Code: CIT - 667
 ● System implementation
Content ● Maintenance activities

System Implementation ● System Testing

Implementation
• Implementation phase - distribute the system to all of
the knowledge workers and they begin using the system
to perform their everyday jobs

• Two primary implementation activities

1. Write detailed user documentation
• User documentation - highlights how to use the system
Implementation
2. Provide training for the system users
• Online training - runs over the Internet or off a
CD-ROM
• Workshop training - is held in a classroom
environment and lead by an instructor
Implementation
• Choose the right implementation method
– Parallel implementation – use both the old and new system
simultaneously
– Plunge implementation – discard the old system completely and use
the new
– Pilot implementation – start with small groups of people on the new
system and gradually add more users
– Phased implementation – implement the new system in phases
Implementation & Maintenance
• 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 Process 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
The Process of Coding, Testing and
Installation: Deliverables
The Process 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
The Process of Documenting the
System, Training Users and
Supporting Users
• Deliverables
– Documentation
• System documentation
• User documentation
– User training plan
• Classes
• Tutorials
– User training modules
• Training materials
• Computer-based training aids
– User support plan
• Help desk
• On-line help
• Bulletin boards and other support mechanisms
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
Maintenance activities in System implementations
System Testing
Testing

• verifies that the system works and meets all of the

business requirements defined in the analysis
phase
• Two primary testing activities:
1. Write the test conditions
• Test conditions - the detailed steps the system must perform
along with the expected results of each step
The Process of Maintaining
Information Systems
• Deliverables and Outcomes
– Development of a new version of the
software, new versions of all design
documents and training materials created or
modified during the maintenance effort
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
• Inspection
– A testing technique in which participants examine program code
for predictable language-specific errors
• Walkthrough
– A peer group review of any product created during the systems
development process; also called a structured walkthrough
• Desk Checking
– A testing technique in which the program code is sequentially
executed manually by the reviewer
Software Application Testing:
Types of Testing
• Unit Testing
– Each module is tested alone in an attempt to discover any
errors in its code, also called module testing
• 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
Software Application Testing:
Types of Testing
• 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
• 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
1. The purpose of the testing is confirming that the
system satisfies requirements
2. Testing must be planned
3. 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
Test Case
Software Application Testing:
Acceptance Testing by Users
• The process whereby actual users test a completed
information system, the end result of which is the users’
acceptance of it
Software Application Testing:
Acceptance Testing by Users
• Alpha Testing
– 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
Software Application Testing:
Acceptance Testing by Users
• Beta Testing
– User testing of a completed information system
using real data in the real user environment
What’s Next?

System Implementation