A deterministic finite automaton (DFA) is an abstract machine that reads input from a serial (nonreversible) stream and changes between a finite number of  states according to the current state and the current input.  When the input stream is exhausted the final state of the machine is used to draw some general conclusion about the input string.  There is usually one state that indicates the input string was accepted (according to some criterion), and any other final state may indicate that the string was rejected.  In Computer Science these concepts are applied in areas such as determining whether some input meets the grammar rules of a programming language.  When a DFA is enhanced with the ability to move backwards and forwards over the stream and to overwrite the input symbols with output symbols it is called a standard Turing machine, which provides an important theoretical model for what it means to "compute."  Turing machines appear prominently in decidability theory, which is the study of problems that can and cannot be solved with computers.  I hope you are aware that there are fairly straightforward problems that can be proven to be unsolvable by computers.  Some of these proofs are surprisingly simple as long as you think recursively.  If you were not aware of this, I encourage you to do some reading about the Halting Problem.

Your course project is to create a puzzle-solving game that provides animation of deterministic finite automata.  I call this game Robot Factory, and it is modeled after an online Flash game called Manufactoria which in turn was inspired by Zachtronic's Games for Engineers.  The general idea is that Robots emerge from a source tunnel and follow conveyor belts that are placed by the player.  Each Robot carries a sequential  tape containing red  and blue marks.  When the Robot encounters a switch (also placed by the player), it moves in one of  three directions depending on whether the current mark is red, blue, or the tape has reached the end.  After taking one of those directions, the tape is advanced one position to the next mark.  Each Robot (and tape) represents a test case for a particular Goal that is stated in a message bar just under the Menu Bar. The Goal states conditions under which the Robot should be accepted by moving it to a sink tunnel. A Robot is rejected by directing it onto any blank cell on the game board. Goals are expressed in terms of features of the tape, such as "contains at least two consecutive reds, followed by one and only one blue."  The Goal statements, test tapes, and outcomes will be expressed in text files that are loaded from the File menu.

Following are detailed specifications for the project, along with some hints on how to proceed.  Read the specifications very carefully - each behavior has some points associated with it.  I am also providing the scoring sheet that I will use to grade your project. If you are uncertain about any of the requirements, please ask. I am distributing the project definition early so that you can make incremental progress as you acquire knowledge. I suggest that you get started as soon as possible in order to take maximum advantage of your opportunities to receive my help. Only bad things can come if you wait until the last week of the quarter to get started.  I will provide a 32-bit Windows executable (it is not a class file, so don't waste your time trying to decompile it) of a solution that goes beyond the minimum requirements.  I will also supply you with some GIF files for the playfield elements, but feel free to design your own.  You can use other image formats with Swing - I often use GIF for such things because it allows the specification of transparent pixels.  I offer some ideas for how you might improve the implementation if you are so inclined.  Feel free to pursue those or any other enhancements you think of as long as you don't violate the requirements.  I suggest you start by playing around with my solution, including creating a goal statement and some test cases beyond the ones I provide.  You are not, however, required to provide any test files with your solution.