Updated Introduction (markdown)

ni-richard 2019-09-10 13:33:59 +02:00
parent 44b371fe98
commit 558394cb89

@ -8,4 +8,4 @@ In the upper-left part of the page you can see the chat bot, right next to it is
### Sequence of events ### Sequence of events
Everything that has a beginning has an end. Generally, you can define the steps of an exercise using a [finite-state machine](https://en.wikipedia.org/wiki/Finite-state_machine). This means that certain events can trigger a transition from one state to another. For instance, you want the user to login in your web service, and if it was successful, you would trigger the next step by notifying the *TFW server*, which will forward your message to the *FSM* instance that evaluates your request, and finally the state change happens, and additional logic is executed to prepare the environment for the next step until the last. Everything that has a beginning has an end. Generally, you can define the steps of an exercise using a [finite-state machine](https://en.wikipedia.org/wiki/Finite-state_machine). This means that certain events can trigger a transition from one state to another. For instance, you want the user to login in your web service, and if it was successful, you would trigger the next step by notifying the *TFW server*, which will forward your message to the *FSM* instance that evaluates your request, and finally the state change happens, and additional logic is executed to prepare the environment for the next step until the last.
This was just a short summary, you can find detailed description regarding each component in the wiki. In the second chapter, you will find detailed description regarding each component.