Skip to main content

Timeline for Examples of Finite State Machines

Current License: CC BY-SA 2.5

10 events
when toggle format what by license comment
Jul 7, 2018 at 13:10 vote accept ocodo
Jul 7, 2018 at 13:10
Dec 13, 2012 at 3:00 comment added Evan Plaice Why does the 'Active' state point to both the 'Connect' and 'OpenSent' states if it's only function is to reset the connection for a transition to 'Idle'. The other problem is the diagram marks the transitions, not the states (ex connected, accepted, timeout, rejected, open). The states should be represented by labeling the arrows. It's good to label and describe the transitions but they usually represent the conditionals whereas the states are finite (ie hence FSM).
Apr 5, 2012 at 16:30 comment added ocodo @Job I agree, however my point is that this is a nice example, when you already know what a state machine is, so from a pedagogic perspective, it's pretty obtuse.
Apr 5, 2012 at 13:31 comment added Job @slomojo, my nitpicking was with formatting. I personally find it easier to grasp the state machine when things are arranged better, when they take advantage of the symmetry, etc. Idle should be above Connect, OpenConfirm above OpenSent, and Established filling in the leftover 6th spot at the top left. One or two arraows will intersect, but the whole diagram will be much easier to eyeball, IMO.
Apr 5, 2012 at 5:53 comment added ocodo @Job - bit of a late response, sorry, but I now keep thinking this is far too esoteric an example, the Safe, Vending Machine, etc. are way more useful I think.
Feb 15, 2011 at 3:09 comment added Job There has to be a better way to draw this.
Feb 15, 2011 at 1:14 comment added Mike Dunlavey I tried to fix the label of the chart to BGP, but it wouldn't let me - not enough characters :)
Feb 15, 2011 at 0:33 comment added tcrosley ok, +1 for including a diagram. :)
Feb 15, 2011 at 0:22 comment added ocodo @tcrosley - it's from wikipedia, so doesn't really deserve credit.
Feb 14, 2011 at 22:08 history answered ocodo CC BY-SA 2.5