Abstract
In safety-critical fields, architectural languages such as AADL (Architecture Analysis and Design Language) have been playing an important role, and the analysis of the languages and systems designed by them is a challenging research topic. At present, a formal method has become one of the main practices in software engineering for strict analysis, and it has been applied on the tools of formalization and analysis. The formal method can be used to find and resolve the problems early by describing the system with precise semantics and validating the system model. This article studies the comprehensive formal specification and verification of AADL with Behavior annex by the formal method. The presentation of this specification and semantics is the aim of this article, and the work is illustrated with an ARINC653 model case study in Isabelle/HOL.
Highlights
In safety-critical domains such as avionics, aerospace, automotive, and defence, a latent software error even can give rise to catastrophic consequences
It describes a system as a hierarchy of software and hardware components and offers a set of predefined component categories as follows: (i) Software components: data, subprogram, subprogram group, read, read group, Process, and their types, implementations, features, connections, properties (ii) Execution platform components: processor, memory, bus, and device (iii) System composites: they represent composite sets of software and execution platform components (iv) Annex subclauses: they allow annotations expressed in a sublanguage to be attached to the component and contain Behavior Annex, Error Annex, Data Annex, etc According to the component categories, AADL software component elements are composed and synchronized to form the whole software system
Our work presents a method of the description of AADL and a methodology of model transformation from a comprehensive subset of AADL to Isabelle/HOL
Summary
In safety-critical domains such as avionics, aerospace, automotive, and defence, a latent software error even can give rise to catastrophic consequences. Such systems have to be carefully designed and analyzed according to some strict standards such as DO-178C [1], which stipulates analysis, testing, and certification activities. AADL is based on a component-centric model, and it defines the system architecture as a set of interconnected components that hierarchically describes the interfaces, the implementations, the properties, and the channels among components It describes a system as a hierarchy of software and hardware components and offers a set of predefined component categories as follows:.
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
