Final Presentations/Documentation

Home Schedule Policies Resources Design Notebooks

Final Presentations

The final presentation is your opportunity to celebrate your success and share the experience with your fellow students, faculty, friends, and guests. Your intended audience for this presentation is a technically-inclined person, but not necessarily an engineer. Pretend your presentation will be shown on a television special about new and great technologies – you want the audience to leave feeling that they’ve learned a great deal about the latest technology (and perhaps seen sheer genius in action).

Schedule of events

4:00 - 4:30: Interactive demonstrations and posters. This is a time for guests to individually interact with your products and see demonstrations. It is arranged at the beginning of the time in order to accommodate the schedules of our guests in the SPU administration.

4:40 - 5:50: Team presentations. Each team will have a total of 15 minutes for their presentation. Because you will have demonstrated your project earlier, you may show a reduced version of your demonstration.

What to present

Note: Turn in a copy of your final presentation on CD/DVD on the day you present.

Have some fun with this, but be sure to cover at least the following areas:

bulletIntroduce all team members and their areas of expertise
bulletExplain what the purpose of the final product is – Why does Joe Techie’s life depend on its success?
bulletDescribe what the specific engineering challenges of your project are. Include both hardware and software challenges.
bulletPresent the story of your design – early concepts to final design. Highlight interesting challenges and solutions. Don't be afraid to discuss mistakes as long as you recovered well. Joe Techie needs to know that you’re human.
bulletDemonstrate the product. Make it look as cool as it really is. Use A/V equipment so that everybody can see you product.
bulletIf necessary, show videotaped/photographed field trials
bulletPass around items for the audience to touch and feel. For example, if you have left over PCBs, pass them around. If you don’t need your first prototype any more, pass it around.  Don’t pass your finished product around, though – you want your demo to work…

Media Equipment

We will be in OMH 109 for our final presentations. The media equipment includes:

bulletWinXP computer
bulletVCR (with aux input that can be used for a video camera)
bulletDVD player
bulletAudio amplifier
bulletMicrophone
bulletOverhead projector

Please coordinate your media use with the other teams presenting on the same day.

Details

The Final Presentation should require about 15 min. of class time, plus time for questions.  Each member of the group should make a significant contribution to the presentation. Each team member will receive an individual grade for their part in the presentation.

Final Documentation

Throughout the year, you've been keeping an up-to-date project notebook. However, chances are that some documents fell through the cracks and haven't been  updated. Update all the documents in your project notebook to reflect the current state of your project. 

Format

You should turn in one binder that includes all of your final documentation. (Web-based notebook writers - please discuss options with instructor.) Do not include old, edited copies in your binder. Your final documentation will become your team's senior design portfolio, and will be archived and used for engineering program assessment.

First, review the description of the design notebook to remind yourself of your task.

Here are some examples of what changes are expected in each section:

Design Documents

Add a section that describes what major changes you made from your initial design and why you made the change. 

Functional Specification

Attach all approved change requests to your functional specification.

Schedule

Include the final schedules from each of the three quarters.

Hardware Technical Specification

Schematic - Update to reflect what you actually built. Some groups have a lot of changes here.

Power Supply - Update to reflect reality. 

PCB - Don't change the PCB, but update the documents to reflect the PCB that was actually built.

Software Technical Specification

Software Architecture - Update and rewrite to reflect the actual software.

Device Drivers - Ditto

Interface Technical Specification

Update to reflect any changes you made to your user and other interfaces.

Mechanical Technical Specification

Update to reflect you actual enclosure.

Test Plan and Results

Include all of your test plans and the results from them. It is OK for results to be handwritten.

 

Kevin Bolding September 22, 2009