A finitestate machine (FSM) or finitestate automaton (plural: automata), or simply a state machine, is a mathematical model of computation used to design both computer programs and sequential logic circuits. It is conceived as an abstract machine that can be in one of a finite number of states. The machine is in only one state at a time; the state it is in at any given time is called the current state. It can change from one state to another when initiated by a triggering event or condition; this is called a transition. A particular FSM is defined by a list of its states, and the triggering condition for each transition.
The behavior of state machines can be observed in many devices in modern society that perform a predetermined sequence of actions depending on a sequence of events with which they are presented. Simple examples are vending machines, which dispense products when the proper combination of coins is deposited, elevators, which drop riders off at upper floors before going down, traffic lights, which change sequence when cars are waiting, and combination locks, which require the input of combination numbers in the proper order.
Finitestate machines can model a large number of problems, among which are electronic design automation, communication protocol design, language parsing and other engineering applications. In biology and artificial intelligence research, state machines or hierarchies of state machines have been used to describe neurological systems. In linguistics, they are used to describe simple parts of the grammars of natural languages.
Considered as an abstract model of computation, the finite state machine is weak; it has less computational power than some other models of computation such as the Turing machine.^{[1]} That is, there are tasks that no FSM can do, but some Turing machines can. This is because the FSM memory is limited by the number of states.
FSMs are studied in the more general field of automata theory.
Contents

Example: coinoperated turnstile 1

Concepts and terminology 2

Representations 3

State/Event table 3.1

UML state machines 3.2

SDL state machines 3.3

Other state diagrams 3.4

Usage 4

Classification 5

Acceptors and recognizers 5.1

Start state 5.1.1

Accept (or final) states 5.1.2

Transducers 5.2

Generators 5.3

Determinism 5.4

Alternative semantics 6

FSM logic 7

Mathematical model 8

Optimization 9

Implementation 10

Hardware applications 10.1

Software applications 10.2

Finite automata and compilers 10.3

See also 11

References 12

Further reading 13

General 13.1

Finite state machines (automata theory) in theoretical computer science 13.2

Abstract state machines in theoretical computer science 13.3

Machine learning using finitestate algorithms 13.4

Hardware engineering: state minimization and synthesis of sequential circuits 13.5

Finite Markov chain processes 13.6

External links 14
Example: coinoperated turnstile
State diagram for a turnstile
A turnstile
An example of a very simple mechanism that can be modeled by a state machine is a turnstile.^{[2]}^{[3]} A turnstile, used to control access to subways and amusement park rides, is a gate with three rotating arms at waist height, one across the entryway. Initially the arms are locked, blocking the entry, preventing patrons from passing through. Depositing a coin or token in a slot on the turnstile unlocks the arms, allowing a single customer to push through. After the customer passes through, the arms are locked again until another coin is inserted.
Considered as a state machine, the turnstile has two states: Locked and Unlocked.^{[2]} There are two inputs that affect its state: putting a coin in the slot (coin) and pushing the arm (push). In the locked state, pushing on the arm has no effect; no matter how many times the input push is given, it stays in the locked state. Putting a coin in – that is, giving the machine a coin input – shifts the state from Locked to Unlocked. In the unlocked state, putting additional coins in has no effect; that is, giving additional coin inputs does not change the state. However, a customer pushing through the arms, giving a push input, shifts the state back to Locked.
The turnstile state machine can be represented by a
state transition table, showing for each state the new state and the output (action) resulting from each input
Current State

Input

Next State

Output

Locked

coin

Unlocked

Unlock turnstile so customer can push through

push

Locked

None

Unlocked

coin

Unlocked

None

push

Locked

When customer has pushed through, lock turnstile

It can also be represented by a directed graph called a state diagram (above). Each of the states is represented by a node (circle). Edges (arrows) show the transitions from one state to another. Each arrow is labeled with the input that triggers that transition. Inputs that don't cause a change of state (such as a coin input in the Unlocked state) are represented by a circular arrow returning to the original state. The arrow into the Locked node from the black dot indicates it is the initial state.
Concepts and terminology
A state is a description of the status of a system that is waiting to execute a transition. A transition is a set of actions to be executed when a condition is fulfilled or when an event is received. For example, when using an audio system to listen to the radio (the system is in the "radio" state), receiving a "next" stimulus results in moving to the next station. When the system is in the "CD" state, the "next" stimulus results in moving to the next track. Identical stimuli trigger different actions depending on the current state.
In some finitestate machine representations, it is also possible to associate actions with a state:

Entry action: performed when entering the state,

