Additions:
There actually used to be something useful here, but I decided it wasn't worth it. Instead, look at this crap!
Deletions:
B142L – Intro to Computing
Coursework 1 – due
07/12/2008
20 Questions Game
Tasklist
1. Part 1: Guess a number – due
26/10/2008
a. Pseudocode for “Guess a number”.
b. Flowchart for “Guess a number”.
c. Working code for “Guess a number”.
2. Part 2: Guess a word – due
09/11/2008
a. Pseudocode for “Guess a word”.
b. Flowchart for “Guess a word”.
c. Working code for “Guess a word”.
3. Part 3: Guess an animal – due
23/11/2008
a. Pseudocode for “Guess an animal”.
b. Flowchart for “Guess an animal”. (
This still needs to be uploaded to CodeWiki and Mosaic∞)
c. Working code for “Guess an animal”.
4. Final project: Guess an animal - due
07/12/2008
a. Clean/friendly UI
i. Menu-based or
ii. ANSI-based that should:
1. Allow (re-)start/quit of game.
2. Display questions & allow selection of answer.
3. At the end of the game, display:
a. Number of questions aksed
b. Time elapsed for the game
c. Same records for previous games
b. Anti-cheating mechanisms
c. Clean error/exception handling
d. Use an algorithm to:
i. Generate questions
ii. Make guesses – at least 30 animals in 20 questions
iii. Decide to end the game
e. Documentation
i. Inline comments that indicate entire solution.
ii. User’s guide
iii. Written description of solution used.
iv. Flowchart of solution used.
Additions:
a. Pseudocode for “Guess an animal”.
b. Flowchart for “Guess an animal”. (
This still needs to be uploaded to CodeWiki and Mosaic∞)
Deletions:
a. Pseudocode for “Guess an animal”.
b. Flowchart for “Guess an animal”.
Additions:
a. Pseudocode for “Guess a number”.
c. Working code for “Guess a number”.
a. Pseudocode for “Guess a word”.
Deletions:
a. Pseudocode for “Guess a number”.
c. Working code for “Guess a number”.
a. Pseudocode for “Guess a word”.
Additions:
Deletions:
Additions:
Deletions:
B142L – Intro to Computing
Coursework 1 – due
07/12/2008
20 Questions Game
Tasklist
Information:
http://cnfolio.com/B142LCW20081207∞
1. Part 1: Guess a number – due
26/10/2008
a. Pseudocode for “Guess a number”.
b. Flowchart for “Guess a number”.
c. Working code for “Guess a number”.
2. Part 2: Guess a word – due
09/11/2008
a. Pseudocode for “Guess a word”.
b. Flowchart for “Guess a word”.
c. Working code for “Guess a word”.
3. Part 3: Guess an animal – due
23/11/2008
a. Pseudocode for “Guess an animal”.
b. Flowchart for “Guess an animal”.
c. Working code for “Guess an animal”.
4. Final project: Guess an animal - due
07/12/2008
a. Clean/friendly UI
i. Menu-based or
ii. ANSI-based that should:
1. Allow (re-)start/quit of game.
2. Display questions & allow selection of answer.
3. At the end of the game, display:
a. Number of questions aksed
b. Time elapsed for the game
c. Same records for previous games
b. Anti-cheating mechanisms
c. Clean error/exception handling
d. Use an algorithm to:
i. Generate questions
ii. Make guesses – at least 30 animals in 20 questions
iii. Decide to end the game
e. Documentation
i. Inline comments that indicate entire solution.
ii. User’s guide
iii. Written description of solution used.
iv. Flowchart of solution used.