Formal Verification of AADL Specifications in the Topcased Environment

Abstract

We describe a formal verification toolchain for AADL, the SAE Architecture Analysis and Design Language, enriched with its behavioral annex. Our approach is based on tools that are integrated in the Topcased environment. We give a high-level view of the tools involved and illustrate the successive transformations that take place during the verification process.

An ocarina extension for AADL formal semantics generation

“…Then, the LNT AST is scanned by the LNT code printer in order to produce code source files 4 https://github.com/OpenAADL/ocarina (*.lnt). To obtain a modular specification, we generate a set of LNT modules which corresponds to the construction of a set of LNT LTSs.…”

“…In addition, Ocarina can be easily integrated as a backend for other AADL editors (already used through OSATE and AADL Inspector tools), which increases the visibility of our work. AADL Formal approaches are often based on model transformation into different languages such as Lustre [13], TLA+ [22], Signal [5], ACSR [24], TASM [25], Fiacre [4], Real-time Maude [20] and BIP [8]. As examples: many work [5,26] are around the Polychrony platform and Signal language for synchronous verification of AADL models where behavior is specified by BA or Simulink.…”

“…As examples: many work [5,26] are around the Polychrony platform and Signal language for synchronous verification of AADL models where behavior is specified by BA or Simulink. The transformations are implemented within OSATE and the analyses are performed by Polychrony and SynDEx tools; authors in [25] transform a synchronous AADL subset (periodic threads, data port connections, modes and BA) to the TASM language, in order to verify behavioral properties (deadlock and reachability) with TASM tool suite and UPPAAL; the transformation of AADL model into the Fiacre language is addressed in the TOPCASED environment [4]. This work supports periodic/sporadic thread and event/data port connections, but it is restricted to the non-preemptive scheduling.…”

“…Many projects and tool-chains are dedicated to AADL processing, that often adopt model transformation techniques to allow formal analyses. Several AADL formal semantics are defined using different formalisms such as Petri nets [21,23], timed automata [12,14] and different process algebras [4,5,8,20,25]. These approaches are implemented within platforms such as OSATE and TOPCASED aiming the convenient reuse of existing tools like UPPAAL, Tina and Polychrony.…”

Formal Semantics and Analysis of Behavioral AADL Models in Real-Time Maude

“…Work in class (iii) includes [3,4,17] and our own work. The main difference between [3,4] and our work is that we give a formal executable semantics to an AADL model with a behavior annex specification of its thread behavior, associating to it a real-time rewrite theory.…”