Exit action: performed when exiting the state.
Representations
Fig. 1 UML state chart example (a toaster oven)
Fig. 2 SDL state machine example
Fig. 3 Example of a simple finite state machine
State/Event table
Several state transition table types are used. The most common representation is shown below: the combination of current state (e.g. B) and input (e.g. Y) shows the next state (e.g. C). The complete action's information is not directly described in the table and can only be added using footnotes. A FSM definition including the full actions information is possible using state tables (see also virtual finitestate machine).
State transition table
Current state →
Input ↓

State A

State B

State C

Input X

…

…

…

Input Y

…

State C

…

Input Z

…

…

…

UML state machines
The Unified Modeling Language has a notation for describing state machines. UML state machines overcome the limitations of traditional finite state machines while retaining their main benefits. UML state machines introduce the new concepts of hierarchically nested states and orthogonal regions, while extending the notion of actions. UML state machines have the characteristics of both Mealy machines and Moore machines. They support actions that depend on both the state of the system and the triggering event, as in Mealy machines, as well as entry and exit actions, which are associated with states rather than transitions, as in Moore machines.
SDL state machines
The Specification and Description Language is a standard from ITU that includes graphical symbols to describe actions in the transition:

send an event

receive an event

start a timer

cancel a timer

start another concurrent state machine

decision
SDL embeds basic data types called Abstract Data Types, an action language, and an execution semantic in order to make the finite state machine executable.
Other state diagrams
There are a large number of variants to represent an FSM such as the one in figure 3.
Usage
In addition to their use in modeling reactive systems presented here, finite state automata are significant in many different areas, including electrical engineering, linguistics, computer science, philosophy, biology, mathematics, and logic. Finite state machines are a class of automata studied in automata theory and the theory of computation. In computer science, finite state machines are widely used in modeling of application behavior, design of hardware digital systems, software engineering, compilers, network protocols, and the study of computation and languages.
Classification
The state machines can be subdivided into Transducers, Acceptors, Classifiers and Sequencers.^{[4]}
Acceptors and recognizers
Fig. 4 Acceptor FSM: parsing the string "nice"
Acceptors (also recognizers and sequence detectors) produce a binary output, saying either yes or no to answer whether the input is accepted by the machine or not. All states of the FSM are said to be either accepting or not accepting. At the time when all input is processed, if the current state is an accepting state, the input is accepted; otherwise it is rejected. As a rule the input are symbols (characters); actions are not used. The example in figure 4 shows a finite state machine that accepts the string "nice". In this FSM the only accepting state is number 7.
The machine can also be described as defining a language, which would contain every string accepted by the machine but none of the rejected ones; we say then that the language is accepted by the machine. By definition, the languages accepted by FSMs are the regular languages—that is, a language is regular if there is some FSM that accepts it.
The problem of determining the language accepted by a given FSA is an instance of the algebraic path problem—itself a generalization of the shortest path problem to graphs with edges weighted by the elements of an (arbitrary) semiring.^{[5]}^{[6]}^{[7]}
Start state
The start state is usually shown drawn with an arrow "pointing at it from any where" (Sipser (2006) p. 34).
Accept (or final) states
Fig. 5: Representation of a finitestate machine; this example shows one that determines whether a binary number has an even number of 0s, whereS_1 is an accepting state.
Accept states (also referred to as accepting or final states) are those at which the machine reports that the input string, as processed so far, is a member of the language it accepts. It is usually represented by a double circle.
The start state can also be an accepting state, in which case the automaton accepts the empty string. If the start state is not an accepting state and there are no connecting edges to any of the accepting states, then the automaton is accepting nothing.
An example of an accepting state appears in Fig.5: a deterministic finite automaton (DFA) that detects whether the binary input string contains an even number of 0s.
S_{1} (which is also the start state) indicates the state at which an even number of 0s has been input. S_{1} is therefore an accepting state. This machine will finish in an accept state, if the binary string contains an even number of 0s (including any binary string containing no 0s). Examples of strings accepted by this DFA are ε (the empty string), 1, 11, 11…, 00, 010, 1010, 10110, etc…
Classifier is a generalization that, similar to acceptor, produces single output when terminates but has more than two terminal states.
Transducers
Fig. 6 Transducer FSM: Moore model example
Transducers generate output based on a given input and/or a state using actions. They are used for control applications and in the field of computational linguistics.
In control applications, two types are distinguished:

Moore machine

The FSM uses only entry actions, i.e., output depends only on the state. The advantage of the Moore model is a simplification of the behaviour. Consider an elevator door. The state machine recognizes two commands: "command_open" and "command_close", which trigger state changes. The entry action (E:) in state "Opening" starts a motor opening the door, the entry action in state "Closing" starts a motor in the other direction closing the door. States "Opened" and "Closed" stop the motor when fully opened or closed. They signal to the outside world (e.g., to other state machines) the situation: "door is open" or "door is closed".
Fig. 7 Transducer FSM: Mealy model example

Mealy machine

