What is maintenance phase in software engineering

Click here to view master references table. No references have been currently identified for this SWE. If you wish to suggest a reference, please leave a comment below. The purpose is to provide examples of tools being used across the Agency and to help projects and centers decide what tools to consider.

The evidence for confirmation of the activity can take any number of different forms, depending on the activity in the task. Examples are:. Software assurance will perform audits of the maintenance processes and procedures in use during this phase. Some of the processes and procedures to audit include the configuration management processes, change management processes, the process to transition changed software into the operational environment, and the testing procedures, particularly those associated with testing safety-critical functions and regression testing.

Every task that involves performing an audit should also clarify that all audit findings are promptly shared with the project will be addressed in the handbook guidance. Return to Software Engineering Community of Practice. Introduction B. Institutional Requirements C. Project Software Requirements D.

Topics E. Tools, References, and Terms F. Here we also discuss the introduction and need for software maintenance along with advantages and disadvantages. You may also have a look at the following articles to learn more —.

Submit Next Question. By signing up, you agree to our Terms of Use and Privacy Policy. Forgot Password? This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the cookie policy. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to our Privacy Policy. Software Maintenance By Priya Pedamkar.

Skip to content. Change Language. Related Articles. Introduction of Software Engineering. Software Requirements. Software Testing and Debugging. Table of Contents. Improve Article. Save Article. Preventive Maintenance - This includes modifications and updations to prevent future problems of the software. It aims to attend problems, which are not significant at this moment but may cause serious issues in future. Reports suggest that the cost of maintenance is high.

There are various factors, which trigger maintenance cost go high, such as:. IEEE provides a framework for sequential maintenance process activities. It can be used in iterative manner and can be extended so that customized items and processes can be included. It is generated by user or system may itself report via logs or error messages.

Here, the maintenance type is classified also. Analysis - The modification is analyzed for its impact on the system including safety and security implications.

If probable impact is severe, alternative solution is looked for. A set of required modifications is then materialized into requirement specifications. Design - New modules, which need to be replaced or modified, are designed against requirement specifications set in the previous stage. Test cases are created for validation and verification. Implementation - The new modules are coded with the help of structured design created in the design step.

Every programmer is expected to do unit testing in parallel. System Testing - Integration testing is done among newly created modules. Integration testing is also carried out between new modules and the system. Finally the system is tested as a whole, following regressive testing procedures.

Acceptance Testing - After testing the system internally, it is tested for acceptance with the help of users. If at this state, user complaints some issues they are addressed or noted to address in next iteration.

Delivery - After acceptance test, the system is deployed all over the organization either by small update package or fresh installation of the system.