Verification of User Interface Software: The Example of Use-Related Safety Requirements and Programmable Medical Devices
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...
Gespeichert in:
Veröffentlicht in: | IEEE transactions on human-machine systems 2017-12, Vol.47 (6), p.834-846 |
---|---|
Hauptverfasser: | , , , |
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | 846 |
---|---|
container_issue | 6 |
container_start_page | 834 |
container_title | IEEE transactions on human-machine systems |
container_volume | 47 |
creator | Harrison, Michael D. Masci, Paolo Creissac Campos, Jose Curzon, Paul |
description | 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. |
doi_str_mv | 10.1109/THMS.2017.2717910 |
format | Article |
fullrecord | <record><control><sourceid>crossref_ieee_</sourceid><recordid>TN_cdi_crossref_primary_10_1109_THMS_2017_2717910</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>7993052</ieee_id><sourcerecordid>10_1109_THMS_2017_2717910</sourcerecordid><originalsourceid>FETCH-LOGICAL-c333t-7f023543407a4b125f8f9be4bcaff1979167d3c51f79d29c3c1655b746276ff43</originalsourceid><addsrcrecordid>eNo9kMtOwzAQRS0EElXpByA2_oEUP-I4ZodKoZVagfpgGznODAQ1SbEDtH9PqhZmM7O4Z0ZzCLnmbMg5M7eryXw5FIzrodBcG87OSE_wJI2EZOr8bxaGX5JBCB-sq1QopdIe2b2CL7F0ti2bmjZI1wE8ndYteLQO6LLB9sd6uKOrd6Djna22GzjlogVsbAsFXVqEdk8X8PlVeqigbgO1dUFffPPmbVXZvGPmUHRnNvQBvksH4YpcoN0EGJx6n6wfx6vRJJo9P01H97PISSnbSCMTUsUyZtrGORcKUzQ5xLmziNx0zya6kE5x1KYQxknHE6VyHSdCJ4ix7BN-3Ot8E4IHzLa-rKzfZ5xlB3vZwV52sJed7HXMzZEpAeA_r43pdAr5C9RObDM</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype></control><display><type>article</type><title>Verification of User Interface Software: The Example of Use-Related Safety Requirements and Programmable Medical Devices</title><source>IEEE Electronic Library (IEL)</source><creator>Harrison, Michael D. ; Masci, Paolo ; Creissac Campos, Jose ; Curzon, Paul</creator><creatorcontrib>Harrison, Michael D. ; Masci, Paolo ; Creissac Campos, Jose ; Curzon, Paul</creatorcontrib><description>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.</description><identifier>ISSN: 2168-2291</identifier><identifier>EISSN: 2168-2305</identifier><identifier>DOI: 10.1109/THMS.2017.2717910</identifier><identifier>CODEN: ITHSA6</identifier><language>eng</language><publisher>IEEE</publisher><subject>Analytical models ; Formal specifications ; Formal verification ; human error ; Mathematical model ; Medical devices ; modal action logic (MAL) ; Model checking ; Performance evaluation ; PVS ; theorem proving ; User interfaces</subject><ispartof>IEEE transactions on human-machine systems, 2017-12, Vol.47 (6), p.834-846</ispartof><lds50>peer_reviewed</lds50><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c333t-7f023543407a4b125f8f9be4bcaff1979167d3c51f79d29c3c1655b746276ff43</citedby><cites>FETCH-LOGICAL-c333t-7f023543407a4b125f8f9be4bcaff1979167d3c51f79d29c3c1655b746276ff43</cites><orcidid>0000-0002-5567-9650</orcidid></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/7993052$$EHTML$$P50$$Gieee$$Hfree_for_read</linktohtml><link.rule.ids>314,777,781,793,27905,27906,54739</link.rule.ids></links><search><creatorcontrib>Harrison, Michael D.</creatorcontrib><creatorcontrib>Masci, Paolo</creatorcontrib><creatorcontrib>Creissac Campos, Jose</creatorcontrib><creatorcontrib>Curzon, Paul</creatorcontrib><title>Verification of User Interface Software: The Example of Use-Related Safety Requirements and Programmable Medical Devices</title><title>IEEE transactions on human-machine systems</title><addtitle>THMS</addtitle><description>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.</description><subject>Analytical models</subject><subject>Formal specifications</subject><subject>Formal verification</subject><subject>human error</subject><subject>Mathematical model</subject><subject>Medical devices</subject><subject>modal action logic (MAL)</subject><subject>Model checking</subject><subject>Performance evaluation</subject><subject>PVS</subject><subject>theorem proving</subject><subject>User interfaces</subject><issn>2168-2291</issn><issn>2168-2305</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2017</creationdate><recordtype>article</recordtype><sourceid>ESBDL</sourceid><sourceid>RIE</sourceid><recordid>eNo9kMtOwzAQRS0EElXpByA2_oEUP-I4ZodKoZVagfpgGznODAQ1SbEDtH9PqhZmM7O4Z0ZzCLnmbMg5M7eryXw5FIzrodBcG87OSE_wJI2EZOr8bxaGX5JBCB-sq1QopdIe2b2CL7F0ti2bmjZI1wE8ndYteLQO6LLB9sd6uKOrd6Djna22GzjlogVsbAsFXVqEdk8X8PlVeqigbgO1dUFffPPmbVXZvGPmUHRnNvQBvksH4YpcoN0EGJx6n6wfx6vRJJo9P01H97PISSnbSCMTUsUyZtrGORcKUzQ5xLmziNx0zya6kE5x1KYQxknHE6VyHSdCJ4ix7BN-3Ot8E4IHzLa-rKzfZ5xlB3vZwV52sJed7HXMzZEpAeA_r43pdAr5C9RObDM</recordid><startdate>201712</startdate><enddate>201712</enddate><creator>Harrison, Michael D.</creator><creator>Masci, Paolo</creator><creator>Creissac Campos, Jose</creator><creator>Curzon, Paul</creator><general>IEEE</general><scope>97E</scope><scope>ESBDL</scope><scope>RIA</scope><scope>RIE</scope><scope>AAYXX</scope><scope>CITATION</scope><orcidid>https://orcid.org/0000-0002-5567-9650</orcidid></search><sort><creationdate>201712</creationdate><title>Verification of User Interface Software: The Example of Use-Related Safety Requirements and Programmable Medical Devices</title><author>Harrison, Michael D. ; Masci, Paolo ; Creissac Campos, Jose ; Curzon, Paul</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c333t-7f023543407a4b125f8f9be4bcaff1979167d3c51f79d29c3c1655b746276ff43</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2017</creationdate><topic>Analytical models</topic><topic>Formal specifications</topic><topic>Formal verification</topic><topic>human error</topic><topic>Mathematical model</topic><topic>Medical devices</topic><topic>modal action logic (MAL)</topic><topic>Model checking</topic><topic>Performance evaluation</topic><topic>PVS</topic><topic>theorem proving</topic><topic>User interfaces</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Harrison, Michael D.</creatorcontrib><creatorcontrib>Masci, Paolo</creatorcontrib><creatorcontrib>Creissac Campos, Jose</creatorcontrib><creatorcontrib>Curzon, Paul</creatorcontrib><collection>IEEE All-Society Periodicals Package (ASPP) 2005-present</collection><collection>IEEE Open Access Journals</collection><collection>IEEE All-Society Periodicals Package (ASPP) 1998-Present</collection><collection>IEEE Electronic Library (IEL)</collection><collection>CrossRef</collection><jtitle>IEEE transactions on human-machine systems</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Harrison, Michael D.</au><au>Masci, Paolo</au><au>Creissac Campos, Jose</au><au>Curzon, Paul</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Verification of User Interface Software: The Example of Use-Related Safety Requirements and Programmable Medical Devices</atitle><jtitle>IEEE transactions on human-machine systems</jtitle><stitle>THMS</stitle><date>2017-12</date><risdate>2017</risdate><volume>47</volume><issue>6</issue><spage>834</spage><epage>846</epage><pages>834-846</pages><issn>2168-2291</issn><eissn>2168-2305</eissn><coden>ITHSA6</coden><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.</abstract><pub>IEEE</pub><doi>10.1109/THMS.2017.2717910</doi><tpages>13</tpages><orcidid>https://orcid.org/0000-0002-5567-9650</orcidid><oa>free_for_read</oa></addata></record> |
fulltext | fulltext |
identifier | ISSN: 2168-2291 |
ispartof | IEEE transactions on human-machine systems, 2017-12, Vol.47 (6), p.834-846 |
issn | 2168-2291 2168-2305 |
language | eng |
recordid | cdi_crossref_primary_10_1109_THMS_2017_2717910 |
source | IEEE Electronic Library (IEL) |
subjects | Analytical models Formal specifications Formal verification human error Mathematical model Medical devices modal action logic (MAL) Model checking Performance evaluation PVS theorem proving User interfaces |
title | Verification of User Interface Software: The Example of Use-Related Safety Requirements and Programmable Medical Devices |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-20T08%3A21%3A02IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-crossref_ieee_&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Verification%20of%20User%20Interface%20Software:%20The%20Example%20of%20Use-Related%20Safety%20Requirements%20and%20Programmable%20Medical%20Devices&rft.jtitle=IEEE%20transactions%20on%20human-machine%20systems&rft.au=Harrison,%20Michael%20D.&rft.date=2017-12&rft.volume=47&rft.issue=6&rft.spage=834&rft.epage=846&rft.pages=834-846&rft.issn=2168-2291&rft.eissn=2168-2305&rft.coden=ITHSA6&rft_id=info:doi/10.1109/THMS.2017.2717910&rft_dat=%3Ccrossref_ieee_%3E10_1109_THMS_2017_2717910%3C/crossref_ieee_%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rft_ieee_id=7993052&rfr_iscdi=true |