Sandén (2011) defines state diagrams as a way to show the possible states an object could be on. He also defines, that events are action verbs that occur on an arrow between two events (if an action doesn’t change the state it can be listed in the state). Whereas an action can have conditions on them.
Thus, a state diagram shows the transition from state to state as events occur. An event usually has many occurrences, and they are instantaneous. Finally, a super-state can encompass multiple states (Sandén, 2011). An activity is an operation that takes time, and it has the keyword “do /”
The goal of this post was to make a state diagram of Maekawa’s voting algorithm on the “Maekawa’s algorithm” within the “Distributed mutual exclusion” set. This can be done in various ways. One option is the following 5 states:
- Released and not voted
- Released and voted
- Wanted and not voted
- Wanted and voted
- Held and voted (for self)
- request_received, etc., for messages arriving from other nodes
- acquire for when the local node wants the lock
- release for when the local node gives up the lock.
A possible solution is shown below:
- Sandén, B. I. (2011-01-14). Design of Multithreaded Software: The Entity-Life Modeling Approach, 1st Edition. [VitalSource Bookshelf Online]. Retrieved from https://bookshelf.vitalsource.com/#/books/9781119143086/