how to make a good presentation

Download How to Make a Good Presentation

Post on 09-Feb-2016

53 views

Category:

Documents

3 download

Embed Size (px)

DESCRIPTION

How to Make a Good Presentation. Daniela Stan DePaul University July 1 st , 2005. Outline. Part I: Key Advice for Presentation Style Part II: Key Advice on Presentation Content Topics covered in Part II Selecting a Problem Picking a Solution. Slide Presentation:. - PowerPoint PPT Presentation

TRANSCRIPT

  • How to Make a Good Presentation

    Daniela StanDePaul University

    July 1st, 2005

  • OutlinePart I: Key Advice for Presentation Style

    Part II: Key Advice on Presentation Content

    Topics covered in Part IISelecting a ProblemPicking a Solution

  • Slide Presentation:We describe the philosophy and design of the control flow machine, and present the results of detailed simulations of the performance of a single processing element. Each factor is compared with the measured performance of an advanced von Neumann computer running equivalent code. It is shown that the control flow processor compares favorably in the program.

    We present a denotational semantics for a logic program to construct a control flow for the logic program. The control flow is defined as an algebraic manipulator of idempotent substitutions and it virtually reflects the resolution deductions. We also present a bottom-up compilation of medium grain clusters from a fine grain control flow graph. We compare the basic block and the dependence sets algorithms that partition control flow graphs into clusters. A hierarchical macro-control-flow computation allows them to exploit the coarse grain parallelism inside a macrotask, such as a subroutine or a loop, hierarchically. We use a hierarchical definition of macrotasks, a parallelism extraction scheme among macrotasks defined inside an upper layer macrotask, and a scheduling scheme which assigns hierarchical macrotasks on hierarchical clusters.

    We apply a parallel simulation scheme to a real problem: the simulation of a control flow architecture, and we compare the performance of this simulator with that of a sequential one. Moreover, we investigate the effect of modeling the application on the performance of the simulator. Our study indicates that parallel simulation can reduce the execution time significantly if appropriate modeling is used.We have demonstrated that to achieve the best execution time for a control flow program, the number of nodes within the system and the type of mapping scheme used are particularly important. In addition, we observe that a large number of subsystem nodes allows more actors to be fired concurrently, but the communication overhead in passing control tokens to their destination nodes causes the overall execution time to increase substantially.The relationship between the mapping scheme employed and locality effect in a program are discussed. The mapping scheme employed has to exhibit a strong locality effect in order to allow efficient executionMedium grain execution can benefit from a higher output bandwidth of a processor and finally, a simple superscalar processor with an issue rate of ten is sufficient to exploit the internal parallelism of a cluster. Although the technique does not exhaustively detect all possible errors, it detects nontrivial errors with a worst-case complexity quadratic to the system size. It can be automated and applied to systems with arbitrary loops and nondeterminism.

  • Slides OverviewWe describe the philosophy and design of the control flow machine, and present the results of detailed simulations of the performance of a single processing element. Each factor is compared with the measured performance of an advanced von Neumann computer running equivalent code. It is shown that the control flow processor compares favorably in the program.

  • How to Give a Bad Talk David A. Patterson, UC, BerkeleyWhy waste research time preparing slides? Ignore spelling, grammar and legibility. Who cares what 50 people think?

    Transparencies are expensive. If you can save five slides in each of four talks per year, you save $7.00/year!

    Do you want to continue the stereotype that engineers can't write? Always use complete sentences, never just key words. If possible, use whole paragraphs and read every word.

  • How to Give a Bad Talk David A. Patterson, UC, Berkeley (cont)You need the suspense! Overlays are too flashy.

    Be humble -- use a small font. Important people sit in front. Who cares about everybody else?

    Flagrant use of color indicates uncareful research. It's also unfair to emphasize some words over others.

    Confucius says ``A picture = 10K words,'' but Dijkstra says ``Pictures are for weak minds.'' Who are you going to believe? Wisdom from the ages or the person who first counted goto's?

  • How to Give a Bad Talk David A. Patterson, UC, Berkeley (cont)You should avoid eye contact to show respect. Blocking screen can also add mystery.

    You prepared the slides; people came for your whole talk; so just talk faster. Skip your summary and conclusions if necessary.

    Why waste research time practicing a talk? It could take several hours out of your two years of research. How can you appear spontaneous if you practice? If you do practice, argue with any suggestions you get and make sure your talk is longer than the time you have to present it.

  • Hints for Good PresentationSpeak clearly

    Use large fonts

    Use lots of figures:A picture is worth a thousand words

    Point to the projection (screen), not the source Do not use a pointer

  • Hints for Good PresentationBe sure the projection is on the screen

    Watch the time

    Talk to the audience, not the screen Do not read your slides to the audience

  • Alternatives to Bad Presentations

    Allocate 2 minutes per slide, leave time for questions

    Dont over animate

    Do dry runs with friends/critics for feedback, including tough audience questions Tape a practice talk (audio tape or video tape)Dont memorize speech, but have notes readyBill Tetzlaff, IBM: Giving a first class job talk is the single most important part of an interview trip. Having someone know that you can give an excellent talk before hand greatly increases the chances of an invitation. That means great conference talks.

  • Things to Think AboutOral Communication is different from written communicationK.I.S.S. (keep it simple stupid)Focus on getting one to three key points acrossRepeat key insightsThink about your audience address them in layerssome are experts in your sub-areasome are experts in the general areaothers know little or nothingThink about your rhetorical goalsClear picture of your contributionsMake the audience want to read your paperPractice in publicIt is hard distilling work down to 20 or 30 minutes

  • ROC: Recovery-Oriented ComputingAaron Brown and David PattersonROC Research Group, EECS Division, University of California at BerkeleyFor more info: http://roc.cs.berkeley.edu

  • AME is the 21st Century Challenge

    Availabilitysystems should continue to meet quality of service goals despite hardware and software failuresMaintainabilitysystems should require only minimal ongoing human administration, regardless of scale or complexity: Today, cost of maintenance = 10X cost of purchaseEvolutionary Growthsystems should evolve gracefully in terms of performance, maintainability, and availability as they are grown/upgraded/expandedPerformance was the 20th Century Challenge1000X Speedup suggests problems are elsewhere

  • People are the biggest challenge

    People > 50% outages/minutes of failureSources of Failure in the Public Switched Telephone Network, Kuhn; IEEE Computer, 30:4 (Apr 97)FCC Records 1992-1994; Overload (not sufficient switching to lower costs) + 6% outages, 44% minutes

    Chart1

    0.2659574468

    0.2553191489

    0.2021276596

    0.1170212766

    0.1489361702

    0.0106382979

    Number of Outages

    Number of Outages

    Chart2

    0.25

    0.25

    0.125

    0.3214285714

    0.0357142857

    0.0178571429

    Minutes of Failure

    Minutes of Failure

    Sheet1

    Minutes of FailureNumber of Outages

    Human-company14%25%

    Human-external14%24%

    HW failures7%19%

    Act of Nature18%11%

    SW failure2%14%

    Overload44%6%

    Vandalism1%1%

    100%100%

    Less Overload56%94%

    Leaving out overload

    Minutes of FailureNumber of Outages

    Human-company25%Human-company27%

    Human-external25%Human-external26%

    HW failures13%HW failures20%

    Act of Nature32%Act of Nature12%

    SW failure4%SW failure15%

    Vandalism2%Vandalism1%

    100%100%

    hoursperiod (hours)years

    235064040

    0.9999942961

    Telephone swtiches

    Sheet1

    0

    0

    0

    0

    0

    0

    Minutes of Failure

    Sheet2

    Sheet3

    Chart1

    0.2659574468

    0.2553191489

    0.2021276596

    0.1170212766

    0.1489361702

    0.0106382979

    Number of Outages

    Number of Outages

    Chart2

    0.25

    0.25

    0.125

    0.3214285714

    0.0357142857

    0.0178571429

    Minutes of Failure

    Minutes of Failure

    Sheet1

    Minutes of FailureNumber of Outages

    Human-company14%25%

    Human-external14%24%

    HW failures7%19%

    Act of Nature18%11%

    SW failure2%14%

    Overload44%6%

    Vandalism1%1%

    100%100%

    Less Overload56%94%

    Leaving out overload

    Minutes of FailureNumber of Outages

    Human-company25%Human-company27%

    Human-external25%Human-external26%

    HW failures13%HW failures20%

    Act of Nature32%Act of Nature12%

    SW failure4%SW failure15%

    Vandalism2%Vandalism1%

    100%100%

    hoursperiod (hours)years

    235064040

    0.9999942961

    Telephone swtiches

    Sheet1

    0

    0

    0

    0

    0

    0

    Minutes of Failure

    Sheet2

    Sheet3

  • Recovery-Oriented Computing (ROC) Hypothesis

    If a problem has no solution, it may not be a problem, but a fact, not to be solved, but to be coped with over time Shimon PeresFailures are a fact,