Jump to content

Guidelines for Presentations

From SDQ-Wiki
This page is a translated version of the page Vortragshinweise and the translation is 100% complete.
Note
This page contains general requirements and guidelines for presentations by students. The information is summarized again on the pages for the different types of presentations: There are also presentation tips for the reading group (in German).

General

Consider the target audience of the talk and create suitable slides:

  • The content should be designed to be understandable and easy to follow for the target audience. Consider which terms can be assumed to be known and which need to be introduced or possibly omitted.
  • If there is too much content that could be presented, when in doubt leave content out and concentrate on specific, interesting aspects instead of trying to touch briefly on everything. Also discuss your selection with your supervisors.
  • For talks in the SDQ Proposal Seminar and the SDQ Institute Seminar, the target audience is not the supervisors but the other attendees, i.e., your fellow students as well as other researchers present, including those from other research groups.

Good advice on effective presentations: Garr Reynolds’ website, Presentation Zen blog and the accompanying book, more tips in the links at the end of this page.

Please also note the page on Hybrid Presentations.


Slides

Important principle: The slides should complement and support the spoken talk, not make it superfluous. This means that the slides should never contain all the information that is said. If the slides contain too much information (especially text), the audience is distracted from the spoken word.

Format

  • The SDQ Document Templates (PowerPoint/OpenOffice/LaTeX) must be used.
  • Projectors at KIT have an aspect ratio of 16:9 or 16:10. With the templates in this format, you can therefore make optimal use of the screen.
  • Font:
    • Sans-serif fonts (e.g., Helvetica, Roboto, Calibri, Arial) are easier to read on screen/projector than serif fonts (e.g., Times, Georgia)
    • The document templates are set to sans-serif fonts. Please do not change this default.
  • Font size:
    • Choose a size that is easy to read even from a typical seating distance from the screen.
    • In PowerPoint's default size, this means a minimum size of 18 pt
    • Maintain font sizes in imported diagrams as well: redraw them or overwrite the labels if necessary
    • The document templates are designed to be easy to read in the default size
  • Every slide except the title slide must contain the following in the footer:
    • Name of the presenter
    • Title of the thesis and type (abbreviation)
      • e.g.: not "Proposal for a Master's Thesis", but "Metamodel Evolution in the Context of a MOF-Based Metamodeling Infrastructure (MA)"
      • Long titles may be shortened in the footer
    • Current slide number
  • The following is also recommended for the footer:
    • Total number of slides (in PowerPoint only possible manually [1])
    • For longer talks, a progress indicator

Preparation

A widely used method for preparing slides without any distracting technology:

  • For each slide, write one to three keywords on a Post-it that describe what is to be conveyed to the audience.
  • Then rearrange the Post-its generously on a sheet of paper.
  • If necessary, stick Post-its together or tear them apart to plan which two slides should be merged or which slide should be split into two.
  • Before writing, turn the adhesive strip of the Post-its to the vertical; this makes it easier to split slides.
  • Important: Only start creating the actual slides on the computer once the order and content of the Post-its are settled.

Required Content

  • Title slide:
    • Topic of the talk (= title of the thesis)
    • Type of talk (final talk for bachelor's/master's thesis, proposal talk for bachelor's/master's thesis, seminar talk, etc.)
    • Name of the presenter
    • Names of the supervising researchers
  • Schedule (only for proposal talks and for final talks with critical reflection)
  • Conclusion slide with outlook: as the last slide

Slide Design

  • Observe the principle above
  • Max. 5–7 bullet points per slide
    • As in the written work, the subdivision of bullet points serves to delimit, not to emphasize.
    • It follows that there must be at least two entries on each outline level.
  • No complete sentences
  • For slides in 16:9 format, do not set text across the full width
    • otherwise hard to read because of overly large jumps
    • use a two-column format
  • Images/diagrams instead of text: Where possible, text should be replaced by illustrative graphics. Helpful images can be found at Sources for images
  • Colors:
    • Red/green and blue/violet are hard to distinguish for color-blind people.
    • Therefore, always use an additional distinguishing feature in diagrams, e.g., solid/dashed
  • Images
    • include them as vector graphics (sharp display at any resolution)
    • scale them with a constant aspect ratio

Time Planning

  • For slides in the "classic style" (5–7 bullet points per slide), plan 1–2 minutes of talk time per slide
  • Other presentation styles can lead to faster slide changes.
  • For time planning, it is recommended to create a table:
