Objective:

Assignment:

• If you look at prog2, there's a main loop which asks the user if they want to keep playing. If they respond with yes, then the contents inside the loop handles the mechanics of playing the mastermind game. Now, if you look at those components, there's a part that deals with generating the code, and another part that deals with scoring the guesses. Each of these parts, can best be broken down into separate methods. Note that you may find another sub-task, e.g. when scoring a guess, that could be in its own method also. Your task for lab2 is to rewrite your prog2 so that it uses methods.

  Specifically, your program must have at least the following two methods:

  // ======================= //
  // returns the secret code //
  // ======================= //
  static  int  generateCode()
  

  and

  // ================================================== //
  // scores the guess. returns true iff code == guess   //
  // ================================================== //
  static  boolean  scoreGuess( int code, int guess )
  

  Optional part: As you are rewriting prog2 to use methods, also think about possibly using arrays as an alternative way of managing and scoring secret codes and guesses.

• The sample runs for your revised program should be the same as the simplified and full versions of prog2.

• Your program should be saved in a file named Mastermind.java or BonusMM.java, just as in prog2.

• Your class should be named Mastermind or BonusMM respectively.

• Make sure your code (and every program that you write) have a comment block in the beginning of the file. Make sure your code is properly formatted and documented (as always).

• Submit your program using the following command on unix.ic.ucsc.edu:

   submit cmps012a-ap.w15 lab3 Mastermind.java
  and/or
   submit cmps012a-ap.w15 lab3 BonusMM.java
  

  Make sure that for this program, and all other programs you write for CMPS 12A this quarter, have been recompiled and tested on unix.ic.ucsc.edu before submission.

• Grading rubrics for lab3:

  100 -- if meets most requirements i.e. compiles/runs,
         has comment block with correct info, code is properly documented/formatted.
  75  -- if missing comment block, or poor formatting, or lack of documentation
  50  -- has submission, but problem with compilation or crashes, empty file,
         wrong filename, wrong class name, doesn't run, requires manual intervention by grader, etc.
         (i.e. compilation or runtime errors)
  50  -- if compiles and runs, but different or wrong sequence of codes / numbers (and answers)
         (i.e. logic errors)
  0   -- no submission
  
  Who Will Grade What:
  --------------------
  Ryan   : aalkahel - dlopez8
  Kara   : dlskilli - jssorens
  Derek  : jtorre34 - romarks
  Eitan  : rpickett - zwang58