Rodin: an open toolset for modelling and reasoning in Event-B

Abstract

Abstract. Event-B is a formal method for system-level modelling and analysis. Key features of Event-B are the use of set theory as a modelling notation, the use of refinement to represent systems at different abstraction levels and the use of mathematical proof to verify consistency between refinement levels. In this article we present the Rodin modelling tool that seamlessly integrates modelling and proving. We outline how the Event-B language was designed to facilitate proof and how the tool has been designed to support changes to models while minimising the impact of changes on existing proofs. We outline the important features of the prover architecture and explain how well-definedness is treated. The tool is extensible and configurable so that it can be adapted more easily to different application domains and development methods.

From Event-B Models to Dafny Code Contracts

“…Modelling in Event-B is facilitated by a platform called Rodin [2]. Rodin is an extensible open source software which is built on top of the Eclipse IDE.…”

“…This paper presents work in progress on a tool-supported development approach by linking two existing verification tools, Rodin [2] and Dafny [4]. The Rodin platform supports the creation and verification of Event-B formal models.…”

High Quality Implementation for Automatic Generation C# Code by Event-B Pattern

“…The Rodin platform is an open and extensible tool for Event-B specification and verification [6,12]. RODIN have various useful plug-ins such as a proof-obligation generator, provers, modelcheckers, UML transformers, etc .…”

“…The introduction of the RODIN [3] platform allows such extensions to be provided by thirdparty developers, and translation of Event-B to the C# programming language has always been intended. We discuss B2C# as an extension to RODEN and describe its use on two examples.…”

“…MIDAS was developed as a demonstration of a generic Event-B model, capturing the generic properties of binary Instruction Set Architectures (ISAs) in order to provide a reusable template. GCC [3] compilers were developed and used to generate binary executable from hand coded test suites.…”