SENIOR DESIGN

2008 - 2009 SENIOR DESIGN SCHEDULE

Fall Semester - 2008

Tuesday, September 23rd - Initial meeting to discuss the details and expectations of senior design. ATTENDANCE IN CLASS IS REQUIRED - (CAT 61)

Tuesday, October 7th - Students must have created a team, selected an advisor, and selected a project or received approval for a project idea they propose (10 %). ...more

Tuesday, October 14th - Project Plan, abstract, and logo (10 %). ...more

Tuesday, October 21st - Meeting to discuss requirements document and acceptance test plan. ATTENDANCE IN CLASS IS REQUIRED - (CAT 61)

Tuesday, November 25th - Requirements Document (60 %). ...more

Tuesday, December 2th - Acceptance Test Plan (20 %), ...more


Winter Semester - 2009

Tuesday, January 6th - ATTENDANCE IN CLASS IS REQUIRED (Location TBD) Discuss quarter outline, initial presentations, and design document.

Tuesday, January 13th
Website: Requirements Document and Acceptance Test Plan (5%)
1) Submit the URL of your project website. (Supply the URL to BbVista as a "comment").
2) Submit your requirements document (PDF and HTML) and acceptance test plan (PDF). Supply the documents in a single, self-contained .tar/zip file to BbVista as an "attachment". This submission is for archiving only and will not be graded.
3) On your project website, make the requirements document and acceptance test plan available.
4) Send your URL to the reviewing team: If you are Team n, and n>1, then your reviewing team is Team n-1; if you are Team 1 then your reviewing team is Team 10.

Tuesday, January 20th
Review: Requirements Document and Acceptance Test Plan (7.5%)
Submit your review (PDF format). If you are Team n, and n<10, then you will review the work of Team n+1; if you are Team 10 then you will review the work of Team 1.

Tuesday & Wednesday, January 27th & 28th
Initial Presentation (15%)
Submit a short description (max of 150 words) of your project. Supply the description to BbVista as a "comment". The abstract will be used for the projects page. The abstract will not be graded; instead you will receive a grade for your actual presentation.

Presentations should be created describing your project. You may assume a technical audience, but do not assume that the audience knows anything about the domain of your project. Your group is given 5 minutes to prepare, 15 minutes to present, and 5 minutes for question and answers. As your projects probably will not function by the time of the presentation, you should enhance your description of the project with visual aids depicting what your project will look like. In addition to the project description, you should mention your developement methodology, any external stakeholders, and anything novel about your project. Each member of the team should speak and it is highly recommended that you automate the presentation with a tool like PowerPoint or Open Office Impress.

EACH STUDENT MUST ATTEND 5 PRESENTATIONS INCLUDING THIER OWN.

View the schedule of presentation. (5 Groups will meet during class time Tuesday from 6:00 - 9:00, 5 Groups will meet from 1:00-5:00 on Wednesday)

Attire is up to you, however while I do not mandate dressing up, it is recommend dressing as you would for the final presentation. People react different in a suit and this is a good trial run to get the kinks out of your presentation style.

Presenation Guidelines
Evaluation Form
Grading Rubric

Tuesday, February 3rd
Design Document. (40 %)
1) Submit your design document (PDF and HTML). Supply the documents in a single, self-contained .tar/zip file to BbVista as an "attachment".
2) On your project website, make the design document available.
...more details.

Tuesday, February 10th
Integration Test Plan. (10 %)

1) Submit your Integration Test Plan document (PDF).
2) On your project website, make the Integration Test Plan document available.
...more

Tuesday, February 17th
Final: Requirements Document and Acceptance Test Plan (10%)
1) Submit your final requirements document (PDF and HTML) and acceptance test plan (PDF). Supply the documents in a single, self-contained .tar/zip file to BbVista as an "attachment".
2) On your project website, make the final requirements document and acceptance test plan available.

Tuesday, February 17th
Website: Design Document and Integration Test Plan
(5 %)
1) Submit the URL of your project website. (Supply the URL to BbVista as a "comment").
2) Submit your design document (PDF and HTML) and integration test plan (PDF). Supply the documents in a single, self-contained .tar/zip file to BbVista as an "attachment". This submission is for archiving only and will not be graded.
3) On your project website, make the design document and integration test plan available.
4) Send your URL to the reviewing team: If you are Team n, and n>1, then your reviewing team is Team n-1; if you are Team 1 then your reviewing team is Team 10.

Tuesday, February 24th
Review: Design Document and Integration Test Plan. (7.5 %)
Submit your review (PDF format). If you are Team n, and n<10, then you will review the work of Team n+1; if you are Team 10 then you will review the work of Team 1.

Spring Semester - 2009

Tuesday, April  7th: Design document (PDF and HTML) and integration test plan (PDF). The team administrator submits the final version of the documents via WebCT (10%).

Tuesday, April 28th: Beta-version available on project web-site for peer testing. (5 %)

Tuesday, May  5th: Beta-test report. The team administrator submits the test report in PDF format via WebCT (10%). The team administrator sends a copy to the administrator of the reviewed team.

Tuesday, May 5th: Project web-site (final version) (5%).

Tuesday, May 12th: Project code (final version) (50%). The team administrator submits the beta-version via WebCT.

Tuesday May 19th and Wednesday May 20th, Final Presenations (20 %)

Evening of Tuesday May 26th (5:30 PM - 9:00 PM) - Final Four Competition

  • Location: Disque 103

Wednesday, June 2nd - College of Engineering Contest