Course Notes & More
Deliverables Schedule
| Phase |
Week # |
Dates |
Preliminary Version (Friday Meeting) |
Final Version (Sunday Deadline) |
| Intro |
0 |
March 14 - 16 |
Team Meeting with the TAs |
|
Phase 1 |
1 |
March 20 - 26 |
Requirements / Domain Models |
|
Phase 1 |
2 |
March 27 - April 2 |
Requirements / Domain Models / Design |
Phase 1 - R/M Submission |
Phase 1 |
3 |
April 3 - 9 |
Design |
|
Phase 1 |
4 |
April 10 - 16 |
Design |
Phase 1 - Design Submission |
Phase 1 |
5 |
April 24 - 30 |
Phase 1 - Discussion of Implementation |
|
Phase 1 |
6 |
May 1 - 7 |
Phase 1 Demo |
Phase 1 - Demo Submission |
Phase 2 |
7 |
May 8 - 14 |
Requirements / Domain Models / Design |
|
Phase 2 |
8 |
May 15 - 21 |
Requirements / Domain Models / Design |
Phase 2 - R/M/D Submission + Code Reviews |
Phase 2 |
9 |
May 22 - 28 |
Phase 2 - Testing |
Phase 2 - Testing Submission + Code Reviews |
Phase 2 |
10 |
May 29 - June 4 |
Phase 2 - Discussions |
|
| Final |
11 |
TBA |
Final Demo |
Final Report & Source Code |
Weekly Meetings
Each team will meet with the TA and/or the instructor once a week for 40 minutes. Your preparation and performance at these meetings, along with your timely achievement of project milestones, will determine your grade in this project. It is very important that you come to these meetings well-prepared. For each meeting, the following will be due
- the preliminary or final version of project deliverables
- a written meeting agenda (progress report + meeting plan)
- The meeting agenda should be submitted one day before the meeting. The meeting agenda will be graded. You will get feedback about project deliverables during the meeting. If you can attend the meeting well-prepared, you will get more concrete feedback.
- All team members must be present at all meetings.
- All team members must answer questions and participate in the discussion at each meeting.
Meeting Agenda
The meeting will follow the agenda, which must be a minimum 1-2 page document:
- A description of all the new issues that have been discovered during the previous week. This includes a list of unresolved design issues.
- A description of all the issues that have been solved over the past week. This includes a list of design issues that were resolved, and how they were resolved.
- An assessment of success at meeting the previous week's plan.
- A plan for the next week, with specific actions and goals for each team member.
- Issues you would like clarified by the TA and/or the instructor.
- When there is a division of labor between team members, the member performing each task must be clearly indicated. For example, this is the case for Programming and Unit testing phases. For these phases, each member is responsible for writing and testing different classes, and this work division must be explained clearly.
Explanation of Submissions (Deliverables)
Requirement and Modeling (R/M)