1. Chapter 10

2. 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

3. Chapter Objectives
Explain the importance of software quality assurance
Describe the application development process
Differentiate between program, system, operations, and user documentation
Describe test and operational environment
Describe different training options
Identify and describe changeover methods
Explain post-implementation evaluation 3

4. Software Quality Assurance
Software Engineering
Software development process that stresses solid design, accurate documentation, and careful testing.
Software Engineering Institute (SEI)
Capability Maturity Model (CMM)
Capability Maturity Model Integration (CMMI)
International Organization 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

5. Overview of Application Development
Application Development Steps

6. Testing the System Unit Testing Test data
Programmers must test programs that interact with other programs and files individually
Integration Testing
Integration testing, or link testing
Testing the programs independently does not guarantee that the data passed between them is correct
System Testing
Acceptance tests
You should regard thorough testing as a cost-effective means of providing a quality product

7. Documentation Program Documentation System Documentation
Operations Documentation
User Documentation

8. 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

9. Operational and Test Environments
The environment for the actual system operation is called the operational environment or production environment
The environment that analysts and programmers use to develop and maintain programs is called the test environment
A separate test environment is necessary to maintain system security and integrity and protect the operational environment

10. Training Vendor Training Webinars and Podcasts
Outside Training Resources
In-House Training

11. Data Conversion Data Conversion Strategies
The old system might be capable of exporting data in an acceptable format for the new system or in a standard format such as ASCII or ODBC
If a standard format is not available, you must develop a program to extract the data and convert it
It is essential that the new system be loaded with accurate, error-free data

12. System Changeover Direct Cutover Involves more risk
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

13. 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

14. 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

15. 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

16. Post-Implementation Tasks
Post-Implementation Evaluation (Review)
Includes feedback for the following areas:
Accuracy, completeness, and timeliness of information system output
User satisfaction
System reliability
Adequacy of system controls and security measures
Hardware efficiency and platform performance
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

17. Post-Implementation Tasks (Cont…)
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
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

18. Chapter Summary
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 49

19. Chapter Summary
Data conversion often is necessary when installing a new information system
System changeover is the process of putting the new system into operation
A post-implementation evaluation assesses and reports on the quality of the new system and the work done by the project team 49