System Maintenance

System Maintenance

Karen Fetrow

CMGT 554

July 7, 2015

Ed Odjaghian

System Maintenance

Introduction:

        System maintenance is an ongoing process for the software design flaws of an SDLC that

can include 60-80 percent of the budget. It includes activities after the installation of the

software. This is what keeps the system operation to its fullest. It begins with implementation of

the new SDLC systems it has to be continually Monitored and maintained and is ongoing from

then on with requests and errors. The maintenance of an SDLC is problem resolution to existing systems and removal of the error in the system.

The Phases of the implementation and maintenance actually loop into each other from the

beginning to the end and back to the beginning again for each new maintenance requests then

repeated many times for all and any needs the system and users have. The Maintenance is a set

of activities for the whole system development that ultimately will end with new software

versions and new designs documentation as well as training to follow on the new materials and

new processes. Maintenance composes half of the cost involved.

There is adaptive maintenance and corrective maintenances, perfective and preventative.  

1. Corrective maintenance is finding the errors and removing them.  It is generally agreed to

find 100 percent of all errors on a large system installation are extremely rare. Adaptive

maintenance is fixing the errors and implementing new requests.  

2-Preventative

This is safeguarding and stopping ahead of time to save money and future costs involving the

system while perfective is making enhancements for performance and usability.

Replacement of the old software with a new updated version as well as any training

needed for the user.

3-Perfective 

Perfective maintenance is when the new system has been being used for a time and the

weakness need minor changes for improvements. It concerns functional enhancements to the

systems activities to increase performance or user interface.

4-Preventative

        Preventative maintenance it to help keep the system up and running smoothly and be able  

To locate and identify problems before they become a costly problem This is used to increase the

maintainability for updating documentation, adding comments and improving the modular

structure of the system

        System Maintenance requires everyone that uses the system to be observant and report at

all times needs and problems. There are test ran to create system checks to also keep a smooth.

[pic 1]

Pg. 324

Maintenance:

The maintenance of an SDLC is problem resolution to existing systems and removal of

the error in the system.

There are Five major maintenance tasks to keep the system maintenance at all times.

They are:

1-Identification by obtaining maintenance request

This involves finding, noticing and documenting the need for a request or error to be

changed and fixed. - The first step requires a process of collecting a formal maintenance

requests for SSR. This is used for a problems or feature that is asked to be added to the

existing system or a change in the environment or a change in the requirements of the systems

software. After initial installation and some time for the users have had some experience using

the software needs not identified or uncovered initially can be a concern. There can also be input

data changes that need updating or format that need changing. These will all require

modifications on the software which will be an adaptive maintenance.

2- Transforming the requests into changes

        The requests then need to be presented, explained and analyzed verses cost and put into

code to improve on or add to the existing software then implementing the change.

3-Designing the changes

The design of the changes need to make the necessary changes or

additions to the existing software. This will remedy the requests as well as repair or remove any

errors or fixes needed to the present software

4- Implementing 

I the actual replacement and installing or altering of the existing software as well as altering the

changes to the users. The installation of the modification; The existing software will be modified

to support the request. The outcome will be rewritten software creating new versions of it. This is

a similar process to the development of the software. The old and new will share some of the

same codes. The old version needs to be understood in order to write a new version. At this point