E-Type software evolution
There are following E-Type software evolution are given below.
Similarly to the E-Type software evolution, the real-world requirements must change in the program and the environment becomes less progressively used.
Similarly to the E-Type software evolution, the tending structure of the software becomes more complex. Then the extra resource is used to increase the tends complexity and the unless work is done to maintain
Conservation of familiarity:
The familiarity with the software evolution about how it was developing, why it was developing in that specific manner. The lifetime of over the system the approximately incremental change in each release.
In this evolution system, the functionality of the system is continually increasing and maintain the user specification. In the continued growth the measure of implementing the changes grows become to the lifestyle changes of the business.
The lifecycle of the programs, its rate of development is approximately constant.
Reducing or Declining quality:
In this evolution, the quality of the system is declining unless and operational environment is changing.
In which the process of E-Type software evolution the distributing of self-regulation is the product and process are a measure to normal.
In which the feedback process the multi-loop are constitute working and the multi-level feedback system must be treated such as successful to improve.