Description: This was our final project for CS8, and recently we had been learning about Caesar Ciphers and how to decrypt messages which have multi digit keys or how to test through all the words in the alphabet. So for our final project, Ms. Tran made a scavenger hunt for us where we had to track down her cow using 5 clues she provided us, all of which were encrypted.
Procedure:
Clue 1: At the beginning, we were having a tough time getting started. We knew we had to try all 26 options in the alphabet, so we resorted back to the old code. But as we were, we kept encountering problems with the "for n in key". I ended up turning the key into a string and that's how it ended up working. We used "for i in range (1,27)" and inserted the message. This is the code we used to find the answer to the first clue and the remaining three clues.
Clue 2: Using the "for i in range(1,27)" code, we inserted the encrypted message again, and got this message. From this clue we now know that the cow is still at Pinewood, hanging around the Cue Quad, and likes candy.
Clue 3: Using the "for i in range(1,27)" code again, we inserted the encrypted message again, and got this message. From this clue we know that the cow might have also gotten candy from Ms. King or Ms. Sanchez.
Clue 4: Using the "for i in range(1,27)" code again, we inserted the encrypted message again, and got this message. From this clue we guessed that the numbers written on the candy wrapper might have been from the cow, and it would be useful for clue 5.
Clue 5: Now for Clue 5 we used the decrypted message from Clue 4 because we tried inserting it into the "for i in range(1,27)" and it didn't work so we had to try to find another solution. We knew from Clue 4 that we already had 6 digits to the 10 digit key, and inserted numbers until the code actually worked. By the letters we knew were correct we counted how many it was to get to the right letter, and inserted it. This was our final key and message:
Reflection: In this project, I think me and Rebecca work well together. We worked together to debug our code when it didn't work for the first 4 codes, and then she would give me the decrypted code and I would insert it into my program.
S - Strengths: strengths of the Ceasar Cipher, me and Rebecca worked well and efficently together, we both put in the same amount of work and effort.
O - Opportunities: opportunities where we could have improved, at the beginning when we were debugging we took really long, and were behind at first in getting the clues. This possibly gave us a big disadvantage because others had a longer time to inspec the code.
U - Understanding: I used my knowledge on Ciphers and how to decode encrypted messges and encode them in different ways.
L - Limitations: Some limitations we encountered during this project were some bugs in our code. However, we quickly listened to the problem our code was telling us, and fixed it.
WISCR: The two qualities that I believe I demonstrated this project were clear communicators and insight critical thinkers. Me and Rebecca maintained clear communication, and were able to effectly move through Clues 1-4, and we were insightful critical thinkers when debugging our code and inspecting how to solve clue 5.