Course syllabus‎ > ‎

Schedule and dates

In this section we summarize important semester and course dates.

Overall semester dates

  • Monday, January 6th is the first day of the semester
  • Monday-Friday, February 17th-21st is Reading Week (no classes and labs)
  • Thursday, April 10th is the last day of the semester
  • Friday, April 11th is the final exam

Important ECE 297 dates (labs, tutorials, milestones, design documents, midterm, and final)

Milestone Due dates Deliverable or task
First Lab Week of January 13th Read Milestone 1 description and attend lab section
Team Selection 
(important)
Friday, January 17th
at 5:00 PM
All students have to make a team selection 
(see Team Selection Instructions)
First Tutorial Week of January 20th
Attend the tutorial section assigned to you in ROSI
Milestone 1
Sunday, January 26th at 11:59 PM Code submission Milestone 1 due
Design Document:
Basic Storage Server
Sunday, February 9th at 11:59 PM Design Document: Basic Storage Server due
Milestone 2
Sunday, February 16th at 11:59 PM
Code submission Milestone 2 due
Midterm Week of February 24th 15-20 min Midterm Software Demonstration in laboratory sections (read midterm instructions!)
Design Document: Extended Storage Server Sunday, March 9th at 11:59 PM
Design Document: Extended Storage Server due
Milestone 3
Sunday, March 16th at 11:59 PM Code submission Milestone 3 due
Design Document: Scalable and Concurrent Storage Server Sunday, March 30th at 11:59 PM
Design Document: Scalable and Concurrent Storage Server due
Last Lab Week of March 31st Attend lab and optional Tech talk
Milestone 4
Sunday, April 6th at 11:59 PM Code submission Milestone 4 due
Final Friday, April 11th Final Exam Presentation (read final exam instructions!)

All submission deadlines are 11:59 PM. Specific days are noted in the above table. It is your responsibility to meet all deadlines. Do not wait until the last minute to submit. We will not respond to last minute inquiries regarding late submissions or notifications about barely-missed submission deadlines.

The above table lists three design documents which constitute the written communication about the detailed design of your project milestone as specified in each assigned milestone description. Each design document is to be handed in online, to Turnitin, as a PDF document or Word document. You may select any word-processor, such as Latex or Microsoft Word for producing the PDF or Word document. Your Project Manager may also request a printed copy and will specify whether it is to be submitted at the first lecture or first tutorial, following the 11:59 p.m. deadline.

The text of all design documents must be submitted to Turnitin.com by the 11:59 PM deadlines. The University of Toronto requires that the following notice be included in the syllabus:

   Students will be required to submit their course essays to
   Turnitin.com for a review of textual similarity and detection of
   possible plagiarism. In doing so, students will allow their essays
   to be included as source documents in the Turnitin.com reference
   database, where they will be used solely for the purpose of
   detecting plagiarism. The terms that apply to the University's use
   of the Turnitin.com service are described on the Turnitin.com web
   site.

The code refers to the source code and any additional software artifacts, as specified in the individual milestones.

Note, the dual-deadline model for each milestone. There are two deadlines for each milestone, except the first milestone that only has a code submission deadline and no design document deadline, for a total of 7 deadlines for this course. This is neither counting the Midterm Software Demonstration and the Final Exam Presentation, which are scheduled separately, nor the deadline for Team Selection.

The first deadline for each assigned milestone requires the submission of the design document. The document will form the basis for the discussions in the tutorials with the communication instructors. Also, our intent for having you submit the design document first is to have you think about the design prior to the actual implementation. The second deadline for each milestone requires the submission of the source code.

Detailed submission instructions are provided in each of the four milestone handouts.

back to top