IBM
Contents Index Previous Next



Generating and Starting an SDL Explorer


In addition to simulating a system, it is also possible to validate the system using the SDL Explorer. An explorer can be used to automatically find errors and inconsistencies in a system, or to verify the system against requirements.

In the same way as for a simulator, you must generate an executable explorer and start it with a suitable user interface.

Note:

In order to generate an explorer that behaves as stated in the exercises, you should use the SDL diagrams that are included in the distribution instead of your own diagrams. To do this:

  • On UNIX: Copy all files from the directory
    $telelogic/sdt/examples/demongame
    to your work directory ~/demongame.
  • In Windows: Copy all files from the directory
    C:\IBM\Rational\SDL_TTCN_Suite6.3\sdt\examples\demongame
    to your work directory
    C:\IBM\Rational\SDL_TTCN_Suite6.3\work\demongame
    .

If you generate an explorer from the diagrams that you have created yourself, the scheduling of processes (i.e. the execution order) may differ.

If you choose to copy the distribution diagrams, you must then re-open the system file demongame.sdt from the Organizer.

What You Will Learn

Quick Start of an SDL Explorer

An explorer can be generated and started in the same way as described earlier for the simulator, i.e., by using the Make dialog and the Tools menu in the Organizer. However, we will now show a quicker way.

  1. Make sure the system diagram icon is selected in the Organizer.
  2. Click the Explore quick button. The following things will now happen, in rapid succession:
    • An executable explorer is generated. Messages similar to when generating a simulator are displayed in the Status Bar, ending with "Analyzer done." This is the same action as manually using the Make dialog and selecting an explorer kernel. If you like, you can verify that an explorer kernel has been used by looking at the tail of the Organizer log.
    • A graphical user interface to the explorer is started. The status bar of the Organizer will read "Explorer UI started." This is the same action as manually selecting Explorer UI from the Tools menu.
    • The generated explorer is started. The Explorer UI shows the message "Welcome to SDL EXPLORER." This is the same action as manually using the Open quick button and selecting the executable explorer (named demongame_xxx.val (on UNIX), or demongame_xxx.exe (in Windows), where the _xxx suffix is platform or kernel/compiler specific).

Note:

If you receive errors from the Make process (in the Organizer Log window) or if no Explorer is started, do as follows:

  • Open the Make dialog and change to a Validation kernel reflecting the C compiler used on your computer system, e.g.
    gcc-Validation or Microsoft Validation.
  • Click the Full Make button and check that no errors where reported.
  • Click the Explore quick button again. An Explorer should now be started as described above.

The Explorer UI looks like this:

Figure 122 : The main window of the Explorer UI

As you can see, the graphical user interface of an explorer is very similar to a simulator GUI, which you have learned to use in the previous exercises. However, the button modules to the left are different and a few extra menus are available.

An explorer contains the same type of monitor system as a simulator. The only difference is the set of available commands.

When an explorer is started, the static process instances in the system are created (in this case Main and Demon), but their initial transitions are not executed. The process in turn to be executed is the Main process. You can check this by viewing the process ready queue:

  1. Locate the button module View in the left part of the window, and click the Ready Q button. The first entry in the ready queue is Main, waiting to execute its start transition.
    • If the View module appears to be empty, you have to click the toggle button to the left of the module's name. The button module is then expanded. You may collapse and expand any button module by using these toggle buttons:

Figure 123 : A collapsed button module

  1. If required, resize the Explorer UI window so that all button modules are visible. You may also reduce the width of the text area. In the exercises to come, you will have a number of windows open at the same time.

Basics of an SDL Explorer

Before you start working with the explorer exercises, you should have an understanding about the basic concepts of the SDL Explorer.


http://www.ibm.com/rational
Contents Index Previous Next