Please enable JavaScript.
Coggle requires JavaScript to display documents.
SAD: MODULE 5 (CHAPTER 13) SYSTEM IMPLEMENTATION (6 MAJOR ACTIVITIES…
SAD: MODULE 5 (CHAPTER 13)
SYSTEM IMPLEMENTATION
PURPOSE
CONVERT
To convert final physical system specs into working and reliable software
DOCUMENT
To document work that has been done
PROVIDE
To provide help for current and future users
6 MAJOR ACTIVITIES
CODING
WORKING
Physical design specs are turned into working computer code
TESTING
Tests are performed using various strategies and in parallel with coding
Master test plan: Analysis phase
Unit, system, and integration test plans: Design phase
Actual testing: Implementation phase
7 TYPES OF TESTS
INSPECTION
examine
Participants examine program code for predictable language-specific code
WALKTHROUGH
peer grp review
A peer grp review of any product created during the systems development process, including code
DESK CHECKING
sequentially
Program code is sequentially executed manually by the reviewer
UNIT TESTING
module
Each module is tested alone in an attempt to discover any errors in its code
INTEGRATION TESTING
bringing together modules
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
SYSTEM TESTING
bringing together programs
The bringing together of all the programs that a system comprises for testing purposes
programs are typically integrated in top-down, incremental fashion
STUB TESTING
?
Used in testing modules, 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
TESTING PROCESS
Purpose:confirm
To confirm that system satisfies the requirements
Test Case:scenario
A specific of transactions. queries or nav paths
represent either:
typical system use, critical system use, abnormal system use
ACCEPTANCE TESTING BY USERS
actual users
Actual users test a completed information system , the end result of which is the user's acceptance of it
Alpha Testing
simulated data
User testing of a completed information system using simulated data
Types of Alpha Test
Recovery Testing
fail
Forces software to fail in order to verify that recovery is properly performed
Security Testing
protection mechanism
Verified that protection mechanisms built into the system will protect it from improper penetration
Stress Testing
break
Tries to break the system
Performance Testing
possible environments
Determines how the system performs on the range of possible environments in which it may be used
Beta Testing
real data
User testing of a completed information system using real data in the real user environment
INSTALLATION
REPLACED
The current system is replaced by a new system
4 installation strategies
Direct Installation
turn off/on
Changing over from the old system to a new one by turning off the old system when the new system is turned on
Parallel Installation
same time
Running the old information system and the new one at the same time until management decides the old system can be turned off
Single-location/pilot Installation
at one site
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 org.
Phased Installation
incrementally
Changing from the old information system to the new one incrementally, starting with one or a few functional components and the gradually extending the installation to cover the whole new system
DOCUMENTATION
FOR WHO?
Information system personnel who will maintain the system throughout its productive life
People who will use the system as part of their daily lives
cth: System documentation, user documentation, user training plan, user training modules
TRAINING
SUPPORT
