Process of Software Evolution
The software evolution process is mostly depending upon the main type of software that is maintained and the organization has used the process of development and also involves the skills of the people. Some organizations used the informal process for conversation between developer and user system for changing the request and the other hand many organizations and companies used the formalized process at each stage of the documentation of the evolution. All the organizations and companies to change the proposals that are required for the system driver.
Therefore the evolution process has been including basic functions such as.
- Change Request
- Release Planning
- System Implementation
- Releasing System
During the releasing planning of software evolution process if all the proposal has been changed means new functionality, adaptation and fault repair are occur in the system. In this situation to make a discussion which changes the implementation for the next version of the system to release. This proposal, which is used to iterate with the next releasing the change proposal.
System Implementation or change Implementation:
System Implementation or change Implementation is the iteration of software process development where the structure of a new version of the software is design, implementation, and testing. In the critical software evolution process, there is change implementation of the first stage should modify the system implementation, design, and specification that can be effective to change the system process. So the requirements of the new system should be effective to change the analysis and validation of the proposed system. After the implementation the system should be tested, if any error that can be occurs during the implementation, so the components of the system are redesign and again tested to the system.
After the process of the system implementation then the next step is the impact analysis process. In which the impact analysis process complete details of the necessary information are analyzed and emerge change should not appear in the change analysis process.
In the change request process, the necessary information is required and the impact analysis process analyzed the necessary information and pass to the next step release planning process. The release planning process passes the information to the next step of the change implementation process so any problem in the implementation process retrieves the information to the previous step of release planning. If no problem in the change implementation processes the pass the information to the system release process. All the information are complete the system analysis process retrieves the first step of change request process so the evolution process is done. The change request process sometimes is related to the system release process.
Types of Release Planning:
There is three types of release planning are given below.
- System Enhancements
- Fault Repair
- Platform Adaptation
Reasons for Process Software Evolution:
The urgent changes appear are three reasons…
- If the environments of the operating system have changed the unexpected effect that destroys the normal operating system.
- In the running business system, there is unanticipated change such as the sudden change in the new competitors.
If any fault occurs in the system that has been allowed to repair or redesign the normal operating system and again continue.