wiki:news:27okt2012
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
wiki:news:27okt2012 [2012/11/19 19:23] – [Points to consider with regions] pmueller | wiki:news:27okt2012 [2012/11/19 22:12] – [New beta version supporting regions] pmueller | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
In state diagrams usually only one state is active at a time. In UML state diagrams regions also allow to model concurrency - i.e. more than one state is active at a time (AND states). | In state diagrams usually only one state is active at a time. In UML state diagrams regions also allow to model concurrency - i.e. more than one state is active at a time (AND states). | ||
Line 151: | Line 151: | ||
** Regions must work on the same instance data ** | ** Regions must work on the same instance data ** | ||
- | State diagrams follow the // | + | State diagrams follow the // |
+ | |||
+ | * If the event '' | ||
+ | * But there is no state change in region '' | ||
+ | * This behavior ensures that the result of a machine execution step is 100% predictable and e.g. not dependent | ||
+ | * But on the other side it means that a second run of the machine is required to reach state '' | ||
{{ : | {{ : |
wiki/news/27okt2012.txt · Last modified: 2022/08/17 19:47 by pmueller