Integrating Formal Verification and Assurance: An Inspection Rover Case Study

Hamza Bourbouh, Marie Farrell, Anastasia Mavridou, Irfan Sljivo, Guillaume Brat, Louise A. Dennis, Michael Fisher

Research output: Chapter in Book/Report/Conference proceedingChapterpeer-review

Abstract

The complexity and flexibility of autonomous robotic systems necessitates a range of distinct verification tools. This presents new challenges not only for design verification but also for assurance approaches. Combining the distinct formal verification tools, while maintaining sufficient formal coherence to provide compelling assurance evidence is difficult, often being abandoned for less formal approaches. In this paper we demonstrate, through a case study, how a variety of distinct formal techniques can be brought together in order to develop a justifiable assurance case. We use the AdvoCATE assurance case tool to guide our analyses and to integrate the artifacts from the formal methods that we use, namely: fret, cocosim and Event-B. While we present our methodology as applied to a specific Inspection Rover case study, we believe that this combination provides benefits in maintaining coherent formal links across development and assurance processes for a wide range of autonomous robotic systems.
Original languageEnglish
Title of host publicationNASA Formal Methods
Subtitle of host publication13th International Symposium, NFM 2021, Virtual Event, May 24–28, 2021, Proceedings
EditorsAaron Dutle, Mariano M. Moscato, Laura Titolo, César A. Muñoz, Ivan Perez
Place of PublicationCham, Switzerland
PublisherSpringer Nature
Pages53-71
Number of pages19
ISBN (Electronic)9783030763848
ISBN (Print)9783030763831
DOIs
Publication statusPublished - 19 May 2021

Publication series

NameLecture Notes in Computer Science
PublisherSpringer
Volume12673
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349

Fingerprint

Dive into the research topics of 'Integrating Formal Verification and Assurance: An Inspection Rover Case Study'. Together they form a unique fingerprint.

Cite this