Cooperation of Formal Methods in an Engineering Based Software Development Process

Communications in Computer and Information Science

Aït‐Ameur

Méry

et al. 2020

This paper reports our experience for developing Human-Machine Interface (HMI) complying with ARINC 661 specification standard for interactive cockpits applications using formal methods. This development relies on the FLUID modelling language, we have proposed and formally defined in the FORMEDICIS 1 project. FLUID contains essential features required for specifying HMI. To develop the MultiPurpose Interactive Applications (MPIA) use case, we follow the following steps: an abstract model of MPIA is written using the FLUID language; this MPIA FLUID model is used to produce an Event-B model for checking the functional behaviour, user interactions, safety properties, and interaction related to domain properties; the Event-B model is also used to check temporal properties and possible scenario using the ProB model checker; and finally, the MPIA FLUID model is translated to Interactive Cooperative Objects (ICO) using the PetShop CASE tool to validate the dynamic behaviour, visual properties and task analysis. These steps rely on different tools to check internal consistency along with possible HMI properties. Finally, the formal development of the MPIA case study using FLUID and its embedding into other formal techniques, demonstrates reliability, scalability and feasibility of our approach defined in the FORMEDICIS project.

Section: Related Workmentioning

confidence: 99%

Formal Development of Multi-Purpose Interactive Application (MPIA) for ARINC 661

Communications in Computer and Information Science

Aït‐Ameur

Méry

et al. 2020

“…The proposed approach targets the important problems of HMI related to reachability, observability and reliability. A global development approach for developing a software for human-computer interaction is proposed in [6,7] that can be used from the abstract model to the code generation. Silva et al [36] propose an approach to generate user interface software, particularly in Java, from a declarative description in the Teallach MB-UIDE.…”

Section: Discussionmentioning

confidence: 99%

Refinement Based Formal Development of Human-Machine Interface

Geniet

Software Technologies: Applications and Foundations

2018

Human factors have been considered as the most common causes of accidents, particularly for interacting with complex critical systems related to avionics, railway, nuclear and medical domains. Mostly, a human-machine interface (HMI) is developed independently and the correctness of possible interactions is heavily dependent on testing, which cannot guarantee the absence of runtime errors. The use of formal methods in HMI development may assure such guarantee. This paper presents a methodology for developing an HMI using a correct by construction approach, which allows us to introduce the HMI components, functional behaviour and the required safety properties progressively. The proposed methodology, generic refinement strategy, supports a development of the model-view-controller (MVC) architecture. The whole approach is formalized using Event-B and relies on the Rodin tools to check the internal consistency with respect to the given safety properties, invariants and events. Finally, an industrial case study is used to illustrate the effectiveness of our proposed approach for developing an HMI.

“…An incremental development of an interactive system using B methods presented in Aït‐Ameur et al 5,77 to describe interaction requirements and the properties of reachability, observability, and reliability. In Aït‐Ameur et al, 78,79 a development life cycle was proposed to produce source code from a formalized model of an interactive system for implementation purpose. For developing a multi‐model interactive system supporting CARE properties, the Event‐B modeling language was used for specifying system requirements and the required safety properties 80 .…”

Section: Related Workmentioning

confidence: 99%

F3FLUID: A formal framework for developing safety‐critical interactive systems in FLUID

J Software Evolu Process

Aït‐Ameur

Mendil

et al. 2022

This paper proposes a unified formal framework, Formal Framework For FLUID (F3FLUID), for the development of safety-critical interactive systems. This framework is based on the Formal Language of User Interface Design (FLUID) pivot modeling language defined in the FORMEDICIS project, which enables high-level system requirements for interactive systems to be specified in the FLUID language. This modeling language is specifically designed for handling concepts of safety-critical interactive systems, including domain knowledge. A FLUID model is used as a source model for the generation of several target models in different modeling languages to support the formal verification methods, such as theorem proving and model checking. In this paper, we use the Event-B modeling language for checking functional behaviors, user interactions, safety properties, and domain properties. A FLUID model is transformed into an Event-B model, and then, the Rodin tool is used to check the internal consistency with respect to the given safety properties. We illustrate the operational semantics of the FLUID language, and the transformation strategy of FLUID models into Event-B models, including the tool development. We use the ProB model checker to analyze the temporal properties and to animate the formalized specification. In addition, an interactive cooperative objects (ICOs) model is derived from the Event-B model for animation, visualization and validation of dynamic behaviors, visual properties, and task analysis. Finally, an industrial case study, complying with the ARINC 661 standard, Multi-Purpose Interactive Applications (MPIA), is used to illustrate the effectiveness of our F3FLUID framework for the development of safety-critical interactive systems.