Allow generation of state tables and sample runs

[GoogleCodeExporter]

Add a generator generate state-state and state-event tables. See the attached 
file for examples and semantics.

Also add a generator to generate a random sequence of events (selected from the 
possible events in the model) and a table showing what state the system would 
be in after every transition. Each run of the generator would give a different 
result. It could be biased to 'normally' choose events that are in fact 
expected, but not always. This would be very good pedagogically.
Please use tags such as 'stateMachines', 'Tracing', etc. to help us
categorize this request.

Original issue reported on code.google.com by TimothyCLethbridge on 24 Jul 2014 at 2:16

Attachments:

• StateTableForUmpleIssue.xlsx

[GoogleCodeExporter]

Original comment by TimothyCLethbridge on 5 Sep 2014 at 3:08

• Added labels: Priority-High, ucosp
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by TimothyCLethbridge on 5 Sep 2014 at 3:11

• Added labels: Type-ProjectUG
• Removed labels: Type-Enhancement

[GoogleCodeExporter]

Original comment by CraigBry...@gmail.com on 9 Feb 2015 at 1:19

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Here's a draft of the colouring of sub-states and sub-sub-states (see the tabs 
at the bottom left of the page to switch between examples):

https://docs.google.com/spreadsheets/d/1aL_elQ95AO0ehovMzsg6Auo3VK2ec6e4l74j1UNW
cFE/edit?usp=sharing

Original comment by CraigBry...@gmail.com on 9 Feb 2015 at 2:10

• Changed state: Ongoing

[GoogleCodeExporter]

The state tables are implemented now, and I'm turning my focus to the 
generation of sequences of events. I have a few questions to help me get 
started: 

How do you envision the layout of a table showing the resulting state after 
each transition? States as rows and the series of transitions as the columns? 
Then the cell at (current state, last transition) would contain a marker or be 
highlighted in some way? This would allow for concurrency, but may result in 
very large tables.

How many transitions should be generated? Should we generate a random walk 
until all states are visited? Until all transitions are taken?

How should guards be dealt with to ensure visiting all states/ doing all 
transitions?

Original comment by CraigBry...@gmail.com on 3 Mar 2015 at 1:44