Fig. 6.1 The structure of the Dedan program Fig. 6.2 Main window of the Dedan program Fig. 6.3 Definition of actual parameters and initial state of a server (left) and graphical server design (right) Fig. 6.5 Counterexample viewed as configuration sequence execute: the next server state and the next agent message (if any). Clicking this box causes the execution of the action and the output configuration becomes current. A entire LTS can be observed as a graph (Fig. 6.7). Simulation is possible over LTS. On the left, the current configuration is shown textually and a list of next configurations is listed, each with the matching input pair of the action, leading to the next configuration. Clicking one of the next configurations makes it current. On the right, each configuration is shown in a box, and possible next configurations are appointed by arrows. The current configuration is distinguished with a green box. and the red arrows lead to the next configurations. Matching pairs are displayed on the top of each possible next configuration on a pink background. Clicking any visible configuration results in a detailed display of its data and enables taking this configuration as current. The button on upper right corner of the main window converts the model to the agent view, and displays it in a separate window. The shape of this window is similar to the main window (the server view), with the difference that formal and actual parameters are attributed to the agent types and agent variables rather than to servers. Of course, states and services are still attributed to server types. It is shown in Fig. 6.8.
