Trace queries for safety requirements in high assurance systems

  • Authors:
  • Jane Cleland-Huang;Mats Heimdahl;Jane Huffman Hayes;Robyn Lutz;Patrick Maeder

  • Affiliations:
  • DePaul University, Chicago, IL;University of Minneapolis, Minneapolis, MN;Kentucky State University, Lexington, KY;Iowa State University, Ames, IA, USA and Jet Propulsion Laboratory, Caltech;Johannes Kepler University, Linz, Austria

  • Venue:
  • REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
  • Year:
  • 2012

Quantified Score

Hi-index 0.00

Visualization

Abstract

[Context and motivation] Safety critical software systems pervade almost every facet of our lives. We rely on them for safe air and automative travel, healthcare diagnosis and treatment, power generation and distribution, factory robotics, and advanced assistance systems for special-needs consumers. [Question/Problem] Delivering demonstrably safe systems is difficult, so certification and regulatory agencies routinely require full life-cycle traceability to assist in evaluating them. In practice, however, the traceability links provided by software producers are often incomplete, inaccurate, and ineffective for demonstrating software safety. Also, there has been insufficient integration of formal method artifacts into such traceability. [Principal ideas/results] To address these weaknesses we propose a family of reusable traceability queries that serve as a blueprint for traceability in safety critical systems. In particular we present queries that consider formal artifacts, designed to help demonstrate that: 1) identified hazards are addressed in the safety-related requirements, and 2) the safety-related requirements are realized in the implemented system. We model these traceability queries using the Visual Trace Modeling Language, which has been shown to be more intuitive than the defacto SQL standard. [Contribution] Practitioners building safety critical systems can use these trace queries to make their traceability efforts more complete, accurate and effective. This, in turn, can assist in building safer software systems and in demonstrating their adequate handling of hazards.