Implementation n Maintenance

8/8/2019 Implementation n Maintenance

1/22

Software Implementation &

Maintenance


2/22

Software Implementation and

Maintenance

Implementation means the process of convertinga new or a revised system design into anoperational one.

The other aspects are the post-implementationreview and software maintenance. There arethree types of implementation:

1. Implementation of a computer system to replacea manual system.

2. Implementation of a new computer system toreplace an existing one.

3. Implementation of a modified application toreplace an existing one.


3/22

Conversion: The objective is to put the tested

system into operation. Conversion should be

exciting because it is the last step before system

begins to show results. If not, properly planned,then, things can go wrong?

For many first-time users, this theme is familiar?

What went wrong? Conversions are oftenfiasco?


4/22

Activities forConversion

Conversion Plan Testing System

Conversion begins with a review of project plan

and system test documentation and

implementation plan. The parties involved are:

- User

- Project team

- Programmers- Data capture form filling and checking


5/22

2. Files conversion: File conversioninvolves capturing data and creatingcomputerised files from existing files.

Data entry staff

Staff training

Database is prime concern.

3. Creating test files: programs should bechecked on test data files.


6/22

4. Train Personnel: Training aids

1. User manual

2. Screen menu3. Data dictionary

4. Job aids

5. Wall charts


7/22

5. Conversion of physicalFacilities:

Communication networkHardware

6. Conversion of Administrative procedures


8/22

Resistance to change: People will resist changes,how they will react:

1. Hostility: Non-co-operation, fear

2. Withdrawal from the cause of stress-supervisor going

sick3. Refusing to accept the computer

4. Adverse effect on employees status, job satisfaction

5. May even sabotage the system

6. Unable to understand the new system- communicationgap


9/22

There are several ways to reduce resistance tosystem change

1. Identify and discuss the defects in the present

system.2. Convince them that changeover will improve

the quality of work and also it will help them all.

3. Establish open communication between user

and project team.4. Invite and use employee participation in all

phases of conversion process


10/22

Different Ways ofConversion:

1. Parallel Running: new and old system

2. Direct conversion: Totally change-overi.e. only new system

3. Gradual switch over: Partial conversion:

step by step conversion


11/22

Main activities:

1. Programming

2. Test data preparation and system testing3. Data collection/ data capture :

i) filling of forms ii) Data entry

4. Training of users

5. Conversion: Change-over methods direct, gradual, parallel.


12/22

Post Implementation Review

Operational systems are quickly taken for

granted. Every system requires periodic

evaluation after implementation. A post-

implementation review measures the systemsperformance against predefined requirements. A

post-implementation review determines, how

well the system continues to meet performance

specifications. It also provides information todetermine whether major redesign is necessary.


13/22

1. How well system meets the stated

requirements ?

2. Whether major redesign is necessary?

3. Some modification (minor) is needed?

4. Actual projects costs exceed initial estimates.

5. Actual project benefits/initial estimates

6. Major problems surfaced during conversion(review).


14/22

Activities for Post-Implementation

review:

1. Request for review2. Review plan: formal review plan

Objectives of review

Type of evaluation Time schedule


15/22

a) Administrative Plan: Area objectives, costs,performance, benefits

b) Personnel requirements plan: review, performanceobjectives and training performance to data personnel

performance, training performance

c) Hardware plan

d) Documentation review Plan: Instructions for filling theforms, checking the forms, data entry/menu driven;

Manuals- flow charts/charts, dos and donts; evaluate theaccuracy and completeness of documentation compiledto data, documentation standards


16/22

Software Maintenance: Maintenance is

important part of development.

Programmers spend more time

maintaining program than they do writing

them. Software maintainance is required

because:


17/22

1. Software is a product designed in an adhoc fashion with fewstandards

2. Poorly documented, difficult to maintain

3. Maintenance is not as rewarding as developing system.

4. It is assumed that maintenance requires no skill or experience.

5. Users are not fully aware of maintenance problems or its high cost.6. Few tools/techniques are available.

7. A good test plan is lacking

8. Standards, procedures and guidelines are poorly defined andenforced

9. Mostly delegated to junior programmer10.Mostly maintain without care for structure/documentation

11.Programmers expect they will not be there when the implementationtakes place.


18/22

Maintenance/Enhancement: Maintenance can beclassified as

1. Corrective maintenance: means repairing processing/performance failures, making changes because of

previously uncorrected problems or false assumptions.2. Adaptive maintenance: means changing the program

functions and changes in hardware and softwareenvironment.

3.Perfective maintenance: means enhancing theperformance/modifying the program to respond to usersadditional or changing needs.

4. Enhancement


19/22

Of these, more time and money is spent onperfective maintenance thancorrective/adaptive.

Maintenance covers a wide range of activitiesincluding:

1. Correcting coding and design errors.

2. Updating documentation/test data.

3. Upgrading user support.4. Enhancement- adding, modifying or

redeveloping the code to support changes.


20/22

5. It is necessary to keep up with changing userneeds and operational environment.

6. Labor-intensive nature.

7. Reducing maintenance costs- maintenancemanagement audit, software system audit,software modification.

8. Proper Maintenance Plan: makes the software

more reliable, improved response time incorrecting errors, improved user satisfaction,higher morale among maintenance staff.


21/22

To put maintenance in its proper perspective

requires considerable skill and experience, and

in an important and ongoing aspect of system

development.Maintenance demands more orientation and

training than any other programming activities.

The environment must recognize the needs of

the maintenance programmer for tools, methods

and training.


22/22

Documents

Implementation n Maintenance