The FSM uses only input actions, i.e., output depends on input and state. The use of a Mealy FSM leads often to a reduction of the number of states. The example in figure 7 shows a Mealy FSM implementing the same behaviour as in the Moore example (the behaviour depends on the implemented FSM execution model and will work, e.g., for virtual FSM but not for event driven FSM). There are two input actions (I:): "start motor to close the door if command_close arrives" and "start motor in the other direction to open the door if command_open arrives". The "opening" and "closing" intermediate states are not shown.
Generators
The sequencers or generators are a subclass of aforementioned types that have a singleletter input alphabet. They produce only one sequence, which can be interpreted as output sequence of transducer or classifier outputs.
Determinism
A further distinction is between deterministic (DFA) and nondeterministic (NFA, GNFA) automata. In deterministic automata, every state has exactly one transition for each possible input. In nondeterministic automata, an input can lead to one, more than one or no transition for a given state. This distinction is relevant in practice, but not in theory, as there exists an algorithm (the powerset construction) that can transform any NFA into a more complex DFA with identical functionality.
The FSM with only one state is called a combinatorial FSM and uses only input actions. This concept is useful in cases where a number of FSM are required to work together, and where it is convenient to consider a purely combinatorial part as a form of FSM to suit the design tools.^{[8]}
Alternative semantics
There are other sets of semantics available to represent state machines. For example, there are tools for modeling and designing logic for embedded controllers.^{[9]} They combine hierarchical state machines, flow graphs, and truth tables into one language, resulting in a different formalism and set of semantics.^{[10]} Figure 8 illustrates this mix of state machines and flow graphs with a set of states to represent the state of a stopwatch and a flow graph to control the ticks of the watch. These charts, like Harel's original state machines,^{[11]} support hierarchically nested states, orthogonal regions, state actions, and transition actions.^{[12]}
FSM logic
Fig. 8 FSM Logic (Mealy)
The next state and output of an FSM is a function of the input and of the current state. The FSM logic is shown in Figure 8.
Mathematical model
In accordance with the general classification, the following formal definitions are found:

A deterministic finite state machine or acceptor deterministic finite state machine is a quintuple (\Sigma, S, s_0, \delta, F), where:

\Sigma is the input alphabet (a finite, nonempty set of symbols).

S is a finite, nonempty set of states.

s_0 is an initial state, an element of S.

\delta is the statetransition function: \delta: S \times \Sigma \rightarrow S (in a nondeterministic finite automaton it would be \delta: S \times \Sigma \rightarrow \mathcal{P}(S), i.e., \delta would return a set of states).

F is the set of final states, a (possibly empty) subset of S.
For both deterministic and nondeterministic FSMs, it is conventional to allow \delta to be a partial function, i.e. \delta(q,x) does not have to be defined for every combination of q \isin S and x \isin \Sigma. If an FSM M is in a state q, the next symbol is x and \delta(q,x) is not defined, then M can announce an error (i.e. reject the input). This is useful in definitions of general state machines, but less useful when transforming the machine. Some algorithms in their default form may require total functions.
A finitestate machine is a restricted Turing machine where the head can only perform "read" operations, and always moves from left to right.^{[13]}

A finite state transducer is a sextuple (\Sigma, \Gamma, S, s_0, \delta, \omega), where:

\Sigma is the input alphabet (a finite nonempty set of symbols).

\Gamma is the output alphabet (a finite, nonempty set of symbols).

S is a finite, nonempty set of states.

s_0 is the initial state, an element of S. In a nondeterministic finite automaton, s_0 is a set of initial states.

\delta is the statetransition function: \delta: S \times \Sigma \rightarrow S.

\omega is the output function.
If the output function is a function of a state and input alphabet (\omega: S \times \Sigma \rightarrow \Gamma) that definition corresponds to the Mealy model, and can be modelled as a Mealy machine. If the output function depends only on a state (\omega: S \rightarrow \Gamma) that definition corresponds to the Moore model, and can be modelled as a Moore machine. A finitestate machine with no output function at all is known as a semiautomaton or transition system.
If we disregard the first output symbol of a Moore machine, \omega (s_0), then it can be readily converted to an outputequivalent Mealy machine by setting the output function of every Mealy transition (i.e. labeling every edge) with the output symbol given of the destination Moore state. The converse transformation is less straightforward because a Mealy machine state may have different output labels on its incoming transitions (edges). Every such state needs to be split in multiple Moore machine states, one for every incident output symbol.^{[14]}
Optimization
Optimizing an FSM means finding the machine with the minimum number of states that performs the same function. The fastest known algorithm doing this is the Hopcroft minimization algorithm.^{[15]}^{[16]} Other techniques include using an implication table, or the Moore reduction procedure. Additionally, acyclic FSAs can be minimized in linear time.^{[17]}
Implementation
Hardware applications
In a digital circuit, an FSM may be built using a programmable logic device, a programmable logic controller, logic gates and flip flops or relays. More specifically, a hardware implementation requires a register to store state variables, a block of combinational logic that determines the state transition, and a second block of combinational logic that determines the output of an FSM. One of the classic hardware implementations is the Richards controller.
A particular case of Moore FSM, when output is directly connected to the state flipflops, that is when output function is simple identity, is known as Medvedev FSM.^{[18]} It is advised in chip design that no logic is placed between primary I/O and registers to minimize interchip delays, which are usually long and limit the FSM frequencies.
Through state encoding for low power state machines may be optimized to minimize power consumption.
Software applications
The following concepts are commonly used to build software applications with finite state machines:
Finite automata and compilers
Finite automata are often used in the frontend of programming language compilers. Such a frontend may comprise several finite state machines that implement a lexical analyzer and a parser. Starting from a sequence of characters, the lexical analyzer builds a sequence of language tokens (such as reserved words, literals, and identifiers) from which the parser builds a syntax tree. The lexical analyzer and the parser handle the regular and contextfree parts of the programming language's grammar.^{[19]}
See also
References

