Restoration and Degeneration of the Applications
Iosr Journals, Rajesh Venkatesan, Dr. K V G Rao, N Sambasive Rao · Figshare · 2015
This study is to analyze and identify solutions for software degeneration lifecycle. A software runs on multiple platforms (Operating Systems) these days and makes use of their resources which communicate directly with the hardware. It is, at the time of installation, in its most critical and vulnerable state because at that moment, it is dealing the system files which were created or configured with latter. Hence, a software is likely and most probable to degenerate at this stage. So, in a mechanism where the application state can be saved during its update and installation would act as a rescue measure if the software degeneration happens during the same. One crossroad we may come across in the discussion is that the framework that deals with saving the application state shall be embedded along with the application or can it be made a cross platform extension or shall it be a facility in the operating system. Also, from a user point of view, Application Installation, an Upgrade or a Critical Software Patch are always vulnerable. This not only involves unexpected functioning of the software but also affects the utilization of resources in the operating system. This seeks for a restoration framework at the application level. Yes, the operating system for its own self does it today using checkpoints however it is not for the softwares running over it. Restoring applications specifically across platforms is required today for clear software installations and upgrades. I. Experiments and Data analysis: Observation of the software failures leads to discovery of an important fact that the softwares are generally in the high risk of failure during their update/upgrade cycle. For a software, when it is in its useful life as described in the graph below, it undergoes its upgradation many a times and for each single time, there is dramatic increase in its failure rate.