{"id":8118,"date":"2022-03-05T09:45:56","date_gmt":"2022-03-05T09:45:56","guid":{"rendered":"http:\/\/fastbitlab.com\/?p=8118"},"modified":"2023-08-24T11:40:00","modified_gmt":"2023-08-24T06:10:00","slug":"fsm-lecture-60-exercise-007-states-signals-and-data-structure-used","status":"publish","type":"post","link":"https:\/\/fastbitlab.com\/blog\/fsm-lecture-60-exercise-007-states-signals-and-data-structure-used\/","title":{"rendered":"FSM Lecture 60: Exercise-007 States, Signals and Data structure used"},"content":{"rendered":"
\n
\n
\n
\n

 <\/p>\n<\/div>\n

\n

Exercise-007 States, Signals and Data structure used<\/strong><\/span><\/h1>\n
\n
\n
\n

 <\/p>\n

<\/div>\n

 <\/p>\n<\/div>\n<\/div>\n<\/div>\n

In the previous article, you just saw the demo of the 007ClockAlarm application. You can imagine a few states in the application by seeing the demo. <\/span><\/p>\n

Sometimes, the application presents the current time to the user, which I will call a <\/span>ticking mode <\/b>or a <\/span>ticking state of the project<\/b>.  The user can also do a clock setting; that’s why we can introduce one more state called <\/span>clock setting<\/b>.  And the user can also do the Alarm setting; that’s why we can introduce one more state called <\/span>Alarm setting<\/b>.<\/span><\/span><\/p>\n

You can imagine such states or write it down on paper before modeling through the software.<\/span><\/p>\n

\"Figure
Figure 1. States in the application<\/span><\/figcaption><\/figure>\n

 <\/p>\n

The ticking state is our initial state. Whenever you give power to the application, our application will be in ticking mode, showing the current time to the user.<\/span><\/p>\n

 <\/p>\n

\"Figure
Figure 2. States in the application<\/span><\/figcaption><\/figure>\n