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:
 
== 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).

Revision as of 20:52, 5 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.

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