Abstract

One part of demonstrating that a device is acceptably safe, often required by regulatory standards, is to show that it satisfies a set of requirements known to mitigate hazards. This paper is concerned with how to demonstrate that a user interface software design is compliant with use-related safety requirements. A methodology is presented based on the use of formal methods technologies to provide guidance to developers about addressing three key verification challenges: 1) how to validate a model, and show that it is a faithful representation of the device; 2) how to formalize requirements given in natural language, and demonstrate the benefits of the formalization process; and 3) how to prove requirements of a model using readily available formal verification tools. A model of a commercial device is used throughout the paper to demonstrate the methodology. A representative set of requirements are considered. They are based onUS Food and Drug Administration (FDA) draft documentation for programmable medical devices, and on best practice in user interface design illustrated in relevant international standards. The methodology aims to demonstrate how to achieve the FDA's agenda of using formal methods to support the approval process for medical devices.

Highlights

  • D ESIGN anomalies in user interface software are an important concern in safety-critical application domains, including aviation, power generation, and medicine

  • Three types of formal techniques are used in this work to analyze the user interface software of an interactive system: model checking, theorem proving, and simulation

  • Formal verification of usability aspects have seen slow take-up in industry. We address this challenge, providing software developers with a demonstration of how formal techniques can be used to gain high assurance that user interface software design is compliant with given requirements, while considering how software engineers, domain experts, and human factors experts can collaborate to ensure that the manner in which the requirements are satisfied will mitigate use-error

Read more

Summary

INTRODUCTION

D ESIGN anomalies in user interface software are an important concern in safety-critical application domains, including aviation, power generation, and medicine. Three types of formal techniques are used in this work to analyze the user interface software of an interactive system: model checking, theorem proving, and simulation. 1) Model checking is used to validate models and analyze the interface mode behavior of the device against relevant safety requirements Formal verification of usability aspects have seen slow take-up in industry We address this challenge, providing software developers with a demonstration of how formal techniques can be used to gain high assurance that user interface software design is compliant with given requirements, while considering how software engineers, domain experts, and human factors experts can collaborate to ensure that the manner in which the requirements are satisfied will mitigate use-error

Contribution
Organization
RELATED WORK
MODELING AND ANALYSIS APPROACH
MEDICAL EXAMPLE
DEVELOPING A MODEL OF THE DEVICE
Initial Model of the Device
Detailed Model of the Device
VALIDATING THE MODEL AGAINST THE REAL DEVICE
FORMALIZING AND PROVING REQUIREMENTS
Formalization Process
FDA Requirements
Requirements From Property Templates
Feedback Template
Consistency Template
Reversibility Template
VIII. DISCUSSION AND CONCLUSIONS
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.