Difference between revisions of "BTP300 To-Do List Fall 2012"

From CDOT Wiki
Jump to: navigation, search
(Week 8)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== Week 1 ==
 
== Week 1 ==
 
* [[BTP300 Workshop 0 | Workshop 0 (Reading & Practice)]] - VERY IMPORTANT!
 
* [[BTP300 Workshop 0 | Workshop 0 (Reading & Practice)]] - VERY IMPORTANT!
* Be ready for doing Pair Programming in the computer lab next Monday!
+
* Be ready for doing Pair Programming in the computer lab.
  
 
== Week 2 ==
 
== Week 2 ==
Line 8: Line 8:
  
 
== Week 3 ==
 
== Week 3 ==
*Work on A1 as a team! The due date is approaching...
+
*Work on A1 as a team of 2 people and put Pair Programming into practice. The due date is approaching...
*Update Weekly BUG REPORTS.
+
**Update Weekly BUG REPORTS.
 
*Do Workshop 2.
 
*Do Workshop 2.
 
*Do READING on the BTP300 course website.
 
*Do READING on the BTP300 course website.
 +
 +
"**THEME OF THIS WEEK**"  "SENECA IS COOL AND THE POSSIBILITIES ARE ENDLESS!"  (posted by the newly famous Jodie Carleton)
  
 
== Week 4 ==
 
== Week 4 ==
 
*Do READING on the BTP300 course website.
 
*Do READING on the BTP300 course website.
 
*Do Workshop 4 first this week, then Workshop 3 for next week(or vice versa).
 
*Do Workshop 4 first this week, then Workshop 3 for next week(or vice versa).
 +
*Update Weekly BUG REPORTS.
  
 
== Week 5 ==
 
== Week 5 ==
  
*Form teams of 4 or 3 (or leave it as it is) and post up you team members on the wiki.
+
*'''Form teams of 4 or 3 (or leave it as it is) and post up you team members on the wiki.'''
*Start working on A2 Release 0.1 (CFrame).
+
*'''Start working on A2 Release 0.1 (CFrame).'''
 
**Read the Practical Tips for A2 Release 0.1.
 
**Read the Practical Tips for A2 Release 0.1.
 
***Run the executable code for A2 Release 0.1 (CFrame).
 
***Run the executable code for A2 Release 0.1 (CFrame).
Line 28: Line 31:
 
== Week 6 ==
 
== Week 6 ==
  
*Continue working on Assignment 2 Release 0.2
+
*Continue working on Assignment 2.
 
+
** Update Weekly BUG REPORTS.
*Prepare for Test 1.
+
*'''Prepare for Test 1.'''
 
**[https://scs.senecac.on.ca/~btp300/pages/practice/oldTests.html  Past Quizzes, Tests, Exams]
 
**[https://scs.senecac.on.ca/~btp300/pages/practice/oldTests.html  Past Quizzes, Tests, Exams]
 
**Practice_Test1_F2012.txt on matrix
 
**Practice_Test1_F2012.txt on matrix
  
 
== Week 7 ==
 
== Week 7 ==
*Submit Assignment 2 Release 0.1
+
*Submit Assignment 2 Release 0.1.
 
*Be ready for Test 1.
 
*Be ready for Test 1.
 
**You may use one reference sheet (2-sided) and the mini-textbook written by Chris Szalwinski for the quiz.
 
**You may use one reference sheet (2-sided) and the mini-textbook written by Chris Szalwinski for the quiz.
Line 53: Line 56:
  
 
== Week 11 ==
 
== Week 11 ==
 +
*Assignment 2 (Release 0.2) due.
  
 
== Week 12 ==
 
== Week 12 ==

Latest revision as of 13:26, 19 September 2013

Week 1

Week 2

Week 3

  • Work on A1 as a team of 2 people and put Pair Programming into practice. The due date is approaching...
    • Update Weekly BUG REPORTS.
  • Do Workshop 2.
  • Do READING on the BTP300 course website.

"**THEME OF THIS WEEK**" "SENECA IS COOL AND THE POSSIBILITIES ARE ENDLESS!" (posted by the newly famous Jodie Carleton)

Week 4

  • Do READING on the BTP300 course website.
  • Do Workshop 4 first this week, then Workshop 3 for next week(or vice versa).
  • Update Weekly BUG REPORTS.

Week 5

  • Form teams of 4 or 3 (or leave it as it is) and post up you team members on the wiki.
  • Start working on A2 Release 0.1 (CFrame).
    • Read the Practical Tips for A2 Release 0.1.
      • Run the executable code for A2 Release 0.1 (CFrame).
      • Inspect the source code of testFrame() in a2test.cpp.
      • Learn how to use the SVN tool.

Week 6

  • Continue working on Assignment 2.
    • Update Weekly BUG REPORTS.
  • Prepare for Test 1.

Week 7

  • Submit Assignment 2 Release 0.1.
  • Be ready for Test 1.
    • You may use one reference sheet (2-sided) and the mini-textbook written by Chris Szalwinski for the quiz.

Study Week

Week 8

  • Continue working on Assignment 2.
  • Update Weekly BUG REPORTS.

Week 9

Week 10

Week 11

  • Assignment 2 (Release 0.2) due.

Week 12