Slide Time Content
1 0:00 Title, introduction
2 0:30 Motivation
3 2:00 Foundations
…
  • Place the table next to the presentation computer together with a suitable clock (PowerPoint presenter view, stopwatch …)
  • By comparing against the table during the talk, you can tell whether you are faster or slower than planned and react accordingly
  • Usually you want to present more content than is possible in the given time
    • Less important, further slides should be moved to an appendix and not presented
    • Appendix slides can be shown during the discussion time if follow-up questions on the topic are asked
    • Appendix slides do not count toward the total number of slides

Animations

  • In the scientific field, animations are used (only) to present facts more clearly.
  • Rule of thumb: The audience should be able to grasp a displayed graphic in about 5 seconds.
  • If this is not possible, the graphic should be built up step by step with "appear" animations.
  • But: Use animations sparingly:
    • Use animation effects only to clarify the content, not as decoration.
    • Simple appear animations are often sufficient.
    • Therefore, please do not use blinking, flying in, checkerboard appearance, tilting, etc.

Tip for the Title Slide

  • A catchy image on the title slide that depicts the content of the talk helps the audience remember it.
  • Example: A stopwatch and a racetrack for benchmarks.

Time Limits

See also: Length of Written Work and Presentations

Talk

Scheduling

  • The time limit must be observed. As in an exam, this is the only way to create the same conditions for everyone.
  • If you run over time, the supervisor will stop the talk.
  • Using considerably less than the available time (>10%) is graded negatively.
  • Questions from the audience are usually only allowed in the discussion period that follows.
  • Rehearsal:
    • Rehearse the talk once or twice at home so that you can deliver it fluently
    • Use the scheduling table and adapt it if necessary

Technical Preparation

  • Familiarize yourself with the presentation software beforehand.
  • Using the presenter view is useful for presentations. See: Screen Presentation with Notes

In-Person Talks

  • Arrive at least 15 minutes before the start of the session to test the equipment.
  • Presenting from your own laptop is possible and encouraged.
    • If you cannot use your own laptop, please arrange with your supervisor for a laptop to be provided.
    • Before the talk, test whether the presentation runs as desired on the other device.
  • Always bring the presentation on a USB stick as a backup.
  • Projectors or presentation screens are permanently installed in the seminar rooms.
    • The wired connections available are USB-C and HDMI. If necessary, please bring the appropriate adapters for other connections.
    • The projector also supports Miracast (wireless projection).
    • Before the talk, check that the presentation computer works with the projector/screen as desired.
  • On macOS, some projectors are used with an incorrect default resolution
    • This can be fixed in the display settings.
    • To do so, "show all resolutions" must be enabled (see image)
    • Then the native resolution of the projector can be selected
  • If audience members also participate online (hybrid presentation), the slides must be shared. To prepare for this, make sure beforehand that
    1. the presentation laptop has internet access
    2. the necessary software (Teams, Zoom) is installed on the presentation laptop
    3. you have access to the right channel, e.g., in Teams

Online Talks

  • Here too, be in the online room before the start of the session to test the equipment
  • Always use a headset or a speaker microphone to minimize ambient noise and room echo.
  • Check beforehand that the webcam works.
  • Set a clearly visible mouse pointer (red dot or similar) in the presentation software to point at the slides.

Delivery

  • Introduce yourself at the beginning
    • If the session chair introduces you, begin with "Thank you for the kind introduction." and do not repeat your name
    • Otherwise, state your name
  • When presenting, stand next to the screen, not in front of it, so that everyone in the audience can see the whole projection
    • Position the laptop so that you can keep an eye on the presenter view
    • Speak toward the audience, not toward the screen (do not speak with your back to the audience)
    • During the talk, look at everyone in the audience, not only at the supervisors
    • When explaining diagrams, do not point at the laptop but at the screen, without losing contact with the audience.
  • Seriousness:
    • Do not chew gum
    • Overly casual behavior is received negatively. The audience should see that you take your talk seriously.
    • Do not downplay your own contribution, e.g., by saying "I researched a little bit" or similar
  • Speech/acoustics:
    • Speak clearly and concretely
    • Guideline for sentence length: one thought = one sentence.
    • Speak somewhat louder and somewhat more slowly than you would in a direct conversation with one person. Deliberately hold the pauses between sentences.
    • Before each sentence, think about which word should be emphasized
  • Speaking freely:
    • The talk should be delivered freely. This means:
    • Do not write out the text completely and read it aloud (like a news anchor)
    • You can memorize the introduction (first slide) to get into the talk well
    • Deliver the rest of the talk freely, supported by notes.
  • Coordination of communication channels:
    • The slides should support the spoken word and not show something different.
    • Consistent information must reach the audience through both the visual and the acoustic channel.


