Due to the remote learning, and that we are no longer having an exam, I have had to change the weighting of the different components of the course for the June report card. It has been updated on the Class Policies link on the course web site. I will list the weightings here well:
Tests 63% Assignments 27% Summative 10%The summative assignment will be done in pairs. You will design your own Turing game. It can be a board game, a card game, a video game, a party game… whatever kind of game you like. The key thing is that you must invent it. You can’t just copy a game already out there.
The game doesn’t have to be revolutionary. For example, a relatively complex board game might be one in which there are 12 squares, 2 playing pieces, and two dice. The playing pieces move around the board by rolling the dice. Each time they roll a 2 or a 12, or when they land on one of the 3 yellow squares on the board, they score a point. The first player to score 12 points and then pass the starting square wins. Maybe this game would be called (not very creatively, admittedly) High, Low, Yellow.
Extra marks will be given for complexity and creativity. In terms of complexity, at minimum, your game must have at least one nested loop and three if statements.
There are two parts to the assignment: coding the game and documenting the game. The two partners can choose to share marks for both parts, or to have one partner do the coding and receive marks for that part, and the other partner do the documentation and receive marks for that part. If you have not been able to program in Turing at home, then make sure your partner can.
Documentation includes commenting all the code, writing a user manual about how to play the game and navigate your program, designing a game name and logo, and writing a short and fun biography of the two partners for inclusion at the end of the user manual.
Marking Scheme
Coding /25 Game has the minimum complexity (one nested loop and three ifs) /10 Game functions properly without any bugs /5 Good indentation, code spacing/blocking, and variable names /5 Additional complexity and creativity in game design /5 Documentation /25 Clear, explanatory comments for code blocks, variables, and key lines /10 User manual is clear, concise, and covers all game functionality /10 Creativity in game name, logo, and creator biographies /5