怎么写论文摘要

How to Write an Abstract

PhilipKoopman, Carnegie Mellon University
October, 1997

Abstract

Because on-line search databases typically contain only abstracts, it isvital to write a complete but concise description of your work to enticepotential readers into obtaining a copy of the full paper. This articledescribes how to write a good computer architecture abstract for bothconference and journal papers. Writers should follow a checklist consisting of:motivation, problem statement, approach, results, and conclusions. Followingthis checklist should increase the chance of people taking the time to obtainand read your complete paper.

Introduction

Now that the use of on-line publication databases is prevalent, writing areally good abstract has become even more important than it was a decade ago.Abstracts have always served the function of "selling" your work. Butnow, instead of merely convincing the reader to keep reading the rest of theattached paper, an abstract must convince the reader to leave the comfort of anoffice and go hunt down a copy of the article from a library (or worse, obtainone after a long wait through inter-library loan). In a business context, an"executive summary" is often the only piece of a report readby the people who matter; and it should be similar in content if not tone to ajournal paper abstract.

Checklist: Parts of an Abstract

Despite the fact that an abstract is quite brief, it must do almost as muchwork as the multi-page paper that follows it. In a computer architecture paper,this means that it should in most cases include the following sections. Eachsection 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. Usethe following as a checklist for your next abstract:

  • Motivation:
    Why do we care about the problem and the results? If the problem isn'tobviously "interesting" it might be better to put motivation first;but if your work is incremental progress on a problem that is widely recognizedas important, then it is probably better to put the problem statement first toindicate 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 thearea, and the impact it might have if successful.
  • Problem statement:
    What problem are you trying to solve? What is the scope of yourwork (a generalized approach, or for a specific situation)? Be careful not touse too much jargon. In some cases it is appropriate to put the problemstatement before the motivation, but usually this only works if most readersalready understand why the problem is important.
  • Approach:
    How did you go about solving or making progress on the problem? Did youuse simulation, analytic models, prototype construction, or analysis of fielddata for an actual product? What was the extent of your work (did youlook at one application program or a hundred programs in twenty differentprogramming languages?) What important variables did you control,ignore, or measure?
  • Results:
    What's the answer? Specifically, most good computer architecture papersconclude that something is so many percent faster, cheaper, smaller, orotherwise better than something else. Put the result there, in numbers. Avoidvague, hand-waving results such as "very", "small", or"significant." If you must be vague, you are only given license to doso when you can talk about orders-of-magnitude improvement. There is a tensionhere in that you should not provide numbers that can be easily misinterpreted,but on the other hand you don't have room for all the caveats.
  • Conclusions:
    What are the implications of your answer? Is it going to change theworld (unlikely), be a significant "win", be a nice hack, or simplyserve as a road sign indicating that this path is a waste of time (all of theprevious results are useful). Are your results general, potentiallygeneralizable, or specific to a particular case?

Other Considerations

