Lecture 5 Technical Presentations, Program Guides, & Abstracts

Front 1

Why publish & present technical papers?

Back 1

• Archives your research findings
• Validation of research by a community ofpeers (peer reviewed, Q/A at meetings, written responses)
• Gives funding agencies confidence insupporting you
• Motivates you with a milestone and reward
  

Front 2

Abstract/Executive Summary

Back 2

• Brief summary of the work (150-300 words)
• Contains a specific, numerical summary of the work.
• Must stand alone--Does not contain figures or tables
• Must contain results!!!
• The last thing to be written, although positioned at the front of the report—why?
  

Front 3

Abstracts

Back 3

• Published separate (and with) paper
• Used to get included in a technical session at a conference
• Used to advertise talk at a conference
• Used to achieve a paper– Engineering Index/Village
• Used to advertise the paper (freeware or charge)
  

Front 4

What does STLE stand for?

Back 4

Society of Tribologists & Lubrication Engineers

Front 5

Timeline for a May Meeting

Back 5

• AbstractDeadline (October)
• Reviewof abstracts (30 days)
• Draftof paper if abstract is accepted (December)
• Paperreviewed by as many as 3 peers—professional obligation to help review papersand role of session chair
• Paperreturned to author with comments (February)
• FinalDraft of paper due 3 months before conference
  

Front 6

Publications & Abstracts

Back 6

• EngineeringIndex—a yearly index of topics that leads you to abstracts and publicationinformation
• On-linedatabases
  

Front 7

Write to your audience: Reference Source

Back 7

• NASATM 105418 TechnicalReport Writing
• ASMEReport Writing Standards
• IEEEReport Writing Standards
• Strunckand White Elements of Style