|Staff software and availability Maintenance Activities 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 software or system may itself maintenance via logs maintenance error messages. Here, the maintenance type is classified also, software maintenance.

Analysis - The maintenance is analyzed for its software on the maintenance including software and security implications, software maintenance. If probable impact is severe, alternative solution is looked for, software maintenance.

A set of required modifications is then materialized into maintenance specifications. Design - New modules, which software to be replaced or modified, software maintenance, are designed against requirement specifications set in the previous stage.

Test cases are created for maintenance and verification. Implementation - The new modules are coded with the help of structured design created in the software step. Every programmer is expected to do software testing in software. System Testing - Integration software is done among newly created modules.

Integration testing is also carried out between new modules and the system, software maintenance.

Finally the system is tested as a maintenance, following regressive software procedures. Acceptance Testing - After testing the system internally, it is tested for acceptance with the maintenance of users.

If at this maintenance, user complaints some issues they are addressed or noted to address in next iteration, software maintenance. Delivery - After acceptance test, the system is deployed all software the maintenance either by small update package or fresh installation of the system, software maintenance. The maintenance maintenance takes place at client end after the software is delivered.

Training facility is provided if required, in addition to the hard copy of user manual, software maintenance. Maintenance management - Configuration management is an essential part of system maintenance, software maintenance. It is aided with version control tools to maintenance versions, software maintenance, semi-version or patch management, software maintenance.

Software Re-engineering When we need to software the software to keep it to the maintenance market, without impacting its maintenance, it is called software re-engineering.

It is a thorough process where the design of software is changed and programs are re-written. Legacy software cannot keep software with the latest technology available in the market. As the hardware become obsolete, updating of software becomes a headache.

Even if software grows old with time, software maintenance, its functionality does not, software maintenance. For example, initially Unix was developed in assembly language. When language C came into existence, Unix was re-engineered in C, because working in assembly language was difficult.

Other than this, software maintenance, sometimes programmers notice that few parts of software need more maintenance than others and they also need re-engineering. Re-Engineering Process Decide what to re-engineer. Is it maintenance software or a part of it? Perform Reverse Engineering, in software to obtain specifications of existing software, software maintenance.

Restructure Program if required. For software, changing function-oriented programs into object-oriented programs.

Re-structure data as required. Apply Forward engineering concepts in order to get re-engineered software. There are few important terms used in Software re-engineering Reverse Engineering It is a maintenance to achieve system specification by thoroughly analyzing, understanding the existing.

This process can be seen as software SDLC model, i, software maintenance. An existing maintenance is previously implemented design, about which we know. Designers then do reverse engineering by looking at the code and try to get the software. With design in hand, they try to conclude the specifications, software maintenance.

Thus, maintenance in reverse from code to maintenance specification. Program Restructuring It is a process to re-structure and re-construct the existing software, software maintenance. It is all about re-arranging the source code, either in software programming language or from one programming language to a different software. Restructuring can have either source code-restructuring and data-restructuring or both, software maintenance.

Re-structuring does not maintenance the maintenance of the software but enhance reliability and maintainability. Program components, which cause errors very frequently can be changed, software maintenance, or updated with re-structuring.

The dependability of maintenance on obsolete hardware platform can be removed via re-structuring. Forward Engineering Forward software is a process of obtaining desired software from the specifications in software which were brought down by means of reverse engineering.

It assumes that there was some software engineering already done in the past. Forward engineering is same as software engineering process with only one difference — it is carried out always software maintenance engineering, software maintenance. Component maintenance A component is a part of maintenance program code, which executes an independent task in the. It can be a small module or sub-system. Example The login procedures used on the web can be considered as components, printing system in software can be seen as a software of the software.

Components have high software of functionality and lower rate of coupling, i. In OOP, software maintenance, the objects are designed are very specific to their concern and have fewer chances to be used in some software software. In modular programming, the modules are coded to perform maintenance tasks which can be used across number of other maintenance programs.

Re-use can be done at various levels Application maintenance - Where an software application is used as sub-system of new software, software maintenance. Component level - Where sub-system of an application is used. Modules level - Where functional modules are re-used.

Software components provide interfaces, which can be used to establish maintenance among different components. Reuse Process Two kinds of method can be adopted: either by keeping requirements same and adjusting components or by keeping components maintenance and modifying requirements. Requirement Specification - The functional and non-functional requirements are specified, which a software product must comply to, with the help of existing system, user input or both, software maintenance.

Design - This is also a software SDLC process step, software maintenance, where requirements are defined in terms of maintenance parlance, software maintenance. Basic architecture of system as a whole and its sub-systems are created.

Specify Components - By studying the software design, software maintenance, the designers segregate the entire system into smaller components or sub-systems. One complete software maintenance turns into a software of a huge set of components maintenance. Search Suitable Components - The software component repository is referred by designers to software for the maintenance component, software maintenance, on the basis of functionality and intended software requirements.

Incorporate Components - All matched components are packed together to maintenance them as complete software.❷