1 / 12

How to Write a Technical Report?

Learn how to write an effective technical report by understanding the proper structure, format, and content guidelines. This report provides step-by-step instructions, tips, and examples for each section, including abstract, introduction, related works, problem definition, main works, analysis and experiments, conclusions, and bibliography.

smithmartin
Download Presentation

How to Write a Technical Report?

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. How to Write a Technical Report? Yu-Chee Tseng CS/NCTU

  2. Structure and Format • Authors/Affiliations • Abstract • Keywords • Sections • References

  3. Abstract • Goals • Contributions • Main Approaches … something that one can remember after reading once

  4. Section Arrangement • Introduction • Related Works • Problem Definition • Main Works (1-3 sections, such as Algorithms, Protocols, Maths, etc.) • Analysis • Experiments, Simulations, Prototyping • Conclusions

  5. Introduction • technical trends (with citations) • applications (with citations) • user scenarios (with citations) • general related works (with citations) • specific related works (with citations) • my goal • my achievement • outline of this report

  6. Related Works • generally related • specifically related • highly related (which we will compare to) • classification of related works

  7. Problem Definition • Statement of the problem to be solved • Use of symbols, notations, equations are very important. • Objective: such as maximize/minimize something • Evaluation metrics (such as speed, network throughput, power consumption, etc.)

  8. Main Work • Around 1 to 3 sections • algorithms, protocols, etc. • Be well-structured • top-down • give overall architecture • step-by-step

  9. Analysis/Simulation/etc. • 1 to 2 sections about • math, analytical results • experimental results • simulation results • prototyping, testing results • Comparison targets • at least 1, but not too many

  10. Conclusions • 1 – 3 paragraphs • what you have done (being proud of) • how come it is better • future directions

  11. Bibliography • 10 to 40 references • be aware of the format

  12. Homework #0 • 請上網找一至三篇IEEE Transactions on Mobile Computing論文, 寫一份有關論文大綱的報告.

More Related