ABSTRACT
There has been a significant increase in the complexity of software over the last decades, notably regarding safety requirement levels, overall coherence and the interaction between components. A profusion of methods based upon model verification or static analysis currently allows improvement in the fiability of critical software. Although it has shown some limitations, the B method stands out from others in many aspects. Its main force is undoubtfully the use of a programming language which ensures that each step is verified through mathematical evidence. Altough rigour and precision are assisted on in the writing process, the integration of quality as early on as in the designing stage remains a significant asset.
Read this article from a comprehensive knowledge base, updated and supplemented with articles reviewed by scientific committees.
Read the article
INTRODUCTION
It is not the intention of this article that the reader should know everything there is to know about the B method; that would be impossible and pretentious. The B-BOOK – Assigning Programs to Meanings by Jean-Raymond ABRIAL, the inventor of the B-method, which is the basis of the B-language, already runs to over 750 pages and is based on a wealth of mathematical and logical knowledge. The aim here is simply to shed some light on the main concepts behind this method, so that we can better assess it. The mathematical aspects, though essential, will not be over-developed. The discussion will always remain fairly general, sometimes deliberately simplifying to remain understandable.
You do not have access to this resource.
Exclusive to subscribers. 97% yet to be discovered!
Already subscribed?
Log in!
Ongoing reading
B Method for the specification and fabrication of software and proven critical systems