Model-Based Development of the Generic PCA Infusion Pump User Interface Prototype in PVS

Today's automobiles incorporate a great number of functions that are realized by software. An increasing number of safety-critical functions also follow this trend. For the development of such functions, the ISO 26262 demands a number of additional steps to be performed compared to common software engineering activities. We address some of these demands with means to semi-formally express software safety requirements, tools to automatically implement these requirements, and artifacts and traceability information that can be used for safety case documentation. Through a hierarchical classification of safety mechanisms, a semi-formal specification language for requirements, a generation engine and a case study on a production-model automotive system, we demonstrate: first, how expert knowledge of the functional safety domain can be captured, second, how the tedious and error prone task of manually implementing safety mechanisms can be automated, and third, how this serves as a basis for formal safety argumentation.

“…Moreover, we want to investigate the integration of more expressive formalisms and use of interactive theorem provers, as described by Masci et al [14].…”

Section: Resultsmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Automatically Generated Safety Mechanisms from Semi-Formal Software Safety Requirements

Trindade

Bulwahn

Ainhauser

2014

“…Masci et al [13] presented the model-based development of user interface behaviour of an infusion pump in the Prototype Verification System (PVS). The developed model was verified against relevant safety requirements provided by the FDA.…”

Section: Related Workmentioning

confidence: 99%

Stepwise Formal Modelling and Reasoning of Insulin Infusion Pump Requirements

Singh

Wang²,

Lawford

et al. 2015

An insulin infusion pump (IIP) is a critical software-intensive medical device that infuses insulin satisfying patient needs under safety and timing constraints that are appropriate for the treatment of diabetes. This device is used by millions of people around the world. The USA Food and Drug Administration (FDA) has reported several recalls in which IIP failures were responsible for a large number of serious illnesses and deaths. The failures responsible for this harm to people who are dependent on external insulin were caused by the introduction of hardware or software design errors during the system development process. This paper presents an incremental proof-based development of an IIP. We use the Event-B modelling language to formalize the given system requirements. Further, the Rodin proof tools are used to verify the correctness of functional behaviour, internal consistency checking with respect to safety properties, invariants and events.

“…For this study, we replace this naive interface with a more sophisticated one, as presented in [6], which is implemented as PVS executable specifications. This sophisticated user interface has been verified in PVS for basic safety properties (see [6] for details).…”

Section: Gpca Modelmentioning

confidence: 99%

Combining PVSio with Stateflow

Masci

Zhang

Jones

et al. 2014

Self Cite

Abstract. An approach is presented to integrate PVS executable specifications and Stateflow models. It uses web services to enable a seamless exchange of simulation events and data between PVSio and Stateflow. The approach's effectiveness is demonstrated on a medical device prototype. The prototype's user interface is a PVS specification with its software controller implemented in Stateflow. Using the web services approach, a simulation is run over the prototype, during which simulation data produced in PVSio and Stateflow are exchanged properly and smoothly. Such integration allows the wide range of applications developed in Stateflow to be complemented with the rigor of PVS verification.