Difference between revisions of "Cipher cracking 2010 weekly progress"

From Derek
Jump to: navigation, search
(Weekly progress and questions)
(Kevin)
Line 57: Line 57:
 
====Kevin====
 
====Kevin====
 
=====This Week=====
 
=====This Week=====
#.  
+
#. Started writing up my sections of the Stage 1 Design Document.
 +
#. Got a few random letter surveys done. Not really sure if they were that intoxicated though ;(.
 +
#. Looked through the java code from last year's project. Fairly certain the code is working correctly and we get the same outputs.
 +
#. Drew up an initial flow chart of what we think the web crawler code should do.
 
=====Next Week Plan=====
 
=====Next Week Plan=====
#.  
+
#. Finish the Stage 1 Design Document.
 +
#. Finishing touches on confirming last year's results if needed.
 +
#. Possibly start initial coding of the Web Crawler if time permits.
  
 
====Michael====
 
====Michael====

Revision as of 17:13, 28 March 2010

Weekly progress and questions

This is where you record your progress and ask questions. Make sure you update this every week. The deadline is every Friday evening. However, if you sometimes slip a little into the weekend (so long as you don't do it too often) we won't be too hard on your marks.

Please remember that we make use of this progress section to give you your project mark. Your mark will suffer if you don't complete this section.

Semester 1 Week 1

Kevin

This Week
  1. . Had initial group meeting.
  2. . Researched background of the case using Wikipedia and looking at the work from last years project.

Michael

This Week
  1. . Had introduction meeting with project coordinators and Kevin.
  2. . Researched basic case background and ciphers.

Semester 1 Week 2

Kevin

This Week
  1. . Looked into different web crawlers that we could use for our project.
  2. . Started working on Proposal Seminar.
  3. . Bought Secrets of Codes book to help with Proposal Seminar.

Michael

This Week
  1. . Developed a rough project breakdown structure.
  2. . Began compiling information on some available web crawling devices.
  3. . Constructed a basic outline for the proposal seminar.

Semester 1 Week 3

Kevin

This Week
  1. . Had our Proposal Seminar presentation.
  2. . Started to verify the past years results. Started to carefully look at the java code from the previous project group.
Next Week Plan
  1. . Survey several people while drunk/not drunk for random letters.
  2. . Finish or almost finish verifying past year results. Check if we come to the same conclusions.
  3. . Brush up on java writing skills.

Michael

This Week
  1. . Converted the work breakdown structured into a Gantt Chart.
  2. . Completed the Proposal Seminar and presented it on Wednesday.
  3. . Drew up a survey sheet for recording 45 random letters to be taken from a variety of subjects.
  4. . Started collecting random letter samples to explore the theory that the code is just a sequence of random letters.
Next Week Plan
  1. . Complete the collection of random letter samples (intoxicated samples will most likely have to wait until the following weekend :D)
  2. . Draw up an outline for the stage 1 design document.
  3. . Continue researching available web crawlers and hopefully come to a conclusion on one that will be most useful for the project.

Semester 1 Week 4

Kevin

This Week
  1. . Started writing up my sections of the Stage 1 Design Document.
  2. . Got a few random letter surveys done. Not really sure if they were that intoxicated though ;(.
  3. . Looked through the java code from last year's project. Fairly certain the code is working correctly and we get the same outputs.
  4. . Drew up an initial flow chart of what we think the web crawler code should do.
Next Week Plan
  1. . Finish the Stage 1 Design Document.
  2. . Finishing touches on confirming last year's results if needed.
  3. . Possibly start initial coding of the Web Crawler if time permits.

Michael

This Week
  1. .
Next Week Plan
  1. .