Proposal Talk

Goals

  • Convey to the audience which problem you will address in your thesis, why solving the problem is important, which approach you are pursuing, and how your approach is to be evaluated.
    • It must be clear that you approach your thesis with scientific methodology.
    • You must make clear that the problem is relevant and still unsolved or insufficiently solved.
    • You must compare your approach with similar work from the literature (related work).
    • You must show how you intend to demonstrate that your approach actually delivers the promised improvements (form of evaluation, e.g., case study, experiment, formal proof).
  • The speaker uses the talk to obtain feedback on the planned work from the researchers. They can
    • point to further related work
    • assess your methodology
    • share experiences with the tools you intend to use
    • give hints on how to improve the approach
  • The talk should therefore be designed so that it enables the researchers to assess the points mentioned (e.g., by listing related work, tools used, etc.)

Mandatory Content

  • Organizational matters
    • Who is the co-supervisor? (If this has not been determined yet, you should ask about it at the latest during the talk)
    • When are code reviews planned?
  • For implementation work: We want to reuse as much existing work and implementation as possible. Therefore, also address
    • which existing implementations of the chair (PCM, Vitruvius, etc.) you want to build upon
    • where you want to extend them

General Structure

  • About 6–9 slides
  • No outline slide with a table of contents (an overview is not necessary for a talk of only 12 minutes)
  • However, a progress bar/tab index on each slide is quite useful for orientation
  • No lengthy introduction: after 2–3 slides it must be clear what you want to do in your thesis
  • First present what you want to do, and give details later on why it is important and how you want to do it
  • If related work only serves to delineate your work and you do not build on it, present it at the end of the talk so as not to interrupt the presentation of the approach unnecessarily.

Possible Structure (Not Mandatory)

  • Slide 1: Motivation and illustration of the problem (and, if applicable, your approach), graphically if possible (on one slide!)
  • Slide 2: Instead of an outline slide, show a PIBA (four bullet points).
    • Problem, Idea, Benefit, Actions (PIBA)
      • Problem: What is the problem? (understandable to any computer scientist)
      • Idea: What is your approach?
      • Benefit: What is the benefit of your approach? (also compared to other approaches)
      • Actions: Which steps do you want to take?
    • Depending on the topic, three aspects may also suffice (e.g., P-I-B); PIBA is not a strict requirement
  • Slide 3: Foundations: What are the most important foundations of your subject area?
  • Slide 4: Related work: What has already been done in the research area? (alternatively after the evaluation, if only for delineation)
  • Slide 5: Concrete, simple example of your approach (illustrated)
  • Slide 6: Implementation of your approach
  • Slide 7: Planned evaluation
  • Slide 8: Schedule
  • Slide 9: Summary; simply show the PIBA slide (slide 2) again.
    • The slide does not have to be an exact copy of the PIBA slide; it can also omit aspects and include additional points such as evaluation or future work

Motivation

If you need to motivate, show the problem concretely using an easily understandable and usually simple case. Examples:

  • For prediction methods: Show predictions that you consider too imprecise. Show the targeted improvement already here.
  • For tool implementations: Show how much effort it is to perform a central task without your tool. Give an initial impression of the complexity of automating this task.
  • For experiments/empirical studies: Show the research question of your study and why an answer to it is a gain in knowledge. And above all, for whom the findings are important.

Foundations

  • Introduce the most important technical terms from your subject area (at least those from the title of the thesis!)
  • Explain fundamental concepts/models (e.g., the Palladio Component Model)

Related Work

  • Use names and years of the publications (e.g., [Balsamo 2004]), and keep the correct references (title, authors, form of publication, etc.) ready on a backup slide.
  • For each cited work: the title, or in one bullet point what is done there
  • First 2–3 foundational works, standard works (books, important articles),
  • then the 3–4 most relevant related works you have found
  • Delineate your work concretely from the latter. What is possible with your approach that is not possible with these approaches? How much do you want to improve individual parts of the related approaches?
  • However, do not condemn related work. Be aware that your approach often improves only one detail, and that your approach usually does not have all the strengths of the related work. Nobody believes that your approach solves all problems.
  • Do not forget industrial solutions (that is, do not only search Google Scholar and the computer science library)! Often there are already commercial approaches. Try to assess them as well as the publicly available data allows.

Example

  • It should demonstrate as simply and understandably as possible what happens when your approach is applied or your product is used.
  • Build it up step by step, possibly with animation.
  • Images are easier to understand than text.

Implementation of Your Approach

  • Which steps do you want to take?
  • Demonstrate the iterative structure of the work with work packages (including optional ones).
  • Couple work packages with the schedule. (A Gantt chart is usually too cluttered. Limit yourself roughly to 3–4 work packages. Writing the thesis is not a work package, but part of the schedule. Programs for creating Gantt charts include Microsoft Project and Microsoft Visio.) The schedule should also include the planned code reviews.
  • Demonstrate a systematic and goal-oriented procedure.
  • Risk management (What risks are there? How do you plan to react to them, if necessary?)
  • Which tools are to be used? (Name them concretely)
  • Be as concrete as possible on this slide. Not "I will create a model transformation for concurrency patterns", but "I will use the eXtend language from the OAW framework to implement a model-to-model transformation. The design patterns Replication and Rendezvous contained in the source model are mapped in the target model to parallelism operators of the stochastic process algebra Capra." Not "I will solve the problem with LLMs", but "I will use prompts such as <example prompt> with this additional context information."

Planned Evaluation

  • Form (case study, controlled experiment, formal proof)
  • Case example (object of study during the evaluation)
  • Goal, Question, Metric (What goal does the evaluation pursue? Which questions are derived from the goal? Which metrics must be collected to answer the questions?)
  • Hypotheses (What result do you expect/hope for? What are the expected answers to the questions?)
  • The evaluation must be designed so that a computer scientist not familiar with the subject area can judge whether your work was a success or not.

Schedule

  • Show a shortened schedule that reveals the basic structure of your procedure.
  • Make clear how you ensure incrementality in your work. A waterfall-like process is usually questioned, as the risk of failing in an early phase and producing no results is too high.
  • Explicitly show time for buffers, interim evaluations, or milestones.
  • Activities can quite well overlap in the schedule. For example, you can start writing early while still working on other work packages.

Summary

  • Feel free to show the PIBA slide again here as a basis for discussion.
  • The slide does not have to be an exact copy of the PIBA slide; it can also omit aspects and include additional points such as evaluation or future work
  • Still summarize the problem statement and your planned work once more in 2–3 sentences, and do not end merely with the words "Here is the PIBA slide once more".



Final Talk

Please also note the guidelines for the proposal talk again!

Goals

In the final talk, you present the results of your thesis. You show …

  • … that you have worked on a relevant problem of software engineering/computer science using scientific methods.
  • … that you are also able to explain/sell your solution.
  • … that the problem was so difficult or the solution approach so extensive that a computer scientist had to spend four (bachelor's thesis) or six months (master's thesis) on it.
  • … that you are familiar with your field and …
  • … that you have searched extensively and independently for related work, to the best of your knowledge and belief, and …
  • … that you can place your work in relation to the related work (what can I do better, what worse).
  • … how you implemented your solution idea. Your explanations must be understandable to a computer scientist without your prior knowledge.
  • … how your implementation works conceptually.
  • … how your work is to be assessed, by presenting and discussing your evaluation results in detail.
  • … what assumptions and limitations your approach/current implementation has.
  • … where future work can build on your work.
  • … that you can competently and reasonably defend your approach when asked follow-up questions.

Possible Structure

  • Appetizer (illustration of problem + solution approach, preferably graphical)
  • Motivation (Why are you doing what you are doing?)
  • PIBA (What are the problem statement and solution approach? Problem, Idea, Benefit, Actions)
  • Foundations (understandable to computer scientists in general)
  • Related work (incl. differentiation from your own work)
  • Solution approach (What did you do and how?)
  • Evaluation (goal, research question, metrics, results)
    • For implementations additionally: quality assurance measures, test cases, …
  • Limitations (limits of the solution approach, assumptions)
  • Summary (incl. outlook on future work)

The main emphasis is on your own solution approach, closely followed by the evaluation! This must also be reflected in the number of slides spent on these parts. Nevertheless, the appetizer must captivate the audience; they should get the feeling: "I want to know now how she/he got a grip on the problem!"

Doctoral Defense

Internal page: Disputation.

See also