Phases of Software Maintenance Life Cycle

1. Problem Identification Phase

In this phase, tech teams identify the software modification requests and assign identification numbers to each.

Then, developers assess each modification request to determine the type of maintenance activity (adaptive, corrective, preventive, or perfective). After the classification, they prioritize each modification request to determine the order in which it will be processed.

The problem analysis phase determines the feasibility and scope of each validated modification request. This is the phase wherein developers plan the possible changes to be made in the software.  

2. Problem Analysis Phase

Here, the input attribute comprises validated modification requests, an initial estimate of resources, repository information, and project documentation. 

At this stage, developers create new modules that need replacement or modification based on requirements specified in earlier stages. They also create test cases that address safety and security concerns to validate and verify the system.

3. Design phase

The implementation phase is where the developers make modifications to the code, add specifications, integrate new features, and modify the whole software. 

4. Implementation Phase

Here, the input attribute comprises the design phase output, source code, modified system, and project documentation.

In this phase, the development/testing team performs integration testing between new modules and the system. This is done to ensure no new faults are introduced in the software after modifying it during the maintenance process.

5. System Test Phase

Finally, following regressive testing procedures, developers test the system thoroughly. They then create test review reports and updated software documentation.

For More Details, Contact Us Now:

Visit Website