|
Home > EventStudio System Designer > What's New in 4.0 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 1. | FDL Preprocessor FDL has been enhanced to support a powerful preprocessor that is similar to the C preprocessor.
| #include "architecture.fdl" Include an FDL file located in the current directory. | ||||||||||||||||
#include <theme.fdl> Include an FDL file from the paths specified in | ||||||||||||||||||
#ifdef UMTS_RELEASE_7 #else #endif Conditional compilation is supported with the #ifdef-#else-#endif statement. | ||||||||||||||||||
#define msg_ack(msg, a, b) "msg" : a -> b;\ Macros may be defined with multiple parameters. Macros may be nested. | ||||||||||||||||||
| 2. | Summary Sequence Diagrams at Module and Processor Level · Inter module interaction sequence diagram is drawn at module level. The diagram completely hides the processor and object level detail. · Inter processor interaction sequence diagram is drawn at processor level. The diagram completely hides the object level detail. | 1. Add module and processor interaction sequence diagrams using the “Add Document” icon. 2. Use the “Generate All” documents to generate the interactions sequence diagrams.
| ||||||||||||||||
| 3. | Joint Actions Involving Multiple Objects The action statement has been enhanced to support actions involving multiple objects. The objects may spawn processor and module boundaries. | The syntax for the statement is: a, b, c take action "Joint action" | ||||||||||||||||
| 4. | Bidirectional Interaction Support in Message Statement Bidirectional message interactions can now be depicted as double headed arrows. | The syntax for the statement is: Voice : a <-> b | ||||||||||||||||
| 5. | Weighted Arrow in Message Statement Important message interactions can be represented with a thicker arrow. | The syntax for the statement is: Message : a => b Message : a <=> b | ||||||||||||||||
| 6. | Message to Self Support Message to self is represented as an arrow pointing back to the object axis. | The syntax for the statement is: Message : a -> a | ||||||||||||||||
| 7. | Object Method Interaction Modeling EventStudio now supports special statements for method level modeling. Method invocation and return can be modeled using the "invokes" and "returns" statements. The method invocations are represented with UML style instance axis. | A few examples are: CallManager invokes Call.HandleInvite(msg) Call invokes MessageHandler.Send(SIP_OK) Call.HandleInvite returns
| ||||||||||||||||
| 8. | Forward Goto Statement EventStudio now supports forward goto statements to simplify definition of multiple scenarios.
| case leg "Call routing failed": | ||||||||||||||||
| 9. | Case statements can be nested within if-else-endif statements EventStudio supports nesting of case statements inside if-else-endif statement. This simplifies the organization of case statements in a file. | if "Success" case leg "Failure3": | ||||||||||||||||
| 10. | Periodic Timer Support EventStudio now supports periodic timers. A periodic timer keeps running even after a timeout.
| e starts periodic t42 /*…*/ timeout t42 /*…*/ timeout t42 /*…*/ e stops t42 | ||||||||||||||||
| 11. | Visual Ether Protocol Analyzer Support VisualEther Protocol Analyzer is a new product from EventHelix.com Inc. VisualEther allows you to generate Sequence diagrams and collaboration diagrams from Ethereal PDML files. EventStudio has been enhanced to support larger size sequence diagrams with a larger number of entries. | |||||||||||||||||
| 12. | Style Support for Messages EventStudio supports style specification for message statements.
| The style is specified as: module: m style sip: color="1.0,0.0,0.0", feature "Testing" | ||||||||||||||||
| 13. | Section Heading Support A large sequence diagram may be subdivided into sections using the heading statement. · The headings are displayed as a block remark. · A bookmark to the headings is added in the left pane of a PDF sequence diagram file. · Message numbering is reset when headings are encountered. | The syntax for headings is shown in the following example: heading "Conversation Mode"
| ||||||||||||||||
| 14. | Support for Wide Range of Font Sizes Any font size between 1 and 35 may be specified in the Tools->Options->Font Selection tab. The font size range has been expanded for:
| |||||||||||||||||
| 15. | Reverse Arrow Support in Message Statement Reverse arrows may be used in the message statements. This is convenient when dealing with acknowledgements and responses. | For example: "SIP INVITE" : Terminal -> SCSF "SIP OK" : Terminal <- SCSF | ||||||||||||||||
| 16. | Hyperlink Support in "take action", "takes action" and message statements (unidirectional and bidirectional messages) Hyperlinks can be specified in single action and joint action statements. The hyperlinks may refer to files on the internet or a local path. Clicking on the link in the PDF sequence diagram opens the linked document in another window. Note: Hyperlinks are not supported in Microsoft Word Picture (EMF) documents. | The syntax is: obj takes action "Handover" <file://c:\Doc\handover.pdf> a, b take action "SIP Call" <http://rfc.net/rfc3261.html> Invite : src -> dst <file://c:\Doc\intf.htm#Msg>
| ||||||||||||||||
| 17. | Strings May be Used in Module, Processor or Object Names Strings may be used to denote module, processor or object names. This allows the developers to use terms like "I-SCSF", "192.168.10.20". | The syntax is: module: Customer, "IP Multimedia System" processor: "User Terminal" in Customer processor: "I-SCSF" in "IP Multimedia System" eternal : "192.168.20.45" in "User Terminal" | ||||||||||||||||
| 18. | Message Parameter May be Spread Over Multiple Lines The message parameters may be spread over multiple lines. This helps in documenting long parameter lists. | The syntax is: "My Message" (name="XYZ", | ||||||||||||||||
| 19. | Light Weight Header A light weight header that lists the axis only for the lowest level entities. The light weight header does not include the page number and title. This makes the diagrams suitable for inclusion in other documents. | Select the light weight header from the Tools->Options menu and Customize tab | ||||||||||||||||
| 20. | Style Support for Instance Axis Style specifications can now be added to the module, processor and object declarations. The styles allow you to define a color, line style and a font size for the instance axis.
| The style specification example is shown here: style pstyle: color="1.0,0.0,0.0" style cstyle: color="0.0,1.0,0.0" style rstyle: color="0.0,0.0,1.0" module : [pstyle] phone, bts, bsc processor: [cstyle] cpu in phone eternal: [rstyle] rlc_mac in cpu
| ||||||||||||||||
| 21. | Image Specification in Instance Style An image may be specified in the instance styles. JPEG images are supported. The image in a style is used if "Light weight header with image" is selected from the "Tools->Options->Customize tab".
| The style specification with image is shown here: style pstyle: image="c:\phone.jpg" style cstyle: image="c:\xscale.jpg" style rstyle: image="c:\sphere.jpg" module : [pstyle] phone processor: [cstyle] cpu in phone eternal: [rstyle] rlc_mac in cpu | ||||||||||||||||
| 22. | Optional Right Side Remarks The remarks displayed on the right side may be disabled from the "Tools->Options->Customize tab". | Use the "Tools->Options->Customize tab" to disable the right side remark column. | ||||||||||||||||
| 23. | Message Chain Statement Define a message chain to model a chain of messages that are triggered in a sequence. EventStudio attempts to draw all messages in a message in a single line. | The syntax is: chain | ||||||||||||||||
| 24. | Style Support in "take action", "takes action", "begin action", "end action", "allocates", "frees" and "state" statements The style statement gives you full control over the color, font and line style in the action, resource management and state related statements.
| The syntax is: [my_style] obj1, obj2 take action "Joint action" [my_style] object1 takes action "Single action" [my_style] object1 begins action "Feed Dialtone" [my_style] object1 ends action "Feed Dialtone" [my_style] object1 allocates "Channel" [my_style] object1 frees "Channel" [my_style] object1 state = "Awaiting Digits" | ||||||||||||||||
| 25. | Theme Support Themes provide an overall control over the document layout. Most Tools->Options commands can be overridden using themes. A theme statement based on the current settings can be automatically copied to the clipboard using the Tools->Copy Options as Theme command.
| A theme declaration consists of a theme name followed by a sequence of attribute-value pairs. The syntax is: theme MyTheme: blockRemarkFormatting="right-align", theme LeftAlign: blockRemarkFormatting="left-align" {MyTheme} feature "a feature" Theme may be modified within the feature-endfeature block by placing the theme modifier on a line. For example: {MyTheme} feature "a feature" | ||||||||||||||||
| 26. | Scenario Project Templates Scenario Project can now be defined from a predefined list of templates. You may also define your own templates. | Click on the "New" icon and then select the "Scenario Project From Template" option. | ||||||||||||||||
| 27. | Joint State Transition, Action Begin/End, Allocate/Free Support The following joint statements are now supported:
| All joint action statements support style specification. [mystyle] A, B, C begin action "feed dial tone" A, B allocate "time slot" A, B free "time slot" [mystyle] A,B,C end action "feed dial tone" [mystyle] A,B,C state = "Conversation" | ||||||||||||||||
| 28. | Auto Synchronize FDL files and PDF Documents EventStudio automatically synchronizes FDL files and open PDF document. If a PDF document is already open, a new version of the document will is reopened after the document generation has been completed.
| |||||||||||||||||
| 29. | Single Click Document Save, Generate and Display EventStudio greatly simplifies the process of editing FDL by providing instant feedback on the final sequence diagram. A single click or command saves all changes, generates the document and displays the output. The command works even when the document was already open. | Use any of the following to save, generate and display:
| ||||||||||||||||
| 30. | Hierarchically Assign Images to Modules, Processors and Objects EventStudio image header assignment algorithm has been enhanced as detailed in the diagram below:
| |||||||||||||||||
| 31. | Specify Custom Paper Sizes in EMF and PDF Documents Uses can now select custom paper sizes. The custom paper size may be selected from:
| |||||||||||||||||
| 32. | Other Enhancements · EMF file naming has been enhanced to include scenario names. | |||||||||||||||||
| Related Links |
|