Deliverables

Assignments

Project

Proposal

Submitted on Feb. 2.

Proposal Review Meeting

Meetings to discuss your project proposals will happen on the morning of Feb. 8 in EN-1000 according to the schedule below:

Group Number Time
12 9:00 – 9:10
11 9:10 – 9:20
10 9:20 – 9:30
9 9:30 – 9:40
8 9:40 – 9:50
7 9:50 – 10:00
6 10:00 – 10:10
5 10:10 – 10:20
4 10:20 – 10:30
3 10:30 – 10:40
2 10:40 – 10:50
1 10:50 – 11:00

Initial Design Document

Submit via D2L by 5:00 p.m. on Feb. 26.

  • Provide brief introduction to project.  This can be a revised version of the proposal.
  • Select and describe the initial use cases to be implemented in the first iteration.
  • Present class diagrams giving the overall structure of your system, in combination with explanatory text.
  • Present sequence diagrams (generally, one per use case) showing the flow of messages between objects.
  • Provide some explanation of your high-level design choices, illustrating your adherence to design principles and your usage of design patterns.
  • Expected length 10-15 pages, inclusive of UML diagrams which should be embedded into the document.
  • Submit as a PDF file (not Word).


Initial Design Presentations

Presentations describing your projects and initial designs to be held on Thursday, March 1 in EN-1000 according to the schedule below:

Group Number Time
1 9:00 – 9:15
2 9:15 – 9:30
3 9:30 – 9:45
4 9:45 – 10:00
5 10:00 – 10:15
6 10:15 – 10:30
7 10:30 – 10:45
8 10:45 – 11:00
9 11:00 – 11:15
10 11:15 – 11:30
11 11:30 – 11:45
12 11:45 – 12:00
  • Depending on time, it may be necessary for group 12 to present during class on Friday (March 2).
  • These are 12 minute presentations, followed by 3 minutes for questions.  All group members expected to participate in presentation.  All students are expected to attend all presentations and to participate by asking questions and providing suggestions.  There will be a mark for participation.
  • Expected outline for presentations:
    • Provide a brief introduction to the project.  Try and incorporate some kind of visualization of your system/application (even a hand-drawn sketch).  Favour visuals over text in your slides.
    • Describe the overall structure of your design at a high level of abstraction.  Use some UML diagrams.  They do not need to be comprehensive.  Make sure any diagrams are legible when viewed from the back of the classroom.
    • Present some of the more interesting design choices you have faced and explain how your design adheres to design principles and utilizes design patterns. It is also acceptable to present interesting design challenges you have yet to resolve.
    • Content can come from the Initial Design Document (IDD) but do not try and cram everything from your IDD into this presentation.  Try and make it interesting and engage feedback from the class.