Code Generation Tutorial

From Event-B
Revision as of 16:44, 7 December 2010 by imported>Andy (→‎Viewing an IL1 Model)
Jump to navigationJump to search

This Page is Under Construction

Tutorial

The aim of the tutorial is to give a allow users to explore the approach with a relatively simple example. The example uses a shared buffer and reader and writer process.

  • Step 1 - Create the tasking development.
  • Step 2 - Add annotations.
  • Step 3 - Invoke translators.

Preliminaries

Before discussing the modelling aspects further we discuss the PrettyPrint viewers. The PrettyPrinters make the viewing of tasking models easier, and provides a quick route to source code generation. The source code can easily be pasted into an Ada source file.

Viewing a Tasking Development

From the top-menu select Window/Show View/Other/Tasking Pretty Printer.

Note that the Tasking PrettyPrinter may have to be closed when editing the Tasking Development, since it can give rise to exceptions. The PrettyPrinter would need further work to make it robust, however it is intended only as a short-term solution.

Viewing an IL1 Model

From the top-menu select Window/Show View/Other/IL1 Pretty Printer.

Open the SharedBuffer20100819Demo Project and switch to the Resource Perspective. Open the .il1 model and inspect it. Clicking on the Protected, Main Entry, or Task nodes updates the pretty print window.

Creating The Tasking Development

From the Event-B Perspective,

Open the SharedBuffer20100819Tutorial Project.

Select the following Machines: Reader, Writer and Shared.

Right-click and select Make Tasking Development/Generate Tasking Development.

The new Tasking Development will not be visible in the Event-B perspective, change to the resource perspective, open and inspect the new .tasking file. The Tasking Development contains the machines that we wish to provide implementations for. In order to introduce the new concepts we have prepared a partially complete development.

Go to the Project SharedBuffer20100819Tutorial2 to begin the next step.

Providing the Annotations for Implementations