Tutorial: Difference between revisions

No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 12: Line 12:
* [[Tutorial First Model Checking|First steps in model checking]]
* [[Tutorial First Model Checking|First steps in model checking]]
* [[Tutorial Complete Model Checking|Complete model checking]]
* [[Tutorial Complete Model Checking|Complete model checking]]
* [[Tutorial Tuning Model Checking|How to tune model checking]]


Understanding ProB's Animation and Constraint Solving along with Tips:
Understanding ProB's Animation and Constraint Solving along with Tips:
Line 21: Line 22:
* [[Tutorial Understanding ProB's Constraint Solver]]
* [[Tutorial Understanding ProB's Constraint Solver]]
* [[Tutorial Debugging Well-Definedness and Transition Errors]]
* [[Tutorial Debugging Well-Definedness and Transition Errors]]
* [[Tips for Large Specifications]]


Advanced Validation with ProB:
Advanced Validation with ProB:

Latest revision as of 16:21, 2 October 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.