Program 2

Sample Solutions

There are three sample solutions located in this zipped file.

Lab Partners

Everyone is encouraged to work with one lab partner on this assignment. If you do work with a partner, submit one solution with both of your names on it. Also, please look at the class collaboration policy so that you know what is and what isn't allowed.

Sample Solutions to Program 1

• 8 a.m. section (Tyson Joehler and Aric Walker):
  • Answer.java
  • Display.java
  • Driver.java
  • Guess.java
  • Row.java
  • UserInterface.java
• 10 a.m. section (Nick Lamb and Reid Roper):
  • Answer.java
  • Driver.java
  • Game.java
  • InvalidRangeException.java
  • Mastermind.java
  • Questions.java
  • Row.java
• 1 p.m. section (Andrew Szatkowski):
  • Answer.java
  • Driver.java
  • Mastermind.java
  • NumberOfInputException.java
  • NumberRangeException.java
  • Row.java
  • User.java

  General Overview

  In this assignment, you should add a graphical user interface to one of the Program 1 Mastermind solutions above. If you are in the 8 a.m. lab, you must use the 10 a.m. solution as your starting point. If you are in the 10 a.m. lab, you must use the 1 p.m. solution as your stating point. If you are in the 1 p.m. lab, you must use the 8 a.m. solution as your starting point.

  Rationale

  In the software world, programmers are often given code to modify that they did not write themselves. This assignment will give you this experience, as well as showing you how important it is for the starting code base to be well done. In the future, it is hoped that this experience will further motivate you to produce high quality code that others could easily modify.

  GUI Features

  1. The user can enter his/her name via the GUI.
  2. The user can enter the number of pegs (1 - 8) via the GUI. Erroneous integer inputs should be handled appropriately.
  3. The user can enter the number of colors (1 - 6) via the GUI. Erroneous integer inputs should be handled appropriately.
  4. The user can enter the next guess via the GUI.
  5. The GUI can display a complete history of the current game.
  6. At the end of a game, the GUI displays a message stating whether the user won or lost.
  7. At the end of a game, the GUI displays a message stating the total number of wins and losses for the user.
  8. At the end of a game, the user can decide via the GUI whether to play again or quit.

  Grading

  • 60%. GUI Functionality. Modify the starting code as little as possible.
  • 10%. GUI Aesthetics.
  • 10%. GUI Usability.
  • 20%. Comments, elegant solution, etc. This is with respect to your part of the solution, not the code that you are given as a base.

  What to Submit

  E-mail your code to Mike Thiesen at mthiesen@gmail.com in one message before the due date. The subject of the message should be: CS221-xx program2 your-names. The xx is the number of your lab section. Late programs will not be accepted for credit. If you aren't finished by the deadline, submit whatever you have - partial credit is always possible.