*This half of the theory of computing primer will cover the various finite automata, including deterministic, nondeterministic, and pushdown automata. We devote the second half [upcoming] entirely to Turing machines and the halting problem, but to facilitate the discussion of Turing machines we rely on the intuition and notation developed here.*

## Defining Computation

The first step in studying the sorts of possible computations (and more interestingly, those things which cannot be computed) is to define exactly what we mean by a “computation.” At a high level, this is easy: a computation is simply a function. Given some input, produce the appropriate output.

Unfortunately this is much too general. For instance, we could define almost anything we want in terms of functions. Let be the function which accepts as input the date of California Super Lotto drawings, and returns the set of winning numbers for that date. Of course (assuming the winning numbers are chosen randomly), this is ridiculous and totally uninformative. We cannot learn anything interesting about computations if they are performed behind an opaque veil. Instead, we need to rigorously define the innards of our model for computation, and then see what kinds of things it can do.

Because our inputs may be long and complicated, our model should break an input into pieces and work on the pieces in sequence. This motivates the following two definitions:

**Definition**: An *alphabet* is a finite set, usually denoted .

**Definition**: is the set of finite strings whose characters come from . We include the *empty string* as the string of zero length. This operation is called the *Kleene star*.

We will henceforth let inputs to our model be elements of for some fixed alphabet , and operate on each character one at a time.

