Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There are two different approaches to formal methods in the industry.</p> <p>One approach is to change the development process completely. The Z notation and the B method that were mentioned are in this first category. B was applied to the development of the driverless subway line 14 in Paris (if you get a chance, climb in the front wagon. It's not often that you get a chance to see the rails in front of you).</p> <p>Another, more incremental, approach is to preserve the existing development and verification processes and to replace only one of the verification tasks at a time by a new method. This is very attractive but it means developing static analysis tools for exiting, used languages that are often not easy to analyse (because they were not designed to be). If you go to (for instance)</p> <p><a href="http://dblp.uni-trier.de/db/indices/a-tree/d/Delmas:David.html" rel="nofollow noreferrer">http://dblp.uni-trier.de/db/indices/a-tree/d/Delmas:David.html</a></p> <p>(sorry, only one hyperlink allowed for new users :( )</p> <p>you will find instances of practical applications of formal methods to the verification of C programs (with static analyzers Astrée, Caveat, Fluctuat, Frama-C) and binary code (with tools from AbsInt GmbH).</p> <p>By the way, since you mentioned Hoare Logic, in the above list of tools, only Caveat is based on Hoare logic (and Frama-C has a Hoare logic plug-in). The others rely on abstract interpretation, a different technique with a more automatic approach.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload