Tic tac toe: Difference between revisions
Mr. MacKenty (talk | contribs) (Created page with "right|frame|This a problem set for you to work through <ref>http://www.flaticon.com/</ref> This is a problem set. Some of these are easy, others are far m...") |
Mr. MacKenty (talk | contribs) |
||
Line 16: | Line 16: | ||
# it must allow a human to play against a computer a game of tic tac toe | # it must allow a human to play against a computer a game of tic tac toe | ||
# it must draw a tic tac to board, updated with x's and O's as the computer and human play. | ## your program must have win and lose conditions | ||
# it must draw a tic tac to board, updated with x's and O's as the computer and human play. | |||
# It must follow the rules of tic tac toe | |||
== Hacker edition == | == Hacker edition == |
Revision as of 09:40, 5 September 2018
This is a problem set. Some of these are easy, others are far more difficult. The purpose of these problems sets are:
- to build your skill applying computational thinking to a problem
- to assess your knowledge and skills of different programming practices
What is this problem set trying to do[edit]
This problem set is testing your computational thinking, your skill and understanding of lists, and your skill and understanding of loops
The Problem[edit]
Your program must do three things:
- it must allow a human to play against a computer a game of tic tac toe
- your program must have win and lose conditions
- it must draw a tic tac to board, updated with x's and O's as the computer and human play.
- It must follow the rules of tic tac toe
Hacker edition[edit]
In the hacker version:
- Your program should be good at playing tic tac toe
How you will be assessed[edit]
Your solution will be graded using the following axis:
Scope
- To what extent does your code implement the features required by our specification?
- To what extent is there evidence of effort?
Correctness
- To what extent did your code meet specifications?
- To what extent did your code meet unit tests?
- To what extent is your code free of bugs?
Design
- To what extent is your code written well (i.e. clearly, efficiently, elegantly, and/or logically)?
- To what extent is your code eliminating repetition?
- To what extent is your code using functions appropriately?
Style
- To what extent is your code readable?
- To what extent is your code commented?
- To what extent are your variables well named?
- To what extent do you adhere to style guide?
References[edit]
A possible solution[edit]
Click the expand link to see one possible solution, but NOT before you have tried and failed!
not yet!