StateWORKS Newsletter 1/2009
Topics:
1. Welcome
In this first newsletter in 2009 I would like to direct your attention to a specific feature of the VFSM executor that allows its execution path to be changed if required. The change is a local one, limited to one or more chosen states. A new technical note describes that interesting aspect of a VFSM specification and the RTDB based run-time system. In fact the feature has always been available, but was undocumented until now.
We added a new page on our web site that will present various interesting state machines as specified for genuine applications.
Regards
F. Wagner
2. Breaking VFSM Executor
The specification of a behavior using the finite state machine concept requires both a definition of the state machine model and the execution model. The VFSM executor uses an execution model that allows multiple transition triggered by a single event. Some situations would be better off if the execution path allows only a single transition. As these situations are normally limited to a few states in a state machine the VFSM executor can be forced for a given state to perform only a single transition..
The technical note TN25-Breaking-VFSM-Executor describes that feature of the VFSM executor and shows typical examples where it can be applied.
3. New section Technology/Solution on our web site
Our web site has a new section Solution. We should like to present there designs of state machines that are taken from real projects. We start with the Failover state machine designed for a Diameter base protocol project.
If you have designed any interesting state machine, send us the design and we will put it onto our web site. Or if you have a problem that could be solved by a state machine send us the requirements and we will do the job for you. But the problem must be complex enough to be interesting for our web site, and the result non-confidential. (Of course we can also do confidential projects for you, but not for free!).