<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mahadevan, Nagabhushan</style></author><author><style face="normal" font="default" size="100%">Dubey, Abhishek</style></author><author><style face="normal" font="default" size="100%">Karsai, Gabor</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Application of Software Health Management Techniques</style></title><secondary-title><style face="normal" font="default" size="100%">To appear in the Proceedings of the 2011 ICSE Workshop on Software Engineering for Adaptive and Self-Managing Systems</style></secondary-title><tertiary-title><style face="normal" font="default" size="100%">SEAMS '11</style></tertiary-title></titles><dates><year><style  face="normal" font="default" size="100%">2011</style></year></dates><urls><related-urls><url><style face="normal" font="default" size="100%">https://archive.isis.vanderbilt.edu/sites/default/files/Paper_7.pdf</style></url></related-urls></urls><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">New York, NY, USA</style></pub-location><abstract><style face="normal" font="default" size="100%">The growing complexity of software used in large-scale, safety critical cyber-physical systems makes it increasingly difficult to expose and hence correct all potential defects. There is a need to augment the existing fault tolerance methodologies with new approaches that address latent software defects exposed at runtime. This paper describes an approach that borrows and adapts traditional `System Health Management' techniques to improve software dependability through simple formal specification of  runtime monitoring, diagnosis,  and mitigation strategies. The two-level approach to health management at the component and system level  is demonstrated on a simulated case study of an Air Data Inertial Reference Unit (ADIRU). An ADIRU was categorized as the primary failure source for the in-flight upset caused in the Malaysian Air flight 124 over Perth, Australia in 2005.</style></abstract></record></records></xml>