By Topic

Error-free software development for critical systems using the B-Methodology

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

4 Author(s)
Carnot, M. ; Transp. Div., GEC-ALSTHOM, Saint-Ouen, France ; DaSilva, C. ; Dehbonei, B. ; Mejia, F.

A description is given of the process of software development for critical systems using the B-Methodology designed by J.R. Abrial. The author explains the insights of the B formal development process: specification and implementation through refinements where each refinement step is proved using axioms based on the first-order predicate logic and an extension of the Zermelo set theory. They present the techniques and related tools that facilitate the process of realizing and proving programs. Three tools are described: the typechecker, the proof-obligation generator and the prover. Two industrial critical software systems have been carried out using this methodology: the subway speed control under final on-site tests (~3000 lines of Modula-2) and the KVS French train speed control that is in the integration test phase (~15000 lines of Ada)

Published in:

Software Reliability Engineering, 1992. Proceedings., Third International Symposium on

Date of Conference:

7-10 Oct 1992