1 / 12

Title

Title. Name(s) Department of Computer Science and Engineering University of South Florida Tampa, FL 33620 email@cse.usf.edu. Acknowledgments. Acknowledge anyone that has helped you. Agenda. This is your talk outline. Don’t change it.

gmatlock
Télécharger la présentation

Title

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Title Name(s) Department of Computer Science and Engineering University of South Florida Tampa, FL 33620 email@cse.usf.edu

  2. Acknowledgments • Acknowledge anyone that has helped you

  3. Agenda This is your talk outline. Don’t change it. Try to do this with one slide per item, except for Design where you will need more than one slide. Demo should be a video and must explicitly show that you have met your requirements. The Demo is the most important part of this presentation. • Background • Problem • Requirements • Demo • Design • Constraints • Applicable standards • Trade-offs made

  4. Background • First level • Second level • Third level Here describe the background to your project. The background should be sufficient so that your problem statement makes sense to your audience. One or two slides should do it. Do not discuss your solution here.

  5. Problem • First level • Second level • Third level Here describe your problem in one or two concise and precise sentences. Problems are usually stated as questions. Do not discuss your solution here.

  6. Requirements • First level • Second level • Third level Here list your requirements. They should match what you submitted. Remember, requirements are always numbered and measurable. One or two slides should do it. If you have many requirements, you may need to omit the acceptance criteria for brevity.

  7. Demo • First level • Second level • Third level Here include a slide to describe what the demo will show… the have a demo video that explicitly shows that you met your requirements.

  8. Design • First level • Second level • Third level Here describe how you will solve your problem (and meet your requirements). You will likely need mock-up screens, data structure descriptions, flowcharts, and/or block diagrams. In short, a design is a picture… it is not a bullet list.

  9. Constraints • First level • Second level • Third level What are the constraints for your project? This may include one or more of accessibility, aesthetics, codes, constructability, cost, ergonomics, extensibility, functionality, interoperability, legal considerations, maintainability, manufacturability, marketability, policy, regulations, schedule, standards, sustainability, or usability.

  10. Applicable standards • First level • Second level • Third level What are the engineering standards that apply to your project? List them. Explain how they apply to your project.

  11. Trade offs • First level • Second level • Third level What alternative designs did you consider and what trade-offs were made?

  12. Notes • Some rules of thumb • One slide per minute of your talk • Bullet text is one line at most • Slides are not meant to be read • Make sure font sizes are large enough for all to see • No gratuitous “art” • Neatness counts for more than you may first think • Sloppy presentation implies sloppy thinking and sloppy work This is an example of a bad slide. It has far too much text on it.

More Related