^

^ ^{a} ^{b}

^

^

^

^

^ http://www.iam.unibe.ch/~run/talks/20080605BernJonczy.pdf p. 34

^ Brutscheck, M., Berger, S., Franke, M., Schwarzbacher, A., Becker, S.: Structural Division Procedure for Efficient IC Analysis. IET Irish Signals and Systems Conference, (ISSC 2008), pp.1823. Galway, Ireland, 18–19 June 2008. [1]

^ Tiwari, A. (2002). Formal Semantics and Analysis Methods for Simulink Stateflow Models.

^

^ Harel, D. (1987). A Visual Formalism for Complex Systems. Science of Computer Programming , 231–274.

^ Alur, R., Kanade, A., Ramesh, S., & Shashidhar, K. C. (2008). Symbolic analysis for improving simulation coverage of Simulink/Stateflow models. International Conference on Embedded Software (pp. 89–98). Atlanta, GA: ACM.

^

^

^

^

^

^

^
Further reading
General


Wagner, F., "Modeling Software with Finite State Machines: A Practical Approach", Auerbach Publications, 2006, ISBN 0849380863.

ITUT, Recommendation Z.100 Specification and Description Language (SDL)

Samek, M., Practical Statecharts in C/C++, CMP Books, 2002, ISBN 1578201101.

Samek, M., Practical UML Statecharts in C/C++, 2nd Edition, Newnes, 2008, ISBN 0750687061.

Gardner, T., Advanced State Management, 2007

Cassandras, C., Lafortune, S., "Introduction to Discrete Event Systems". Kluwer, 1999, ISBN 0792386094.

Timothy Kam, Synthesis of Finite State Machines: Functional Optimization. Kluwer Academic Publishers, Boston 1997, ISBN 0792398424

Tiziano Villa, Synthesis of Finite State Machines: Logic Optimization. Kluwer Academic Publishers, Boston 1997, ISBN 0792398920

Carroll, J., Long, D., Theory of Finite Automata with an Introduction to Formal Languages. Prentice Hall, Englewood Cliffs, 1989.

Kohavi, Z., Switching and Finite Automata Theory. McGrawHill, 1978.

Gill, A., Introduction to the Theory of Finitestate Machines. McGrawHill, 1962.

Ginsburg, S., An Introduction to Mathematical Machine Theory. AddisonWesley, 1962.
Finite state machines (automata theory) in theoretical computer science
Abstract state machines in theoretical computer science
Machine learning using finitestate algorithms
Hardware engineering: state minimization and synthesis of sequential circuits
Finite Markov chain processes


"We may think of a Markov chain as a process that moves successively through a set of states s_{1}, s_{2}, …, s_{r}. … if it is in state s_{i} it moves on to the next stop to state s_{j} with probability p_{ij}. These probabilities can be exhibited in the form of a transition matrix" (Kemeny (1959), p. 384)
Finite Markovchain processes are also known as subshifts of finite type.


Chapter 6 "Finite Markov Chains".
External links

Finite State Automata at DMOZ

Modeling a Simple AI behavior using a Finite State Machine Example of usage in Video Games

Free OnLine Dictionary of Computing description of Finite State Machines

NIST Dictionary of Algorithms and Data Structures description of Finite State Machines

Interactive FSM: Control Circuit, demonstrates the logic flow of the Finite State Machines.

FSM simulator, simulates DFAs, NFAs and εNFAs, including generated by regular expression.




Each category of languages, except those marked by a ^{*}, is a proper subset of the category directly above it. Any language in each category is generated by a grammar and by an automaton in the category in the same line.




Components



Theory



Applications



Related



This article was sourced from Creative Commons AttributionShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, EGovernment Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a nonprofit organization.