Using the B formal approach for incremental specification design of interactive systems

Abstract

This paper introduces a new technique for the veritication of interactive systems.It first presents the use of a model oriented formal method for specifying interactive systems, i.e. the B method. Then, it suggests formally based solutions which allow solving dimculties that are inherent to interactive systems specification, like reach ability, observability or reliability. Our claim is that this model-oriented technique that uses proof obligations can be used together with model checking techniques, where automatic proofs of properties can be performed.

Formal Verification and Validation of Interactive Systems Specifications

“…In past workshops and conferences, we presented our approach through papers dealing with formal specifications of HCI software (Aït-Ameur et al 1998a), formal verification of HCI software (Aït-Ameur et al 1998), test based validation of existing applications (Jambon et al 1999). This paper addresses another topic not tackled yet by our approach: design and formal validation of formal specifications with respect to informal requirements.…”

“…This work completes the whole development process of a HCI software. Indeed, our approach uses the B formal technique for representing, verifying and refining specifications (Aït-Ameur et al 1998a, Aït-Ameur et al 1998, Jambon et al 1999, test based validation of existing applications (Jambon et al 1999), secure code generation (Jambon 2002) and integration of formal approaches (Girard et al 2003).…”

“…So, the software dependability of these 62 Y. Aït-Ameur, B. Breholée, P. Girard, L. Guittet & F. Jambon safety-critical interactive systems rely as well on safety as on usability properties. Our work focuses on the use of formal techniques in order to increase the quality of HCI software and of all the processes resulting from the development, verification, design and validation activities.In past workshops and conferences, we presented our approach through papers dealing with formal specifications of HCI software (Aït-Ameur et al 1998a), formal verification of HCI software (Aït-Ameur et al 1998), test based validation of existing applications (Jambon et al 1999). This paper addresses another topic not tackled yet by our approach: design and formal validation of formal specifications with respect to informal requirements.…”

“…This work completes the whole development process of a HCI software. Indeed, our approach uses the B formal technique for representing, verifying and refining specifications (Aït-Ameur et al 1998a, Aït-Ameur et al 1998, Jambon et al 1999, test based validation of existing applications (Jambon et al 1999), secure code generation (Jambon 2002) and integration of formal approaches (Girard et al 2003).This paper starts from the translation of the requirements in the UAN notation (Hix and Hartson 1993) and shows how B specifications can be derived from. Then, the EXPRESS formal data modeling language (EXPRESS 1994) is put into practice for the validation of the derived B specifications.…”

“…B supports formal specifications, refinement from specifications to code and property verification through the proof of the generated proof obligations. Specifications are derived from the informal UAN notation and are validated using the EXPRESS data modeling language.Formal specifications, property verification and refinement from specification to code have been have been presented in (Aït-Ameur et al 1998a,Aït-Ameur et al 1998, Jambon et al 1999 respectively. This paper presents the last point: deriving specifications from semi-formal notations and their validation in EXPRESS.…”