Tutorial: Difference between revisions

No edit summary
No edit summary
Line 45: Line 45:
* [[Tutorial LTL Counter-example View| Visualization of LTL Counter-examples in Rodin]]
* [[Tutorial LTL Counter-example View| Visualization of LTL Counter-examples in Rodin]]


The [http://handbook.event-b.org Rodin handbook] also contains material about ProB:
The [https://www3.hhu.de/stups/handbook/rodin/current/html/index.html Rodin handbook] also contains material about ProB:
* [http://handbook.event-b.org/current/html/tut_building_the_model.html#tut:prob  Finding Invariant Violations with ProB]
* [https://www3.hhu.de/stups/handbook/rodin/current/html/tut_building_the_model.html#tut:prob  Finding Invariant Violations with ProB]
* [http://handbook.event-b.org/current/html/tut_populate_context.html#a0000000094 Finding Solutions to Axioms]
* [https://www3.hhu.de/stups/handbook/rodin/current/html/tut_populate_context.html#a0000000094 Finding Solutions to Axioms]





Revision as of 16:27, 27 January 2021


ProB is a flexible and extensible validation tool for high-level specification formalisms. ProB supports

  • multiple languages: B, Z, CSP, Event-B, Promela, dSL, ...
  • and multiple validation techniques
: animation, model checking, ...

Below we present a gentle introduction to ProB focusing on classical B (but many of the commands are also applicable to the other formalisms such as CSP, Event-B and Z).

Understanding ProB's Animation and Constraint Solving along with Tips:

Advanced Validation with ProB:

Other Tutorials:

For ProB for Rodin, the following presents a gentle introduction:

The Rodin handbook also contains material about ProB:


For ProB for CSP, the following presents a gentle introduction:

The following tutorials concern older versions of ProB.

There are two tutorials on the physical units plugin (which is no longer supported as of ProB 1.9.0):

For Co-Simulation we have this tutorial:

We also have a tutorial for B Motion Studio.

Feedback

Please help us to improve this documentation by providing feedback in our bug tracker, asking questions in our prob-users group or sending an email to Michael Leuschel.