Finite State Machine pattern

[stephen-lazarionok]

Description:
The Finite State Machine (FSM) design pattern is a behavioral design pattern used to model the behavior of a system that can be in one of a finite number of states. The system transitions from one state to another in response to external events or internal actions. This pattern is useful in scenarios where an object’s behavior is dependent on its state, and the state can change in response to events.

Main elements of Finite State Machine pattern:

1. States: Define the possible states the system can be in.
2. Transitions: Define the rules or conditions that trigger a change from one state to another.
3. Events: Actions or occurrences that cause state transitions.
4. Context: Maintains the current state of the system and facilitates state transitions.
5. State Interface: Defines the behavior associated with each state. Each state implements this interface to define its specific behavior.

References:

• State Design Pattern - Refactoring Guru
• State Machines - Martin Fowler
• GitHub Contribution Guidelines

Acceptance Criteria:

1. Implement the FSM pattern with at least three distinct states and the transitions between them.
2. Create a context class that maintains the current state and handles state transitions based on events.
3. Provide example scenarios demonstrating the FSM pattern, including state definitions, transitions, and event handling.

[iluwatar]

Hi there @stephen-lazarionok ,

I am aware of the State pattern but unfamiliar with the FSM. Can you point the source of the pattern, web link or some book maybe?

[stephen-lazarionok]

Here is the information about FSM:
The description of the pattern
FSM in Erlang - very nice explanation
The implementation of FSM in Akka

[iluwatar]

Thank you for the links. Especially the first explains the pattern well. We'll accept the pattern once you make the pull request.

[stephen-lazarionok]

Initial pull request is ready - Finite state machine #222. I will add the documentation later as well as include this module to the parent pom.xml later.

[amit2103]

@iluwatar Can I work on this?

[iluwatar]

@amit2103 Yes, I will change the labels

[iluwatar]

@amit2103 any updates?

[amit2103]

@iluwatar COmpleted..Writing Junits

[iluwatar]

@amit2103 are you still working on this?

[iluwatar]

No answer, so this issue is free for taking once again.

[npczwh]

@iluwatar I'd like to take this

[iluwatar]

@JMZ-kk are you working on this?

[JMZ-kk]

Sorry, I have no more time to work on this now.

…

------------------ 原始邮件 ------------------ 发件人: "Ilkka ***@***.***>; 发送时间: 2022年9月22日(星期四) 凌晨2:12 收件人: ***@***.***>; 抄送: ***@***.***>; ***@***.***>; 主题: Re: [iluwatar/java-design-patterns] Finite State Machine pattern (#203) @JMZ-kk are you working on this? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[JanFidor]

@iluwatar could I pick up this magnificent pattern?

[ohbus]

⭐ Sure thing! Thanks for your interest in our project 😃

✔️ Please mention a 📆 timeline 🕙 for when can we expect 🤔 a Pull Request against this issue.

🤝 Looking forward to your contribution.
📖 Be sure to check out our Wiki section

[JanFidor]

@ohbus Hi, as for 📆 timeline I should be able to make a PR in ~2-3 days, but to eer on the side of caution, it will definitely be finished within a week.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[iluwatar]

Updated task description