An abstract must be a fully self-contained, capsule description of thepaper. It can't assume (or attempt to provoke) the reader into flipping throughlooking for an explanation of what is meant by some vague statement. It mustmake sense all by itself. Some points to consider include:

  • Meet the word count limitation. If your abstract runs too long, either itwill be rejected or someone will take a chainsaw to it to get it down to size.Your purposes will be better served by doing the difficult task of cuttingyourself, rather than leaving it to someone else who might be more interestedin meeting size restrictions than in representing your efforts in the bestpossible manner. An abstract word limit of 150 to 200 words is common.
  • Any major restrictions or limitations on the results should be stated, ifonly by using "weasel-words" such as "might","could", "may", and "seem".
  • Think of a half-dozen search phrases and keywords that people looking foryour work might use. Be sure that those exact phrases appear in your abstract,so that they will turn up at the top of a search result listing.
  • Usually the context of a paper is set by the publication it appears in (forexample, IEEE Computer magazine's articles are generally about computertechnology). But, if your paper appears in a somewhat un-traditional venue, besure to include in the problem statement the domain or topic area that it isreally applicable to.
  • Some publications request "keywords". These have two purposes.They are used to facilitate keyword index searches, which are greatly reducedin importance now that on-line abstract text searching is commonly used.However, they are also used to assign papers to review committees or editors,which can be extremely important to your fate. So make sure that the keywordsyou pick make assigning your paper to a review category obvious (for example,if there is a list of conference topics, use your chosen topic area as one ofthe keyword tuples).

Conclusion

Writing an efficient abstract is hard work, but will repay you withincreased impact on the world by enticing people to read your publications.Make sure that all the components of a good abstract are included in the nextone you write.

Further Reading

Michaelson, Herbert, How to Write & Publish Engineering Papers andReports, Oryx Press, 1990. Chapter 6 discusses abstracts.

Cremmins, Edward, The Art of Abstracting 2nd Edition, Info ResourcesPress, April 1996. This is an entire book about abstracting, written primarilyfor professional abstractors.

Translations of this article:


<think>好的,用户想了解如何撰学术论文摘要,包括示例和技巧。首先需要明确摘要的基本结构和目的,通常包括研究背景、方法、结果和结论。接下来要确定用户可能需要具体的步骤或方法,比如各部分应包含什么内容,长度限制,以及常见错误避免。 然后,考虑用户可能需要示例来更好地理解。需要搜索一些典型的摘要例子,分析它们的结构,指出每个部分的关键点。同时,技巧部分可能包括使用主动语态、避免专业术语过多、保持简洁等。 还要注意用户可能混淆摘要和引言,需要明确两者的区别。另外,格式要求如字数限制、关键词的使用也是重要点。需要检查是否有最新的学术规范或不同学科的特殊要求,比如科学论文和人文科学摘要的差异。 可能还需要提醒用户避免在摘要中引用文献,以及如何突出研究的创新点。最后,确保回答结构清晰,分点说明,每个方法或步骤之间有换行,符合用户的格式要求。相关问题需要基于用户的问题和回答内容,比如如何选择关键词、摘要和引言的区别、不同学科的摘要特点等。</think>学术论文摘要需要遵循结构化表达原则,通常包含研究目的、方法、结果和结论四个核心要素。国际标准ISO 214规定摘要应具备独立性、自明性,字数控制在200-300单词为宜。 **典型结构示例** 临床医学论文摘要模板: ``` 背景:糖尿病发病率持续上升,现有检测方法存在局限性 方法:开发基于纳米粒子的荧光传感器,纳入120例样本进行双盲测试 结果:灵敏度达98.2%,特异性96.5%,检测时间缩短至15分钟 结论:新方法为早期筛查提供有效工具 ``` 计算机科学论文摘要片段: ``` 提出改进的残差网络架构ResNet-3D,在UCF101数据集上测试,准确率提升7.2% 采用三维卷积核捕捉时序特征,参数量减少18% ``` **关键技巧** - 动词使用主动语态:"本研究设计"优于"被设计" - 数值精确呈现:$P<0.01$, $R^2=0.87$ - 避免缩略语首次出现不解释:先"随机对照试验(RCT)" - 突出创新点:用"首次"、"创新性"等限定词 - 关键词密度保持3-5%,符合学术搜索引擎优化要求 **常见错误修正对照** 原始句:"做了很多实验证明效果不错" 修正后:"通过30组对比实验验证,处理效率提升42%($p<0.05$)" 机器学习领域摘要公式化表达: $$Acc = \frac{TP+TN}{TP+TN+FP+FN} \times 100\%$$ 其中TP表示真阳性,TN为真阴性,需在方法部分明确定义。 ```latex % LaTeX摘要排版示例 \begin{abstract} \textbf{Background}: Rising demand for... \textbf{Methods}: We propose... \textbf{Results}: Experimental results show... \textbf{Conclusion}: This framework provides... \keywords{keyword1, keyword2} \end{abstract} ```
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值