abstact guidelines技术摘要写作指南.pptVIP

Writing technical Abstract 05/10/2004 Title * * ? Title, Author(s) ? Abstract – (100-200 words) ? Introduction ? Related work ? Body – Problem, Approach, Results ? Conclusions, summary, future work ? Acknowledgements ? References ? Appendix Contents of a Technical Paper Abstracts are found at the beginning of journal articles, research papers, reports, theses, and dissertations. Because on-line search databases typically contain only abstracts, it is vital to write a complete but concise description of your work to entice potential readers into obtaining a copy of the full paper. Despite the fact that an abstract is quite brief, it must do almost as much work as the multipaper that follows it. In a computer architecture paper, this means that it should in most cases include the following sections. Each section is typically a single sentence, although there is room for creativity. In particular, the parts may be merged or spread among a set of sentences. Use the following as a checklist for your next abstract ： Checklist of Abstract Motivation （selective ) : Why do we care about the problem and the results? If the problem isnt obviously interesting it might be better to put motivation first; but if your work is incremental progress on a problem that is widely recognized as important, then it is probably better to put the problem statement first to indicate which piece of the larger problem you are breaking off to work on. This section should include the importance of your work, the difficulty of the area, and the impact it might have if successful. Problem statement: What problem are you trying to solve? What is the scope of your work (a generalized approach, or for a specific situation)? Be careful not to use too much jargon. In some cases it is appropriate to put the problem statement before the motivation, but usually this only works if most readers already understand why the problem is important. Approach: How did you go about solving