CS475: Computer Networks - Finite State Machine (100 Points)

Assignment Goals

The goals of this assignment are:
  1. To implement a finite state machine as a loop with a conditional
  2. To relate state machines to network protocols

The Assignment

Write a program that asks the user to type either a letter A or a letter B, in a loop. They may type any other letter when finished. You are to determine whether the number of A and B characters entered are each odd (for example, 1 A and 3 B characters). However, you may not count the characters directly. Instead, you have a single variable called state which you may set to an integer from 0 through 3. Here are the rules for this variable:

  • Let 0 represent that the number of A and B characters are each even.
  • Let 1 represent that the number of A characters is odd while the number of B characters is even.
  • Let 2 represent that the number of A characters is even while the number of B characters is odd.
  • Let 3 represent that the number of A and B characters are each odd.

Implement this program with a loop and a conditional that checks the input character and the current state value, setting the new state value appropriately each time through the loop.

Then, draw a diagram representing these states, and from each state, draw an arrow labeled A and one labeled B to the appropriate next state that you wrote in your program.

When finished, implement a socket program that sends these characters one at a time to a server, who responds with the current state number reached by reading this character.

Submission

In your submission, please include answers to any questions asked on the assignment page in your README file. If you wrote code as part of this assignment, please describe your design, approach, and implementation in your README file as well. Finally, include answers to the following questions:
  • Describe what you did, how you did it, what challenges you encountered, and how you solved them.
  • Please answer any questions found throughout the narrative of this assignment.
  • If collaboration with a buddy was permitted, did you work with a buddy on this assignment? If so, who? If not, do you certify that this submission represents your own original work?
  • Please identify any and all portions of your submission that were not originally written by you (for example, code originally written by your buddy, or anything taken or adapted from a non-classroom resource). It is always OK to use your textbook and instructor notes; however, you are certifying that any portions not designated as coming from an outside person or source are your own original work.
  • Approximately how many hours it took you to finish this assignment (I will not judge you for this at all...I am simply using it to gauge if the assignments are too easy or hard)?
  • Your overall impression of the assignment. Did you love it, hate it, or were you neutral? One word answers are fine, but if you have any suggestions for the future let me know.
  • Using the grading specifications on this page, discuss briefly the grade you would give yourself and why. Discuss each item in the grading specification.
  • Any other concerns that you have. For instance, if you have a bug that you were unable to solve but you made progress, write that here. The more you articulate the problem the more partial credit you will receive (it is fine to leave this blank).

Assignment Rubric

Description Pre-Emerging (< 50%) Beginning (50%) Progressing (85%) Proficient (100%)
Algorithm Implementation (60%) The algorithm fails on the test inputs due to major issues, or the program fails to compile and/or run The algorithm fails on the test inputs due to one or more minor issues The algorithm is implemented to solve the problem correctly according to given test inputs, but would fail if executed in a general case due to a minor issue or omission in the algorithm design or implementation A reasonable algorithm is implemented to solve the problem which correctly solves the problem according to the given test inputs, and would be reasonably expected to solve the problem in the general case
Code Quality and Documentation (30%) Code commenting and structure are absent, or code structure departs significantly from best practice, and/or the code departs significantly from the style guide Code commenting and structure is limited in ways that reduce the readability of the program, and/or there are minor departures from the style guide Code documentation is present that re-states the explicit code definitions, and/or code is written that mostly adheres to the style guide Code is documented at non-trivial points in a manner that enhances the readability of the program, and code is written according to the style guide
Writeup and Submission (10%) An incomplete submission is provided The program is submitted, but not according to the directions in one or more ways (for example, because it is lacking a readme writeup) The program is submitted according to the directions with a minor omission or correction needed The program is submitted according to the directions, including a readme writeup describing the solution

Please refer to the Style Guide for code quality examples and guidelines.