Since is finite, we may assign to each element a unique finite string of ones and zeros (to keep things simple, let each string have length equal to ceiling of . Then, we can simulate any alphabet by the appropriate subset of . So without loss of generality, we may always assume our input comes from , and thus we will henceforth have .

Now we need a clear objective for our model, and we will phrase it again in terms of . Specifically, we pick a subset of , and call it a *language*. Our computational model will accept an input, and output “accept” or “reject.” We say that our model *recognizes* if it accepts and only accepts those strings in .

Notice that this is a bit different from our colloquial idea of “computation.” Specifically, all our model will do is determine presence of an element in a set which has a potentially complicated construction. While it at first seems that this does not include things like “adding two numbers,” it turns out that we may phrase such objectives in terms of acceptance and rejection. Let , where is some fixed separator. If we fix and , then we may run our computational model on successively higher values of (ordered by absolute value, or restricting everything to be positive) until finding acceptance.

Colloquially, we have defined “computation” as recognizing all inputs which satisfy a qestion. Moreover, we will see that very many complex problems can be recognized as recognition problems, including things that are logically impossible to compute within our model.

The reason we have been heretofore vague in naming our model is that we will actually define four different models of progressively stronger computational ability, and this framework will hold for all of them. So here our first try.

## Deterministic Finite Automata

This definition comes from the intuitive idea that a computation can be carried out via a set of states and transitions between those states. A very simple example is a light switch, which has the states ‘on’ and ‘off’, and which can accept as input ‘switch’ or ‘do nothing’. This model is rigorized here:

**Definition**: A *deterministic finite automaton*, abbreviated DFA, is a five-tuple , where:

- is a set of states, with initial state .
- is our working alphabet, and inputs come from .
- is a
*transition function*, which maps the current state and next input character to the next appropriate state. - is a set of
*final*states. If the last input character lands us in any state , we accept.

Rigorously, let our input word have length and characters indexed . Call the sequence of states in the computation , where . Then our DFA accepts if and only if . We will use this notation throughout our discussion of finite automata. We call the set of languages which a DFA can recognize the *regular languages*. We will soon see that this class is rather small.

Of course, we have some examples of DFAs. The simplest possible DFA has only one state, , and the transition function for all . Depending on whether is empty, this DFA will accept or reject all of . We may visualize this DFA as a directed graph:

Indeed, this visualization provides a convenient way for us to write out the transition function. We simply draw an edge originating at each state for each element of our alphabet. When two or more inputs have the same behavior, we label one edge with multiple input symbols, as above.

Here is a more interesting example: let be the set of binary strings which have an even number of zeros. We design a DFA to accept this as follows:

The shaded state, is the only final state. It is obvious from tracing the diagram that this DFA accepts precisely the set of strings with evenly many zeros. Let’s try something harder:

Let . This is a simple enough language, so let us develop a DFA to recognize it. We can easily construct a DFA which recognizes for a fixed , and if we have two DFAs we can construct a DFA which recognizes their union quite easily (do so as an exercise!). However, due to the restriction that is finite, we cannot connect these pieces together indefinitely! While we might imagine some cleverly designed DFA exists to recognize , we find it more likely that no such DFA exists.

Indeed, it has been proven that no such DFA exists. The key to the proof lies in an esoteric lemma called the Pumping Lemma. Being a notational beast of a lemma, we will not state it rigorously. Colloquially, the lemma says that if is a regular language, then any sufficiently large word can be split up into three pieces , such that the middle piece may be repeated arbitrarily many times, as , with the resulting word still being in . Clearly this breaks the “balance” restraint of no matter where the splitting is done, and so cannot be regular.

Before we increase our model’s expressive power, let us make an “enhancement” to the DFA.

## Nondeterministic Finite Automata

Following the colloquial definition of nondeterminism, we can design our computational system to make state transitions “branch out.” This will be made clear by a slight modification of the DFA.

**Definition**: A *nondeterministic finite automaton*, abbreviated NFA, is a DFA with the following two modifications:

- Instead of having a single state at each step, we allow a set of possible states, which we denote .
- Our initial state is replaced with an initial set of states .
- We include in , allowing for immediate transitions that require no input.
- The transition function now has signature , where denotes the power set of , the set of all subsets of .
- At each step (with input character ), we map over to get , i.e.
- The NFA accepts if any state in is final.

In this way, our machine can get a character as input, and proceed to be in two separate states at the same time. If any of the branches of computation accept, then they all accept.

Extending our example from DFAs, here is an NFA which accepts the language of binary strings which have either an even number of zeros or an even number of ones (or both).

Here, , and by tracing (a little more carefully this time), we can see that it accepts what we expect.

Now, with the added strength of nondeterminism, we might expect that NFAs can compute some things that DFAs cannot. Amazingly, this is not the case. We point the reader to a more detailed description, but trust that our quick explanation will give the necessary intuition to see the equivalence.

The key observation is that despite nondeterminism, there is still a finite number of possible states an NFA can be in. Specifically, there are at most possible subsets of , so we can simply construct a DFA which has states, one corresponding to each subset of , and build up a deterministic transition function that makes things work. This would be an appropriate exercise for the advanced reader, but the beginning student should see Sisper’s Introduction to the Theory of Computation, which contains a complete and thorough proof. (We hate to refer the reader to an expensive textbook, but we could only find sparse proofs of this equivalence elsewhere on the internet, and most assume a particular working set of notation. And Sisper’s book is much better than this terse post for a primer in Computing Theory. The interested reader who lacks mathematical maturity would find it very accessible.)

In other words, every NFA has a corresponding DFA which recognizes precisely the same language. On the other hand, every DFA is trivially an NFA. Thus, the class of languages which NFAs recognize is also the regular languages.

So we have discovered that regular languages, and hence the DFAs and NFAs which recognize them, are quite limited in expressive power. Now let’s truly beef up our model with some mathematical steroids.

## Pushdown Automata

Okay, so these steroids won’t be that strong. Ideally, we just want to add as little as possible to our model and still make it more expressive. This way we can better understand the nuances of computational power, thus strengthening our intuition. While “little” is a subjective notion, lots of “littler” things were tried before arriving at a model that was not equivalent in power to a DFA. We will refrain from explaining them here, except to say that DFAs are equivalent in power to the class of formal Regular Expressions (hence the name, regular languages), which most programmers are familiar with on an informal level.

**Definition**: A *pushdown automaton*, denoted PDA, is an NFA with two additional components: a set of *stack symbols *including , and a modified transition function :

Here, the left hand symbol represents the current top of the stack (which is always popped), and the right hand represents any modification to the stack during state transition. This modification is always a push, and can be an empty push, or a push of arbitrarily many symbols.

For brevity of a description of , which would otherwise be infinite as there are infinitely many possible stacks, we allow to be a partial function, not defined for some inputs. Then a PDA automatically rejects any encountered undefined input. Alternatively, we could construct as a total function, if we add edges for each undefined input going to some terminal state which is inescapable and not final. For the sake of this post, we will accept a partial transition function.

Recalling our discussion of computational ability in our post on Conway’s Game of Life, we recognize that a PDA’s new power is in its ability to grow without bound. Specifically, the stack has no limit to its size, and we can remember important pieces of input which would otherwise be discarded.

This modification seems like it was made just for the problem. Specifically, now we can just push the 0s we see on to the stack, and pop just 1’s until we see an empty stack. Here is a PDA which does just that (making heavy use of epsilon transitions):

Here , and . For each state transition label, we include to mean, “upon receiving $w_k$ as input with on top of the stack, pop and replace it with , where may be a single character or multiple characters or the empty character. The epsilon transitions allow us to move from to and from to seamlessly, but only when the stack is agreeable. As an exercise, modify the above diagram to instead recognize .

Neato! It seems like we’ve got a huge boost in computational power now that we can store some information. Wrong. As great as a stack is, it’s not good enough. Here’s a language that a PDA cannot solve: . This follows from an additional and more nuanced pumping lemma, and we will not dwell on it here. But look at that! This language is hardly any more complex than , and yet it stumps our PDA.

Time to up the steroid dosage. Surprisingly enough, it turns out that our solution will be equivalent to adding another stack! In doing so, we will achieve a level of computational expression so powerful that nothing we know of today can surpass it. We call this panacea of computational woes a Turing machine, and we will cover both it and the wild problems it cannot compute next time.

Until then!