The intent of this presentation is to provide an “Executive Summary” of your project to Design Day attendees and judging panel.
• Design Day Presentations will be given by each team during scheduled timeslots during Design Day on Friday, April 30,
2010. The team presentation schedule can be found online at: http://www.cse.msu.edu/~cse498/archives/pages/2010_01/2010_01_design_day.htm
•
Presenting teams are required to dress business professional .
• Teams should plan to present for approximately 5 minutes, with the remainder of any time during your timeslot reserved for questions from the judging panel. Significant deviations from the five minute mark may impact judging related to your presentation.
•
The objective of your presentation is to provide a concise overview of your project, giving important information related to the project. Although the judging panel will have viewed your project video and technical specifications, your presentation should accomplish two goals:
– Provide someone who may not have viewed your project materials with a high-level understanding of your project; and
– Highlight particular items you feel are more important than others.
• The remainder of this presentation provides a template for information that may be highly relevant for a presentation of this nature. However, resist the urge to address every piece of information suggested. Pick and prioritize items that provide a good high-level overview.
• Miscellaneous wisdom for an Executive Summary presentation:
• Avoid the tendency to drive into the details before you have painted a very high level view of the information you need to present.
•
With a short presentation, like this, do not feel obligated to have each team member participate in giving the presentation. If you can smoothly transition from member to member in the presentation, you can do so, but do not feel obligated.
NOTE: The red notes on the subsequent slides are suggestions for content. Consider what information best presents your project, including what is offered in “ red ”. (And don’t forget to take the red notes out in your final presentation)

<Team Member 1>
<Team Member 2>
<Team Member 3>
<Team Member 4>
Department of Computer Science and Engineering
Michigan State University
Spring 2010

Information to be considered on this slide should include:
• Client / client business
•
Short project name
• Description of problem being solved and why it is a problem
• How was project “given” to you (not how you chose it, but how did client define the project for you?)
• Intended use of end product
– Was project proof of concept – if yes what will project show and where will it be used downstream?
– Was project actual product – if yes how/when will it be deployed?
3

Consider the following on this slide:
• Conceptual picture of deployed solution
•
Interaction of solution with other systems or people/companies
• High-level view of solution, diagramming particular layers such as user interface, database engine, computational layer, communications layer, etc.
4

Consider the following for inclusion on this slide:
• Discussion of technologies deployed in project
•
Discussion of technology of interfacing points and connections to project sponsor data and/or systems
• Discussion of technology decisions made and why (including constraints you had to work around)
•
Discussion of technology changes made during project
• Discussion of technology limitations of solution
5

At this point, entertain questions.