| Feature Description Language (FDL) top |
 | Feature Description Language (FDL) is a simple design language that allows you to define complex scenarios in a feature. | | Module, processor and object declaration can be used to define and classify the entities that will be participating in the feature. | | Types can be assigned to modules, processors and objects. This allows you to keep track of multiple instances of the same entity. | | Object Creation and Deletion is supported for dynamic objects. FDL checks if a dynamic object was created but did not get deleted before feature end. | | Message Interactions can be specified with message fields. Message interactions can be shown between processors, objects and environments. | | Environment Interactions can be shown for left and the right environment. | | Timer start, stop and expiry are fully supported. FDL also checks for missed timer stops. | | Actions can be specified for an object. Actions can be specified as a single step or with separate start and end indications. FDL checks if any actions were started but never stopped. | | Resource Allocation and Freeing can be specified for an object. FDL checks if any resource was allocated but never freed. | | State Transitions can be specified for objects. | | Multiple Scenarios in a feature can be defined using the case and leg statements. A Scenario can be defined by selecting the legs from various case statements in the feature definition. | | If-Else Statement allows further support for multiple scenario definition by allowing the developer to supply scenario variations on previously defined leg statements. | | C Type comments can be added at any place. These comments will be ignored by the parser. | | Remarks can be added after every statement. Remarks will be displayed in the right hand column in the message sequence chart. | | Block Remarks can be added to specify realtime breaks or delineate different sections of the message sequence chart. | | Issue statements can be added to mark unresolved issues in the design. Unresolved issues are shown when the FDL is reviewed. | | Page break statement allows you to force a page break in a sequence diagram. |
|
| Automatic Design Review top |
| Multiple Scenarios Review can be initiated by clicking on one icon. EventStudio will analyze all the defined scenarios and generate comments in the output window. | | Timer Management Review warns about scenarios where a timer stop might have been missed. | | Resource Management Review warns about scenarios where a resource de-allocation might have been missed. | | Action Review warns about scenarios where an action was started but never stopped. e.g. started feeding dial tone but dial tone stop was missed. | | Object Management Review warns about scenarios where a dynamic object was created but did not get deleted. | | Syntax and Semantic Review checks for correct use of FDL syntax and semantics. |
|
| Multiple Scenario Support top |
| Scenario Wizard is used to define Scenarios by specifying the case legs that define a Scenario. | | Case and leg changes are automatically synchronized. Once a Scenario has been defined, further changes in the case and leg statements associated with the Scenario are automatically reflected in the Scenario. | | Fuzzy FDL Parser is used for auto sync. This allows quick synchronization even when the FDL file might have errors. | | Multiple Scenario Definitions can be made in a Scenario Project. All the Scenarios are shown in the left pane. | | Scenarios from multiple FDL files can be included in the a single Scenario Project. | | Scenarios can be renamed, reordered or deleted any time. The names and order will be reflected in the generated documents. |
|
| Syntax Coloring Editor top |
| FDL Syntax Coloring Editor is built into EventStudio. All FDL keywords and comment/remark types are supported. | | Each editor window can be split into two or four panes, thus allowing you to simultaneously edit different parts of the same FDL file. | | Multiple FDL editors can be opened at the same same time. | | Multiple levels of Undo/Redo are supported by the FDL editor. | | Standard Search and Replace is supported. |
|
| Quick Navigation Support top |
| Scenario Leg Navigation takes you directly to the corresponding leg definitions in the FDL file. Double click on the leg icons in the left pane. | | Generated documents can be opened quickly by double clicking on the document icons in the left pane. | | Document index is generated for quick access to all documents. Document index can be opened by clicking on the document index icon. | | FDL Case Leg Tree is automatically generated, giving a birds eye view of the case and leg definitions in an FDL file. | | Case Leg Tree Navigation allows you to quickly reach any leg statement in the FDL file. | | Review Comment Navigation takes you directly to the line where EventStudio has found an error, warning or issue. Just double click on the error in the bottom pane. |
|
| Document Generation top |
| Document Wizard allows the user to specify the specifications for a document. | | Document Layout Customization. PDF document layout can be customized by specifying the column width and remark width. You can also specify the copyright string to be included on all pages. | | Reorder scenarios in the output document by just reordering the scenarios in the left pane. This can be accomplished by just dragging and dropping scenarios. | | Document Detail Customization. PDF document detail can be customized by specifying the level of detail that needs to be included in individual documents. Customization options can be changed after the document has been defined. |
|
| Message Sequence Chart Generation top |
| Generated as PDF Files. PDF is supported by the free Adobe Acrobat Reader on almost all platforms. | | Automatic Orientation. EventStudio automatically chooses between Portrait and Landscape output. | | Automatic Scaling. Message Sequence Charts will always fit on the selected paper size. | | Automatic Positioning of modules, processors and objects. Developers do not have to worry about layout issues. The order of columns in the message sequence chart can be changed by just changing the order of declarations in the FDL file. | | Most standard paper sizes are supported. You can generate output in Letter, Legal, B (11 inch x 17 inch), C(17 inch x 22 inch), A4, A3 and B4 sizes. | | Scenario and Leg Bookmarks are generated in the PDF file. This allows you to quickly move to the desired location within the PDF file. | | Intelligent Page Transition Handling. Page boundaries in the message sequence chart are defined so that individual interactions are not split across two pages. |
|
| Collaboration Diagram Generation top |
| Generated as PDF Files. PDF is supported by the free Adobe Acrobat Reader on almost all platforms. | | Automatic Scaling. Message Sequence Charts will always fit on selected paper size. | | Automatic Positioning of modules, processors and objects. Developers do not have to worry about layout issues. The order of columns in the collaboration diagram can be changed by just changing the order of declarations in the FDL file. | | Most standard paper sizes are supported. You can generate output in Letter, Legal, B (11 inch x 17 inch), C(17 inch x 22 inch), A4, A3 and B4 sizes. | | Scenario Bookmarks are generated in the PDF file. This allows you to quickly move to the desired location within the PDF file. | | Intelligent Page Transition Handling. Page boundaries are automatically selected to prevent cluttering of the collaboration diagram. |
|
| Interface and Interaction Document Generation top |
| Module interface documents only show interactions of processors and objects of the specified module with the rest of the system. | | Processor interface documents only show interactions of objects of the specified processor with the rest of the system. | | Object interface documents only shows interactions of the the specified object with the rest of the system. | | Message interface documents only show interactions with message names matching a specified pattern. | | Module, Processor and Object type based interface documents can be generated to address features where more than one module, processor or object of the same type is involved. | | Environment interaction document just shows message interactions with the environment. All other message interactions are excluded. | | Module interaction document just shows all inter module message interactions. Intra module interactions are excluded. | | Processor interaction document just shows all inter processor message interactions. Intra processor interactions are excluded. |
|
| Unit Test Procedure Generation top |
| Unit test procedure is generated in HTML format. The document can be imported into any word processor that supports HTML. | | Action, Result and Status columns are defined for each step in the testcase. | | Code Review status can also be added in the document. Unit test procedures can be used as a guide during a code review. | | Unit test procedures can be generated for an object type. In this case test cases for individual instances of the type are included in the same document. |
|
| Summary and Statistics Document Generation top |
| Summary Documents list message interactions on a per object or processor basis. Summary Documents are generated in HTML format. | | Module, processor or object summary. Summary Document can be generated for the specified module, processor or object. | | Statistics documents list module, processor and object level message interaction statistics. |
|
