EventHelix.com: CASE Tools; Real-time and Embedded System Design; Object Oriented Design

Home | EventStudio System Designer 5 | Features | Use Cases | Contact Us

EventStudio System Designer 5 Use cases

EventStudio in telecom, object modeling, use case diagrams and reverse engineering

Model telecom flows with message sequence charts

Example of FDL - A DSL for systems engineering

Model call flows and signaling

EventStudio supports modeling of complex call and data session signaling:

Define the architecture as a multi-level hierarchy.
Model unicast, multicast and bidirectional signaling and data flow
Specify state transitions in the call flow diagrams.
Model creation and deletion of call and session contexts.
Model resources allocation and freeing of resources like signaling trunks, DSPs and timeslots.
Specify timer start, stop and expiry.
Represent signaling message interactions and inter object interactions in the same flow.
Explore more

Visualize signaling interactions

Generate well formatted diagrams to your specifications. You control the level of detail in the generated document. A rich set of document types are supported:

Detailed MSC: Represent message interactions, timers and state transitions.

High level MSC : Generate diagrams at higher level of abstraction (up to 5 levels)

Interface MSC: Just see interactions involving one entity.

Collaboration diagram: A high level view of object and message interactions.

Entity wise summary: Clearly see the roles played by different objects.

XML Export: XML representation of the interaction model.

Model object interactions with sequence diagrams

Model object interactions

EventStudio supports modeling of complex call and data session signaling:

Define the architecture as a multi-level hierarchy. The different levels could be used to represent namespaces and modules.
Model method invocation with parameters.
Specify state transitions for objects.
Model creation and deletion of objects.
Model resources allocation and freeing of resources like file descriptors, sockets etc.
Explore more

Visualize object interactions

You can visualize the interactions between objects with a rich set of diagrams and documents:

Sequence diagram: Represent object interactions and state transitions.

High level sequence diagram : Generate diagrams at higher level of abstraction.

Interface sequence diagram: Just see interactions involving one entity.

Collaboration diagram: A high level view of object and message interactions.

Entity wise summary: Clearly see the roles played by different objects.

XML Export: XML representation of the interaction model.

Specify requirements with use case diagrams

Model use cases

Specify the use cases with an easy to learn language:

Define the actors and the system as a multi-level hierarchy.
Built in support for modeling alternative scenarios. Just specify the differences between the base scenario and the alternative scenario. EventStudio generates the complete documentation for the alternative scenario (more about multiple scenarios).
Define sequences to avoid repeating common portions in alternative scenarios.
Model message interactions and object interactions in a single use case.
Explore more

Visualize signaling interactions

Generate well formatted diagrams to your specifications. You control the level of detail in the generated document. A rich set of document types are supported:

Use case diagram: Represent interactions between different actors and system entities.

High level diagram: Just see interactions between actors and system.

Actor-system collaboration: A different view of the system interactions.

Test procedures: Automatically generate tests from the use case definitions.

Entity wise summary: Clearly see the roles played by different actors and system entities.

XML Export: XML representation of the use case flow.

Reverse engineer and visualize design from traces

Write a script to convert traces to FDL

EventStudio models are stored in text files (FDL). These files can easily be generated from any programming language. Thus a script can be easily written to convert a trace output to FDL.

Guidelines for a such a script are:

Read the traces to identify the system hierarchy.
Convert message handling traces to message statements.
Map state transition traces to trace statements.
Translate general traces to action statements
Constructor entry trace can be mapped to object creation in FDL.
Similarly destructor can be mapped to object deletion.
Resource allocation and freeing can also be mapped to FDL.
Method entry trace can map to an object invoke statement
Method exit can be converted into an FDL return statement

Trace visualization workflow

Once you have a trace to FDL conversion scipt in place, a few more steps are needed for trace visualization:

Download tracing.zip. This project contains a default scenario project that expects a trace.fdl header file.
Make sure that conversion script replaces this trace.fdl file.
Add the EventStudio installation direction to the command-line search path.
Use the "evstudio TraceProject.scn /GenerateAll" command-line to generate a sequence diagram and context diagram..

Home | EventStudio System Designer 5 | Features | Use Cases | Contact Us