IBCS1 - 1213 - April

Monday - Tuesday (4/29/13 - 4/30/13)

Agenda:

• Complete Python - Creature Combat Game today
  • Demo CombatSimulation.py by the end of today
  • Mr. Bui will be checking for demos at the beginning of next class
• Toaster Wars - Hacking Competition

Thursday - Friday (4/25/13 - 4/26/13)

Agenda:

• More on the __init__() method
  • Additional parameters
  • Default values for parameters
• Python - Creature Combat Game

Tuesday - Wednesday (4/23/13 - 4/24/13)

Agenda:

• Demo AddressBook
• Basic Requirements (5 points each)
  • Add a contact
  • Find a contact
  • Remove a contact
  • Print all contacts
  • Quit the program
• Advanced Requirements (2.5 points each)
  • Editing a contact
  • Sort the address book

Friday - Monday (4/19/13 - 4/22/13)

Agenda:

• Missing Hangman demos
• Python Classes Review
  • Media:PythonClasses.pptx
• AddressBook Assignment
  • Your program should print out a menu with the following options
  • Add a new contact
    1. Prompt the user for the new contact's name
    2. Prompt the user for the new contact's phone
    3. Add the contact to the address book
  • Find a contact
    1. Prompt the user for the contact's name to find
    2. Use a loop to traverse the address book
    3. If found, print out the contact's full information (name and number)
    4. If the contact is not found, then print "Contact Not found"
  • Remove a contact
    1. Prompt the user for the name of the contact to remove
    2. Use a loop to traverse the address book
    3. If found, delete/remove the contact from the address book
    4. If the contact is not found, then print "Contact Not found"
  • Print out all contacts
    1. User a loop to print out all the contacts in the address book
  • Quit program
• Challenges
  • Add an option to edit a particular contact in the address book
  • Add an option to sort the address book

Monday - Wednesday (4/15/13 - 4/17/13)

Agenda:

• Hangman Live Demos!
  • See Hangman Demonstration rubric
  • 5 points for each basic requirement
  • 1.5 points for each advanced requirement
• Due by the end of Wednesday!

Thursday - Friday (4/11/13 - 4/12/13)

Agenda:

• Work on Hangman code - Hangman is due by the end of the week
  • Live demos will be collected at the beginning of next week
  • Be sure to test your hangman code a lot
• Hangman Game Requirements (at a minimum)
  1. The secret word should be picked randomly from a text file of at least 50 random words (you create the text file)
  2. Player should be allowed to guess a letter
  3. Player is only allowed 7 incorrect guesses (display number of incorrect guesses left every turn)
  4. Correct letters are revealed in the secret word
  5. Incorrect letters are added to an incorrect list
  6. Game over when all letters are revealed correctly or when the player is out of guesses
• Hangman Advanced Requirements
  1. Your game is idiot-proof (i.e. player cannot input invalid keys, numbers, or words unless the word is the solution)
  2. Your game can handle multiple words (i.e. hyphens and spaces are shown automatically)
  3. Your game handles upper and lower case letters the same (i.e. guessing 'a' or 'A' reveals all the upper and lower As)
  4. Print out a fake graphical hangman in the console (Example)
  5. Display a menu at the beginning to allow player to choose a category for the hangman puzzle

Monday - Wednesday (4/8/13 - 4/10/13)

Agenda:

• Print out your Hangman Design (make sure your name is at the top)
• Work on Hangman code - Hangman is due by the end of the week
• Hangman Game Requirements (at a minimum)
  1. The secret word should be picked randomly from a text file of random words (you create the text file)
  2. Player should be allowed to guess a letter
  3. Player is only allowed 7 incorrect guesses (display number of incorrect guesses left every turn)
  4. Correct letters are revealed in the secret word
  5. Incorrect letters are added to an incorrect list
  6. Game over when all letters are revealed correctly or when the player is out of guesses
• Hangman Advanced Requirements
  1. Your game is idiot-proof (i.e. player cannot input invalid keys, numbers, or words unless the word is the solution)
  2. Your game can handle multiple words (i.e. hyphens and spaces are shown automatically)
  3. Your game handles upper and lower case letters the same (i.e. guessing 'a' or 'A' reveals all the upper and lower As)
  4. Print out a fake graphical hangman in the console (Example)

Tuesday - Thursday (4/2/13 - 4/4/13)

Agenda:

• Workshop with a professional programmer - Carney JAMTech
• Return exams
• Review most common uses of major programming concepts
  • types: int, double, string
  • variables
  • functions
  • if-statements
  • while loops
  • lists
• Hangman Game
  1. Review the rules of Hangman
  2. Open a Google Doc and name it Hangman Design
  3. Put your name at the top
  4. Add sub-headings for the following: Variables & Types, Requirements, Design
  5. Under the Variables & Types section, list all the variables that you expect to use and their types (be sure to identify any lists)
  6. Under the Requirements section, list all the rules and requirements for the Hangman game
     • These should be the big picture requirements of how the game works
  7. Under the Design section, write the step-by-step English instructions/pseudocode of your Hangman game
     • This should be the plain language, specific step-by-step instructions of the program (different from rules)
     • You should detail and describe any input or output
     • Be sure to detail what exactly happens in each step (e.g. check each letter of the secret word to see if it matches the guessed letter...)
     • You should include every step from the very beginning when the game starts up until when the game ends
  8. Share the document with Mr. Bui