implementation phase

1111

IMPLEMENTATION PHASE● 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

2222

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

3333

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

4444


● Application Development Steps– Module– After the design is

created, coding can begin

5555


● Project Management– Even a modest-sized project might have

hundreds or even thousands of modules– Important to set realistic schedules, meet

project deadlines, control costs, and maintain quality

– Should use project management tools and techniques

6666

Structured Application Development

● Top-down approach ● 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

7777

Testing the System● After coding, a programmer must

test each program to make sure that it functions correctly

● Syntax errors● Desk checking

– Logic errors● Structured walkthrough, or code

review● Design walkthrough

8888

Testing the System● Unit Testing

– Test data– Programmers must test programs that

interact with other programs and files individually

– Regardless of who creates the test plan, the project manager or a designated analyst also reviews the final test results

9999

Testing the System● Integration Testing

– Integration testing, or link testing– Testing the programs independently does

not guarantee that the data passed between them is correct

– A testing sequence should not move to the integration stage unless it has performed properly in all unit tests

10101010

Testing the System● System Testing

– Major objectives:• Perform a final test of all programs• Verify that the system will handle all input

data properly, both valid and invalid• Ensure that the IT staff has the

documentation and instructions needed to operate the system properly and that backup and restart capabilities of the system are adequate

11111111

Testing the System● System Testing

– Major objectives:• Demonstrate that users can interact with the

system successfully• Verify that all system components are

integrated properly and that actual processing situations will be handled correctly

• Confirm that the information system can handle predicted volumes of data in a timely and efficient manner

12121212

Documentation● Documentation● Program Documentation● System Documentation● Operations Documentation● User Documentation

– Online documentation

13131313

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

14141414

System Installation and Evaluation

● Remaining steps in systems implementation:– Prepare a separate operational and test

environment– Provide training for users, managers,

and IT staff– Perform data conversion and system

changeover– Carry out post-implementation

evaluation of the system– Present a final report to management

15151515

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

16161616

Operational and Test Environments

17171717

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

18181818

Training● Outside Training Resources

– Many training consultants, institutes, and firms are available that provide either standardized or customized training packages

– You can contact a training provider and obtain references from clients

19191919

Training● In-House Training

– The IT staff and user departments often share responsibility

– When developing a training program, you should keep the following guidelines in mind:

• Train people in groups, with separate training programs for distinct groups

• Select the most effective place to conduct the training

• Prepare effective training materials, including interactive tutorials

20202020

Training● In-House Training

– When developing a training program, you should keep the following guidelines in mind:

• Rely on previous trainees• Train-the-trainer strategy

– When Training is complete, many organizations conduct a full-scale test, or simulation

21212121

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

– Often requires additional data items, which might require manual entry

22222222

Data Conversion● Data Conversion Security and

Controls– You must ensure that all system control

measures are in place and operational to protect data from unauthorized access and to help prevent erroneous input

– Some errors will occur– It is essential that the new system be

loaded with accurate, error-free data

23232323

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

24242424

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

25252525

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 the 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

26262626

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

27272727

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

28282828


– Includes feedback for the following areas:• Effectiveness of database implementation• Performance of the IT team• Completeness and quality of documentation• Quality and effectiveness of training• Accuracy of cost-benefit estimates and

development schedules

29292929


– 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

30303030


– Users can forget details of the developmental effort if too much time elapses

– Pressure to finish the project sooner usually results in an earlier evaluation in order to allow the IT department to move on to other tasks

– Ideally, conducting a post-implementation evaluation should be standard practice for all information systems projects

31313131

Post-Implementation Tasks● Final Report to Management

– 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• 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

implementation phase

Documents