Towards an AADL-Based Definition of App Architecture for Medical Application Platforms

Procter, Sam; Hatcliff, John; Robby, .

doi:10.1007/978-3-319-63194-3_3

Cited by 1 publication

(1 citation statement)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Last, Proctor et al proposed an architecture description language extension for AADL for connected medical devices. This can reason about medical apps in general [14]; however, it does not directly provide support for our use case, dependability cases for families of safety-critical devices, such as surgical robots.…”

Section: Introductionmentioning

confidence: 99%

Modeling and testing a family of surgical robots: an experience report

Mansoor

Saddler

Silva

et al. 2018

Proceedings of the 2018 26th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of

View full text Add to dashboard Cite

Safety-critical applications often use dependability cases to validate that specified properties are invariant, or to demonstrate a counter example showing how that property might be violated. However, most dependability cases are written with a single product in mind. At the same time, software product lines (families of related software products) have been studied with the goal of modeling variability and commonality, and building family based techniques for both analysis and testing. However, there has been little work on building an end to end dependability case for a software product line (where a property is modeled, a counter example is found and then validated as a true positive via testing), and none that we know of in an emerging safety-critical domain, that of robotic surgery. In this paper, we study a family of surgical robots, that combine hardware and software, and are highly configurable, representing over 1300 unique robots. At the same time, they are considered safety-critical and should have associated dependability cases. We perform a case study to understand how we can bring together lightweight formal analysis, feature modeling, and testing to provide an end to end pipeline to find potential violations of important safety properties. In the process, we learned that there are some interesting and open challenges for the research community, which if solved will lead towards more dependable safety-critical cyber-physical systems. CCS CONCEPTS • Software and its engineering → Software defect analysis; Formal software verification; Model-driven software engineering;

show abstract

Section: Introductionmentioning

confidence: 99%