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

EventStudio System Designer 5 Features

An example of automatic sequence diagram layout

Focus on systems engineering not diagram layout

Why waste developer time in diagram layout when EventStudio can automatically layout the diagrams?

Do not waste precious development time on clumsy graphical editors that do not scale with increasing complexity As the design gets complicated, graphical editors get increasingly difficult it with the large number of nodes involved.

A text based development language is closer to the mental model developers use when designing a system.

Powerful but simple modeling language

With EventStudio, you specify the system architecture in terms of system, subsystem, module, component and objects. The interactions between these entities can be using one of the following constructs:

Message interactions between objects. A parameter list may be specified.

Shorthand notation for message chains and multicasts.

Method invocation and object management for object oriented design.

Timer start, stop and expiry. Model protocol timers in networking and telecom.

Specify the actions taken by objects and higher level entities like modules.

Compound actions model actions that persists over time (e.g. dial-tone feed).

Resource allocation modeling. Resource leaks are caught at design time.

State transitions model object state. Messages and actions can be hyperlinked.

Wrap interactions in a sequence. This helps compacts diagrams with multiple scenarios.

Slice, dice and analyze your model

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:

Sequence diagram: Represent message and object interactions.

Use case diagram: Represent requirements as a sequence of interactions.

Interface sequence diagram: Just see interactions involving one entity.

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

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

XML Export: XML representation of the interaction model.

Catch design errors early in the lifecycle

EventStudio analyzes the design and catches design errors in success and failure scenarios. Examples of some design errors caught by EventStudio:

Resource leaks and buggy resource management
Missed object creation and deletion
Missed action completion for an action
Free running timer and invalid timer management

Zoom in and out of different abstraction levels

Hierarchically decompose the design into multiple levels (up to 5 levels)

Generate diagrams at different levels of abstraction from the same model.

Get customers, marketing team, system architects, development managers, developers and the test team on the same page. For example:

The marketing team refer to the diagram that describes only inter-system level interactions. Developers focus of detailed object interactions in a subsystem. System architects use diagrams that involve system and subsystem interactions.

Multiple scenarios along with the legs selected are shown in the left pane.

Model multiple scenarios

System architects often generate use cases and sequence diagrams only for basic scenarios. A large number of scenarios are simply left out as it is not practical to document and manage them.

EventStudio addresses these problems with built in support for multiple scenario modeling.

When designing multiple scenarios, just provide details on how the new scenario differs from the base scenarios.
Common parts shared in multiple scenarios need to be defined only one.
Automatically generate documents for a large number of success and failure scenarios