Members:
(corresponding)___________________
(other)__________________________________________________
Part 1: ___________/30pts
- Completeness:
You have the right pieces. Remember to build a definition
of "output for input string $w$"
- Correctness:
Definitions make sense. Mathematical notation is used
correctly. Sets vs. tuples vs. strings used appropriately,
etc. Your definition behaves the way I described transducers.
- Presentation:
Clearly and neatly written / typeset. Clearly and concisely
expressed ideas.
Part 2: ___________/30pts
- Correct behavior:
Your transducer should implement the logic of
user-messages and GUI-actions correctly.
- Matches program:
Your program should faithfully implement the behavior
shown in your transducer. Your first draft of the
transducer might not be perfect - if as you debug your
program, you realize the transducer didn't deal with
something properly ... fix the transducer as well as the
program. Keep it up to date!
- Presentation:
The drawing of your transducer should be easy to follow
... or as easy to follow as possible, given that there are a
number of states and transitions, so you might have some
ugly crossings of lines.
Part 3: ___________/40pts
- Correctness:
Your program should run the GUI correctly!
- README:
You have a README file as one of your solution files that
includes the names and alphas of your group members,
instructions on how to run your program.
Note: -10 points if this is missing!
- Design:
You should have a well-thought out design for your
program, using all the good stuff you've learned as a CS major.
- Commenting and Formatting:
This should be self-explanatory!
Note: up to 10 points off if you do a poor job at this!