The following schedule gives approximate deadlines for the key elements of the senior project. The months below illustrate the typical Fall–Spring track. Report milestone deadlines are defined on the report page by week of classes rather than by calendar date, so that students on an alternative track (e.g., Spring–Fall) can follow the same sequence relative to their own start. Treat the week numbers below as the definition and the months as approximate; work with your advisor and the senior project coordinator to map these weeks onto your calendar.
| Semester | Due Date | Milestones |
|---|---|---|
| Spring (junior year) |
Registration |
Register for CS/DATA 396 for the fall semester. Begin the process of choosing a project and a project advisor. See the list of possible projects for next year and begin a discussion with the faculty project advisor specified there. CS/DATA 396/398 is a two-semester, Fall-Spring course. Alterations to this schedule are rare but possible; see the policies page for details. |
| Fall (CS/DATA 396) |
September |
September 1: Logistics and project matchmaking (all-hands meeting, 7pm, SB 382). Teams should be formed and projects identified. Students who have not found a team by this point will be assigned to one. Post on the Intros and Matchmaking forum before this meeting. September 8: Project visioning (all-hands meeting, 7pm, SB 382). Come prepared to give a 1-minute "elevator pitch" of what you're doing and why it matters. Form a team and find a project advisor by this date. Draft Milestone 1 of the report and discuss it with your project advisor. Milestone 1 is due at the end of Week 4 (submit on Moodle). |
| October |
October 6: Project check-in (all-hands meeting, 7pm, SB 382). Be prepared to share your progress and any challenges you're facing. Submit Milestone 2 at the end of Week 8 (on Moodle). Register for CS/DATA 398 for the spring semester. |
|
| November |
November 10 or 17: Practice talks (all-hands meeting, 7pm, SB 382). Come prepared to give a practice version of your x95 status presentation. Since these presentations take longer, we'll split over two weeks. Submit Milestone 3 at the end of Week 12 (revisions allowed through the end of finals). |
|
| December |
December 1 (tentative) and 8 (confirmed): Present a mid-project status report presentation in a department seminar. Mid December: Publish a draft project website with supporting materials to the project course coordinator. |
|
| Spring (CS/DATA 398) |
January | Review the project guidelines with your faculty advisor and continue work on your report and implementation. |
| February |
Submit Milestone 4 at the end of Week 4 (on Moodle). |
|
| March |
Submit Milestone 5 at the end of Week 8 (on Moodle). |
|
| April–May |
Submit Milestone 6 at the end of Week 12 (revisions allowed through the end of finals). Mid April: A final project presentation practice session may be scheduled. Be prepared to give a dry-run of your full final presentation to the CS/DATA 398 class. Late April: Present a final project presentation in a department seminar. New for this year (details to be confirmed): CS/DATA 398 teams will also present a poster at the Engineering senior design showcase. You'll need to write a one-page write-up with a team photo for the showcase booklet (due early in the spring semester), a graded poster, and attendance at the showcase itself in business-formal dress (plan to purchase if you don't own any) with a laptop demo at your poster, if applicable. Early May: Submit your final project deliverables to the project course coordinator:
|