xjCharts презентация

of event-driven software
A graphical Editor that creates and handles statechart objects in C++ or Java code
A runtime Engine that executes your statecharts according to UML semantics
Editor is easy to use
Engine is fast

its execution, a program performs operations in response to the external or internal events and conditions
Sometimes, this event and time ordering of operations is so pervasive that we can best formally characterize the behavior of such programs in terms of a statechart
David Harel

on the market:
iLogix Statemate
Rational Rose
ObjecTime Developer
ISI BetterState
They are heavyweight environments that force developer to learn a lot, to follow certain design templates, to use project files, etc
Poor integration with other tools developers use

that a component of the system is event-driven
They want to stay with their favorite development environment and rapidly insert a statechart into an existing project
They want the statechart to work fast, with minimum overhead
They do not want to learn a new environment

file between your DE and xjCharts Editor
Two synchronized views on source: graphics and text – edit either
Development platform: Win32

1.1
Everything is generated while you draw
The complete information about the statechart is stored in the source file – no extra files needed

fast: up to 500,000 events per second on Intel Pentium II 450 MHz
Is a library compiled for each target platform
Source may be licensed

/ gcc or pgcc
QNX / Watcom C++
Any Java 1.1 compatible platform
“No OS”
VxWorks
HP-UX

Under Development

state

Simple state

Final state

Transition

Boolean expr. Trigger: Event / Timeout
Action: Code

Guard: Boolean expr. Action: Code

and deep history states
Final states
UML Event model
xjCharts does not support:
Orthogonal states

in your source code
C++ and Java generated while you draw
Development platform: Win32
Target: Win32, Linux, QNX, Java, “no OS”
Fast Engine: 500,000 eps on PII 450
Platform-independent event model
UML syntax and semantics