Lab#6 - lab6 PDF

Title Lab#6 - lab6
Author 奇 尹
Course Introduction to Computer Science II
Institution University of Delaware
Pages 2
File Size 99 KB
File Type PDF
Total Downloads 20
Total Views 140

Summary

lab6...


Description

Assignment Assigned Date Date Due Late Date

Lab #6 11/29/2020 12/10/2020 12/10/2020

Game theory with Java Sudoku The github with the solution from Lab #5, and with extra code (helper stuff) for Lab #6 can be found here: https://github.com/CISC181/SudokuLab6Starter Tasks for Lab #6: 1. Add MaxMistakes as an attribute of the eGameDifficulty. Give the EASY 5 chances, MEDIUM 4 chances and HARD 3 chances. 2. Keep track of mistakes made in the solving of the Sudoku. This is a new attribute in the Sudoku class. Expose a getter and a method to enumerate the mistakes. The number of mistakes should be set to zero when the Sudoku is constructed. 3. As a player makes a mistake (drops a cell that doesn’t work, violates a rule), increment the number of mistakes. If they reach the max mistakes, the game is over… they lost. 4. As the puzzle is being solved, keep track of the number of zeros remaining in the puzzle. Once the number of zeros is zero, the puzzle is either solved, or not solved. If it is solved, show a message that it’s solved. 5. Give the users the ability to Undo and Redo their moves. Undo/Redo will be implemented in the Sudoku class as stacks. As a move is made, push to the Undo stack and clear the Redo stack. If Undo button is clicked, pop the value from the Undo stack, push it to the Redo stack and implement the move. If Redo is clicked, pop it from the Redo stack and implement the move.

Here’s a view of the class diagram… without attributes / methods

Assignment Assigned Date Date Due Late Date

Lab #6 11/29/2020 12/10/2020 12/10/2020

Deliverables:  

Simple Java Project built on JDK version 1.14. Completed code for Sudoku, including unit tests.

Grading – general guidelines/rubric Exemplary Completed on time. Timeliness (25%)

Developing More than 1 day, less than one week late.

Oh, come on! More than 1 week late, less than 2 weeks late. More than 2 weeks late – no submission possible. 0 points

Knowledge of Content (40%)

25 points

10 points.

Lab completed the bulleted deliverables, all functionality implemented, program(s) works as it should

Missed one deliverable

Missed more than one deliverable

Example:  Used JDK 1.7 instead of JDK 1.8  Missed JUnit test case(s)

Coding- Design or Runtime errors

40 points No errors, program compiles and executes as expected

20-35 points No more than two errors

0 – 20 points More than two errors

(35%)

35 points

20-35 points

0-20 points...


Similar Free PDFs