A Conformance Review Strategy for Regulating Safety-Critical Software.
dc.contributor.advisor | Dr. S. Purushothaman Iyer, Committee Chair | en_US |
dc.contributor.advisor | Dr. Laurie Williams, Committee Member | en_US |
dc.contributor.advisor | Dr. Matthias Stallmann, Committee Member | en_US |
dc.contributor.advisor | Dr. Alexander Dean, Committee Member | en_US |
dc.contributor.author | Jetley, Raoul Praful | en_US |
dc.date.accessioned | 2010-04-02T19:09:19Z | |
dc.date.available | 2010-04-02T19:09:19Z | |
dc.date.issued | 2006-09-24 | en_US |
dc.degree.discipline | Computer Science | en_US |
dc.degree.level | dissertation | en_US |
dc.degree.name | PhD | en_US |
dc.description.abstract | Safety is an important concern for software used in life-critical systems such as air transport, nuclear power and medical devices. The critical nature of these systems necessitates that the software used therein be reliable and free of errors. It becomes imperative, therefore, to have a stringent review process in place to ascertain the correctness of the software and to ensure that it meets all requirements and standards. Regulatory agencies encourage the use of formal methods based techniques in the development of safety critical software. However, most manufacturers are reluctant to use these techniques, citing them as too complex and time consuming. As a result, (potentially life-threatening) errors are often not discovered until the software is already on the market. When such an error is eventually discovered, it becomes essential to trace the failure to its exact source in the implementation and to assure that the error correction restores the overall safety and effectiveness of the device. In this dissertation, we present how efficient premarket and postmarket reviews of designs and implementations can be carried out using formal methods based techniques, to enable the process of reviewing software in safety-critical devices. To facilitate premarket conformance reviews, we introduce the notion of usage models -- standardized formal models that serve as design templates. We present an approach to conformance checking of safety-critical software through formal verification and automated test case sequences derived from these standardized models. To provide for efficient postmarket reviews, we establish a methodology based on integrating program slicing with model abstraction to trace software failures to their root cause. We formalize this methodology by presenting an iterative algorithm for abstraction-driven slicing and realize this algorithm through the implementation of the CAdS -- a forensic analysis tool for C programs. We provide case studies involving typical medical device software to illustrate the various concepts involved and present results from these studies to gauge the effectiveness of our proposed approach. | en_US |
dc.identifier.other | etd-06142006-110213 | en_US |
dc.identifier.uri | http://www.lib.ncsu.edu/resolver/1840.16/5195 | |
dc.rights | I hereby certify that, if appropriate, I have obtained and attached hereto a written permission statement from the owner(s) of each third party copyrighted matter to be included in my thesis, dissertation, or project report, allowing distribution as specified below. I certify that the version I submitted is the same as that approved by my advisory committee. I hereby grant to NC State University or its agents the non-exclusive license to archive and make accessible, under the conditions specified below, my thesis, dissertation, or project report in whole or in part in all forms of media, now or hereafter known. I retain all other ownership rights to the copyright of the thesis, dissertation or project report. I also retain the right to use in future works (such as articles or books) all or part of this thesis, dissertation, or project report. | en_US |
dc.subject | slicing | en_US |
dc.subject | abstraction | en_US |
dc.subject | usage model | en_US |
dc.subject | formal methods | en_US |
dc.subject | regulatory agencies | en_US |
dc.title | A Conformance Review Strategy for Regulating Safety-Critical Software. | en_US |
Files
Original bundle
1 - 1 of 1