Maintenance- All activities done after S\w becomes operational Life time activity of S\W .

May range from 15-20 years where as development of SAME S/w might have taken 2 years. NEED FOR MENTAINANCE Error, changes, enhancement, complexity. CORRECTIVE MENTAINANCEOccurs in response to the system failures that are caused by error. Requires action like S\w restoration by correcting errors. ADAPTIVE MENTAINANCE in response to policy change- income tax rule, ban rate, currency change new technlogy new OS, new compiler

PERFECTINO MENTAINANCE improving efficiency enhancement\deletion to make product better, faster, well documented, cleaner structure

OTHER TYPES OF MENTAINANCE Corrective, adaptive, perfective mentainance leave the program complex. Other type of maintenance refers to reduction or controlling effect of these complexities. -CODE RESTRUCTURING -CODE OPTIMISATION (change program into get a tradeoff between program complex and resource utilization) VERY RALRLE ASKED BY THE USER HENCE ONLY 4% (PIE CHART) PROBLEMS DURING MENTANANCE

Program written by one person and maintained by other in isolation over when a person leaves the organization. Program changed by person who did not understand it clearly resulting in deterioration Poor listing. When there is poor flow of reading the program. Like a good listing will tell that from this component 3 go to component no5 listed on page 11. Or to page no2. Lack of stating their own needs of the user when S\w is run over a period of time When maintainability of the S\w is low. Rigid architecture.

MENTAINANCE IS MANGEABLE It is not necessarily an ad hoc activity. Studies shows that maintenance efforts are usually distributed intoEmergency debugging, routine debugging, environment adaptation, enhancement by user, better documentation need and efficiency improvement. Except for emergency debugging routine the rest can be scheduled properly. Only emergency debugging is situation dependent and cannot be scheduled.

SOLUTIONS OF MENTAINANCE PROBLEMS BUDGET AND EFFORT REALLOCATION More time and resources should be inserted in the development specification and design to more maintainable systems rather than unmaintainable systems. In short more maintainable systems should be developed using advanced requirement specification approachable, design techniques and tools quality, quality assurance procedures etc. COMPLETE REPLACEMENT OF THE SYSTEM After a lot of understanding if it comes out that the cost of mentainance is much more than the cost of developing a new maintainable system their complete replacement with a new system is suggested. However it comes at a greater risk and does not give full guarantee.

MAINTANANCE OF THE EXISTING SYSTEM Making the current system to have potential to evolve to a higher scale provided more sophisticated user driven functionality and integration it with other system in a \cost effective manner RIPPLE EFFECT Same as in progress the modification in one component affect the modification in other. The functional and other component can change and stability (resistance to the amplification of the change.

1. Maintenance Objective(whether corrective, adaptive or perfective is to be done) 2. Program Understanding ( to understand complexity, documentation, and self-description) 3. Generate maintenance proposal i.e how the maintenance activity will proceed.If the program can support extension of critical function the proposal is easier to write 4. Consider ripple effect. Correction made in one component of the software might ripple down to other component and needs to be addressed. 5. Software is tested and if it does not pass the test, steps from step 1 onwards are repeated.

MAINTENANCE MODELS 1.QUICK FIX MODEL y y y y y Ad-hoc approach Done without detail analysis of long term effects like ripple effects. Can be used for small projects where development and maintenance is done by the same person who can understand the project even without detailed documentation. Less time consuming for small projects and can satisfy urgent demand of the client. Unrealistic for even medium size project and long term upgrades.

2.ITERATIVE ENHANCEMENT MODEL Iterative enhance model of development is applied to maintenance . Three stages of this model are y y y Analysis of existing system Characterization of proposed modification Redesign and implementation.

Assumes that complete documentation of each phase of SDLC of the system is available . The modification of the highest level documentation(rather than fixing the error immediately) that is affect by the proposed change is the starting point. Therest of the documentation and design is modified removing the ripple effect. Uses other models likequick fix .

3. REUSE ENHANCEMENT MODEL y y y y Reusable, modifiable components are identified. The above parts are analyzed and understood. The above parts are modified according to new requirement Modified parts are integrated into new system

4.BOHEMS MODEL Based on Economics model y y y y y Management decisions of maintenance are made after applying cost benefit evaluations to a set of proposed changes. The approved changes are allocated their own budget and resources. Maintenance manager has to balance the maintenance objectives with environmental constraint. Changes are implemented New software is used Evaluation is done. New changes can be proposed that can restart the cycle.

6. TAUTE MAINTENANCE MODEL Consists of 8 phases. Change Request phase-initiated by client and categorized(corrective, adaptive etc.) by maintenance manager Estimate Phase -Estimates time and resources required to make the changes.Impct of ripple effect caused by the changes is also studied. Schedule Phase-Identify change request for the next scheduled release. Programming Phase Source code modification is performed. Test Phase- Regression testing is done Documentation Phase-System and user documentation of the new system is done. Release phase- New software along with updated documentation is delivered to the client.Acceptance testing is performed. Operation Phase S/W is used and if new problems or new requirements arise we start with change request phase. REVERSE ENGINEERING To find hidden ,unknownand difficult information about the existing system in absence of proper documentation and unstructured nature of the system