Getting Started with EventStudio Introduction to FDL Comments, Remarks and Issues Object Management and Message Parameters Timer and Resource Management State Machine Operations, Actions and Environment Defining Types for Modules, Processors and Objects Multiple Scenario Support Tutorial Sequence Diagram pdf

Home > EventStudio System Designer > Sequence Diagram Tutorial > Introduction
Introduction to FDL

The following conventions are used in the description:

• New language concepts will be introduced as statements in bold font. 
• Lines corresponding to the new statements are numbered and the corresponding description can be found below the file contents.

The FDL file and documents generated at each stage are available in the Tutorial directory of the EventStudio installation.

 

Call1.fdl

1. module : customer, exchange 2. processor : phone in customer 2. processor : frontend in exchange, core in exchange 3. feature "Call Setup" 4. offhook : phone -> frontend dialtone : frontend -> phone digits : phone -> frontend setup_call : frontend -> core setup_complete : core -> frontend ringback : core -> phone endfeature

1. This program defines the message exchanges between a customer and a telephone exchange. The customer and the exchange have been declared with the module declaration. 
2. The processor statements in the next two lines define different entities within the customer and the exchange. Here the customer contains a phone and the exchange contains a frontend and a core processor. This relationship is specified using the in keyword.
3. The feature-endfeature block follows the declarations in FDL. A title for the feature is included in the feature declaration. The feature…endfeature block encloses all the feature interactions between the customer and the exchange.
4. Message interactions have been enclosed within the feature-endfeature block. The first message interaction in the sequence sends an offhook message from the phone to the frontend processor. This is followed by other message interactions involved in call setup. Messages are represented as arrows from the source to the destination.

Examine the  Call1 section of the final sequence diagram file at this point to see the correspondence between the FDL file and PDF output.

Note: FDL also supports a multicast statement for modeling message interactions where a single message is simultaneously received by multiple entities. This statement has not been covered in this tutorial.