What should a tutorial look like?
In case your tutorial is accepted, the following offers suggestions for preparing and
presenting your tutorial.
- Contents
- When preparing the tutorial, keep your audience in mind.
- People don't pay for a tutorial in order to hear things that they already know or that are irrelevant for their work.
- Don't be vague, don't waste time with lengthy introductions, but speak to the point.
- Don't try to impress the audience with the amount of your research, but convey practical knowledge and ideas that the participants will find useful for their own work.
- Whenever possible, use examples and case studies and avoid lengthy abstract passages.
- Consider demonstrations on video or an overhead panel.
- In order to get an audience as homogeneous as possible, clearly state which knowledge you expect from the participants in the tutorial description.
- Slides and notes
- You will have to prepare tutorial notes for the participants.
- These handouts usually contain copies of the slides that you show.
- Use at least a 14 pt (or better an 18 pt) font on all of your slides.
- A good slide should not just repeat everything you say but summarize your presentation.
- Use short phrases and keywords instead of full sentences.
- People cannot read as fast as you speak. Make heavy use of pictures and examples.
- Use colors where they are helpful, but remember that they will not appear in the black and white handouts.
- Don't put too much or too little material on a single slide.
- A good rule of thumb is to spend 3 minutes per slide.
- Don't include slides that you will skip in the presentation; people will find that annoying.
- You will have to deliver the tutorial notes in camera-ready form before the conference. The deadline will be announced.
- To avoid wasting paper, copy two slides on a single page (reduced size). The printed area of such a page must not exceed 27 x 17cm (10.5 x 6.7 inch).
- In addition to the slide copies, also consider providing full-text handouts (papers, summaries, bibliography, etc.). Participants will appreciate that.
- The maximum length of the notes for a half-day tutorial should be 50 pages for slide copies and another 20 pages for full-text material. For full-day tutorials these numbers can be doubled.
- Try to achieve good printing quality.
- We will add an uniform cover page to all tutorial notes.
- Put slide numbers on the slides and page numbers on the pages.
- Presentation
- The participants expect that your presentation will be much easier to understand than a book about the same subject.
- Speak clearly and lively. Try to interact with your audience.
- Encourage the audience to ask questions.
- A presentation is much more lively if it also includes examples and demonstrations on the blackboard, on video or on an overhead panel.
- Tutorials should be split into sessions of 1.5 hours each with a 1/2 hour coffee break in between.
- Don't overrun your tutorial time. After the tutorial the participants will be asked to assess the tutorial with a questionnaire.
- A good rating will help you when applying for other tutorials in the future.
PEPM Proceedings is available for free download from ACM DL during the POPL week!
News
2012-11-16
A preliminary
program is available.
2012-11-15
Information regarding the
venue,
registration, and accommodation updated. Please note that the early registration deadline is 31st December, and some hotels have reservation deadline as early as 15th December.
2012-11-14
17 papers accepted out of submitted 29.
2012-09-28
Submission deadline extended until Sun, Oct 7 23:55 GMT.
2012-09-14
Title and abstracts of
invited talks announced.
2012-07-17
2012-06-16
Call-for-papers announced.
The PEPM Symposium/Workshop series aims at bringing together
researchers and practitioners working in the areas of program
manipulation, partial evaluation, and program generation. PEPM focuses
on techniques, theory, tools, and applications of analysis and
manipulation of programs.
The 2013 PEPM workshop will be based on a broad interpretation of
semantics-based program manipulation and continue last years'
successful effort to expand the scope of PEPM significantly beyond the
traditionally covered areas of partial evaluation and specialization
and include practical applications of program transformations such as
refactoring tools, and practical implementation techniques such as
rule-based transformation systems. In addition, the scope of PEPM
covers manipulation and transformations of program and system
representations such as structural and semantic models that occur in
the context of model-driven development. In order to reach out to
practitioners, a separate category of tool demonstration papers will
be solicited.
Topics of interest for PEPM'13 include, but are not limited to:
- Program and model manipulation techniques such as: supercompilation, partial evaluation, fusion, on-the-fly program adaptation, active libraries, program inversion, slicing, symbolic execution, refactoring, decompilation, and obfuscation.
- Program analysis techniques that are used to drive program/model manipulation such as: abstract interpretation, termination checking, binding-time analysis, constraint solving, type systems, automated testing and test case generation.
- Techniques that treat programs/models as data objects including metaprogramming, generative programming, embedded domain-specific languages, program synthesis by sketching and inductive programming, staged computation, and model-driven program generation and transformation.
- Application of the above techniques including case studies of program manipulation in real-world (industrial, open-source) projects and software development processes, descriptions of robust tools capable of effectively handling realistic applications, benchmarking. Examples of application domains include legacy program understanding and transformation, DSL implementations, visual languages and end-user programming, scientific computing, middleware frameworks and infrastructure needed for distributed and web-based applications, resource-limited computation, and security.
To maintain the dynamic and interactive nature of PEPM, we will
continue the category of `short papers' for tool demonstrations and
for presentations of exciting if not fully polished research, and of
interesting academic, industrial and open-source applications that are
new or unfamiliar.
Student attendants with accepted papers can apply for a SIGPLAN PAC
grant to help cover travel expenses and other support. PAC also
offers other support, such as for child-care expenses during the
meeting or for travel costs for companions of SIGPLAN members with
physical disabilities, as well as for travel from locations outside
of North America and Europe. For details on the PAC programme,
see its
web page.
All accepted papers, short papers included, will appear in formal
proceedings published by ACM Press. In addition to printed
proceedings, accepted papers will be included in the
ACM Digital Library.
Selected papers will be invited for a journal special issue
of Science of Computer Programming dedicated to PEPM'13.
PEPM has established a Best Paper award. The winner will be announced
at the workshop.
Authors must transfer copyright to ACM upon acceptance (for government
work, to the extent transferable), but retain various rights. Authors
are encouraged to publish auxiliary material with their paper (source
code, test data, etc.); they retain copyright of auxiliary material.
The
SIGPLAN Republication Policy and
ACM's Policy and Procedures on Plagiarism apply.
Follow this link for the complete
Call for Papers.
There is also a more compact
plain-text version.
History
Previous Meetings
Journal Special Issues
Statistics