Approach/methodology/system Feature | MS Windows (System Restore. (Ed Bott, 2009) | ASURE (Stelios Sidiroglou, 2009) | Exception Handlers for Healing (Herve Chang, 2013) | The SFDR Approach |
Recover error resulting from deleting software component | Yes | No | No | Yes |
Recover and Replaced component that has same functionality | No | No | Yes | Yes |
Fault recovery | No | Yes | No | Yes |
Generate reports of the default diagnosis and the recovery process | Yes | No | No | Yes |
Store the affected component for future analysis | No | No | No | Yes |
Approach of repairing | System Restore | Dynamically patches the running production application to self-checkpoint at the rescue point | Heal fault s activated by exceptions raised in the OTS components actually deployed in the system | Automatically including Comparing, analyzing, diagnosing and recovery to return the software to its original status of the manufacturer |
State of the recovery | To a specified restore point | To a specified rescue point. | Original state of the manufacturer | To the manufacturer state either the original or with updates |
Knowing the structure of the software and its component | Yes | Yes | Ye s | Yes |
Recovery time | After release | After release | After release | After release |
Building time | During the development of the software | During the development of the software | During the development of the software | During the development of the software |