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

From CDOT Wiki
Jump to: navigation, search
(Week 4)
(Week 5)
Line 20: Line 20:
  
 
*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).
 +
**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.
  
 
== Week 6 ==
 
== Week 6 ==

Revision as of 19:44, 5 September 2013

Week 1

Week 2

Week 3

  • Work on A1 as a team! The due date is approaching...
  • Update Weekly BUG REPORTS.
  • Do Workshop 2.
  • Do READING on the BTP300 course website.

Week 4

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

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.

Week 6

  • Continue working on Assignment 2 Release 0.2
  • The workshop on Templates will be due Oct. 28 (the end of Study Week).
  • Due date for R02 and R03 is extended
    • BOTH Releases 0.2 and 0.3 will be due on Nov. 11.
    • If you can deliver both Release 0.2 and Release 0.3 before Nov. 11, I will award bonus points.

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 Release 0.2 and 0.3, submission due date is Sunday Nov. 11 23:55

Week 9

Week 10

Week 11

Week 12