CSE498, Collaborative Design, Spring 2012
Computer Science and Engineering
Michigan State University

Major Milestones

  • Week 3, Monday, January 23, 2012

    Status Report Presentations
  • Each team gives a five minute status report on a variety of things including client contact, client meeting schedules, team meeting schedules, team organization, server systems and software, development systems and software, a brief description of the project, the status of their project plan, and the initial identification of risks.

    A PowerPoint template is provided on the Downloads page.

    As with all of these milestones, this date indicates the due date. So, in this case the due date is the Monday of the third week, which means that the teams have to complete this work in first three weeks.

  • Week 4, Monday, January 30, 2012

    Project Plan Presentations
  • Each team gives a formal presentation about their project including the functional specifications, design specifications, technical specifications, risks, and proposed project schedule.

    A PowerPoint template is provided on the Downloads page.

    Each team also submits a completed first draft of their project plan.

    While these presentations are made over the course of two weeks (four meetings), all teams must submit their materials and be be ready to present on this date. The per team schedule of presentations for the two weeks is posted on our All-Hands Meetings page the evening prior to this date. Dress for the presentations is business casual.

    Given the short time frame, the project plans are considered a living document, which teams are allowed to update during the semester.

    For examples of project plan presentations, visit course web sites from previous semesters by following links from the Archives page. Note that requirements may change from semester to semester.

  • Week 7, Monday, February 20, 2012

    Alpha Presentations
  • Each team gives a formal presentation demonstrating an alpha version of their system. The purpose of the alpha presentation is to demontrate that the team is capable of completing their project, to specifications and on time. While the software is not expected to be feature complete, all high priority risks should be mitigated.

    A PowerPoint template is provided on the Downloads page.

    While these presentations are made over the course of two weeks (four meetings), all teams must submit their materials and be be ready to present on this date. The per team schedule of presentations for the two weeks is posted on our All-Hands Meetings page the evening prior to this date.

    Corporate clients are invited to attend alpha presentations. If a corporate client is interested in attending, we can work together to schedule it.

    For examples of alpha demonstration presentations, visit course web sites from previous semesters by following links from the Archives page. Note that requirements may change from semester to semester.

  • Week 12, Monday, April 2, 2012

    Beta Presentations
  • Each team gives a formal presentation demonstrating a beta version of their system. The purpose of the beta presentation is to demonstrate that the software portion of the project is complete. While the system may not be totally bug free, the software is expected to be feature complete.

    A PowerPoint template is provided on the Downloads page.

    While these presentations are made over the course of two weeks (four meetings), all teams must submit their materials and be be ready to present on this date. The per team schedule of presentations for the two weeks is posted on our All-Hands Meetings page the evening prior to this date.

    Corporate clients are invited to attend alpha presentations. If a corporate client is interested in attending, we can work together to schedule it.

    For examples of beta demonstration presentations, visit course web sites from previous semesters by following links from the Archives page. Note that requirements may change from semester to semester.

  • Week 15, Monday, April 23, 2012

    Project Videos
  • As part of the course deliverables, each team creates a demonstration video of their project. All of the videos are due on this date, the Monday of the last week of class. We watch the videos during the meetings of the last week and the exam time.

    For examples of project videos, visit course web sites from previous semesters by following links from the Archives page. Note that requirements may change from semester to semester.

  • Week 15, Wednesday, April 25, 2012

    All Deliverables
  • All project deliverables are due on this date.

    Each team must submit all deliverables including all source code (checked out of any repository), the project plan, the user manual, the administrator manual, all-hands meeting PowerPoint presentations, the Camtasia project folder, and the project video.

    Teams must submit their deliverables at the all-hands meeting on this date using the team USB stick.

  • Week 15, Thursday, April 26, 2012

    Design Day Setup
  • Setup for Design Day (see below) takes place at the MSU Union on the afternoon of the day before Design Day. All teams and every team member must participate in setup from 2:30pm until the setup is complete.

  • Week 15, Friday, April 27, 2012

    Design Day
  • At the end of each semester, the College of Engineering sponsors Design Day, at which student teams from throughout the college showcase their capstone course design projects in the MSU Union.

    All teams and every team member must participate in Design Day from 7:00am until the end of the Design Day Awards Ceremony, approximately 2:30pm.