寄托天下
楼主: lghscu
打印 上一主题 下一主题

[综合备考指导] 【1006G】【习惯性GRE】--【备考日记】--方法+经验+毅力 [复制链接]

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

271
发表于 2010-2-23 21:05:24 |只看该作者
本帖最后由 lghscu 于 2010-2-24 21:14 编辑

How to... write an abstract

In this section
What is an abstract?
A definition
An abstract is a succinct summary of a longer piece of work, usually academic in nature, which is published in isolation from the main text and should therefore stand on its own and be understandable without reference to the longer piece. It should report the latter's essential facts, and should not exaggerate or contain material that is not there.

Its purpose is to act as a reference tool (for example in a library abstracting service), enabling the reader to decide whether or not to read the full text.

Two common reasons for writing an abstract are

  • to summarize a longer piece of work published as a journal article, thesis, book or web page, an existing article for the purposes of a journal,
  • or to submit an application to write a paper for a conference.

In both cases, you will be given specific guidelines as to how to write the abstract including a maximum word count from either the relevant publisher or the organizer of the conference; those for Emerald are set out below. Conference papers are usually selected on the basis of abstracts: see tips below.

How to go about the writing process

  • Start by writing a statement of the paper's purpose, which should be as succinct as possible. If you include background keep this to a minimum and only include such information as to provide a context.
  • Summarize the paper, reporting its main facts. Remember the following points:
    • Follow the chronology of the paper and use its headings as guidelines.
    • Do not include unnecessary detail, as in the first example in "How not to write an abstract".
    • You are writing for an audience "in the know" – you can use the technical language of your discipline or profession, providing you communicate your meaning clearly, and bear in mind that you are writing to an international audience.
    • Make sure that what you write "flows" properly, that there are "connecting words" (e.g. consequently, moreover, for example, the benefits of this study, as a result, etc.) and/or the points you make are not disjointed but follow on from one another.
    • Use the active rather than the passive voice, e.g. "The study tested" rather than "It was tested in this study".
    • The style of writing should be dense, and sentences will probably be longer than usual.
  • You should by now have a draft, which will probably be too long. Here are some points to remember in cutting:
    • cut out any unnecessary words that do not add to the meaning, but
    • make sure that the abstract is not so "cut" as to be unreadable; use full sentences, direct and indirect articles, connecting works, etc. An abstract should use continuous prose, not notes.

  • Read through your draft, making sure that it covers the main points listed above, and that there are no grammatical, spelling or typographical errors, also that it "flows" properly.
  • If possible, get a colleague to read through your abstract as a form of "peer review".
  • Submit!

If you have difficulty with the general purpose statement or with summarizsing your article, it may be because the article's general concept is not that clear, or perhaps your research design or approach needs revisiting.

Instructions for writing a structured abstract for EmeraldEmerald has introduced a new format for article abstracts intended to help researchers by consistently providing the most useful information. Each abstract is made up of a number of set elements. An example is provided at the foot of this page.

1. Write the abstract
To produce a structured abstract for the journal and Emerald database, please complete the following fields about your paper. There are four fields which are obligatory (Purpose, Design/methodology/approach, Findings and Originality/value); the other three (Research limitations/implications, Practical implications, and Social implications) may be omitted if they are not applicable to your paper.
Abstracts should contain no more than 250 words. Write concisely and clearly. The abstract should reflect only what appears in the original paper.

Purpose
What are the reason(s) for writing the paper or the aims of the research?

Design/methodology/approach
How are the objectives achieved?

Include the main method(s) used for the research.

What is the approach to the topic and what is the theoretical or subject scope of the paper?
Findings
What was found in the course of the work? This will refer to analysis, discussion, or results.
Research limitations/implications (if applicable)
If research is reported on in the paper this section must be completed and should include suggestions for future research and any identified limitations in the research process.
Practical implications (if applicable)
What outcomes and implications for practice, applications and consequences are identified? How will the research impact upon the business or enterprise? What changes to practice should be made as a result of this research? What is the commercial or economic impact? Not all papers will have practical implications.
Social implications (if applicable)
What will be the impact on society of this research? How will it influence public attitudes? How will it influence (corporate) social responsibility or environmental issues? How could it inform public or industry policy? How might it affect quality of life? Not all papers will have social implications.
Originality/value
What is new in the paper? State the value of the paper and to whom.

2. Using keywords
Using keywords is a vital part of abstract writing, because of the practice of retrieving information electronically: keywords act as the search term. Use keywords that are specific, and that reflect what is essential about the paper. Put yourself in the position of someone researching in your field: what would you look for? Consider also whether you can use any of the current "buzz words".

3. Choose a category for the paper
Pick the category which most closely describes your paper. We understand that some papers can fit into more than one category but it is necessary to assign your paper to one of the categories – these are listed and will be searchable within the database:

  • Research paper. This category covers papers which report on any type of research undertaken by the author(s). The research may involve the construction or testing of a model or framework, action research, testing of data, market research or surveys, empirical, scientific or clinical research.
  • Viewpoint. Any paper, where content is dependent on the author's opinion and interpretation, should be included in this category; this also includes journalistic pieces.
  • Technical paper. Describes and evaluates technical products, processes or services.
  • Conceptual paper. These papers will not be based on research but will develop hypotheses. The papers are likely to be discursive and will cover philosophical discussions and comparative studies of others' work and thinking.
  • Case study. Case studies describe actual interventions or experiences within organizations. They may well be subjective and will not generally report on research. A description of a legal case or a hypothetical case study used as a teaching exercise would also fit into this category.
  • Literature review. It is expected that all types of paper cite any relevant literature so this category should only be used if the main purpose of the paper is to annotate and/or critique the literature in a particular subject area. It may be a selective bibliography providing advice on information sources or it may be comprehensive in that the paper's aim is to cover the main contributors to the development of a topic and explore their different views.
  • General review. This category covers those papers which provide an overview or historical examination of some concept, technique or phenomenon. The papers are likely to be more descriptive or instructional ("how to" papers) than discursive.
Tips for writing abstracts for conference papers
The difficulty here is that you will probably be writing the abstract as a preamble to the actual paper, rather than subsequent to it. Here are some points to remember:

  • Clarify in your own mind what is the purpose of the paper: what it is that you are going to do.
  • Look carefully at the themes of the conference: note those that apply and frame your paper accordingly.
  • Very often, the submission procedure will dictate the format and the number of words of the abstract. For example:
    • Title
    • Name of presenter, contact details
    • Category of presentation (e.g. workshop, research paper, short paper, poster etc.)
    • Conference themes addressed.
    • Key words that will help people deciding whether or not to participate to understand its focus.
    • Objectives/intended outcomes and activities for participants
    • The abstract.
  • Stick closely to the length given. You will often have no choice in this matter, because if you submit electronically you will find yourself cut off in mid sentence as you reach the required limit.
  • When writing the abstract, ask yourself the following questions:
    • What is the purpose of my paper? This should, as with any abstract, be a general definition statement about the objectives of your paper.
    • What approach am I using? I.e. am I reviewing the literature, describing a case study, supporting a research hypothesis, and if the latter, what is my research design and research methodology?
    • What are my findings?
    • What is the import of my findings?
  • Choose your keywords carefully, making sure that they match the themes of the conference.
Some examples of abstracts Below find some examples of structured abstracts for the various categories of Emerald articles. The keywords are also listed. Note that we have deliberataley chosen older articles so that you can compare the structured abstracts supplied below with the unstructured abstracts required at the time of publication (just click on the article link).
Structured abstract examples in this section
Example of a structured abstract for a literature review
Surviving and thriving in academia:
a selective bibliography for new faculty members

Deborah Lee
Reference Services Review
Vol. 31 No. 1
Literature review
Purpose
To provide a selective bibliography for graduate students and new faculty members with sources which can help them develop their academic career.
Design/methodology/approach
A range of recently published (1993-2002) works, which aim to provide practical advice rather than theoretical books on pedagogy or educational administration, are critiqued to aid the individual make the transition into academia. The sources are sorted into sections: finding an academic job, general advice, teaching, research and publishing, tenure and organizations.
Findings
Provides information about each source, indicating what can be found there and how the information can help. Recognises the lack of real training of many academics before they are expected to take on teaching/researching duties and finds some texts which help.
Research limitations/implications
It's not an exhaustive list and apart from one UK book all the rest are US publications which perhaps limits its usefulness elsewhere.
Practical implications
A very useful source of information and impartial advice for graduate students planning to continue in academia or for those who have recently obtained a position in academia.
Originality/value
This paper fulfils an identified information/resources need and offers practical help to an individual starting out on an academic career.
Keywords: Bibliography, Higher education, Teachers, Academic staff, Research, Publishing
Examples of structured abstracts for case studies Cash to accrual and cash to accrual:
a case study of financial reporting in two NSW hospitals 1857 to post-1975

Julie E.M. Scott, Jill L. McKinnon and Graeme L. Harrison
Accounting, Auditing and Accountability Journal
Vol. 16 No. 1
Case study
Purpose
This study traces the development of financial reporting in two publicly funded hospitals in New South Wales over the period 1857 to post-1975, with particular focus on the use of cash and accrual accounting.
Design/methodology/approach
The historical analysis draws on process and conceptual change and stakeholder theory, and uses both primary and secondary data,
Findings
to describe patterns of change (and non-change) in the hospital's financial reporting and to identify the social and political influences associated with such reporting.
Originality/value
This study provides historical context for recent developments in public sector reporting and accountability in Australia, particularly the (re)introduction of accrual accounting, and provides insights into the nature of accounting change both in public sector organisations and generally.
Keywords: Public sector accounting, Financial reporting, Hospitals, Accounting history, Analysis, Stakeholders, Australia
A comparative analysis of vertical integration in the UK brewing and petrol industries
Gary Cook
Journal of Economic Studies
Vol. 24 No. 3
Case study
Purpose
Looks fundamentally at the reasons for vertical integration. Specifically addresses the question of why vertical integration and close contractual equivalents have arisen in the petrol and brewing sectors of the UK.
Design/methodology/approach
Reports the results of a comparative case study. Considers the ability of power and efficiency explanations to account for both the current pattern of vertical integration and its changes over time.
Findings
Principally concludes the following: the recent history of vertical integration is better accounted for by efficiency rationales in the case of petrol and by market power in the case of brewing. Nevertheless, elements of both are present in each industry.
Practical implications
particularly the (re)introduction of accrual accounting, and provides insights into the nature of accounting change both in public sector organisations and generally.
Originality/value
Given the strong similarity in vertical and horizontal industry structure between these sectors, this implies that a case by case approach is preferable to a form-based approach.
Keywords: Brewing industry, Petrol, Transaction costs, Vertical integration
Example of a structured abstract for a conceptual paper  The changing internal market for ethical discourses in the Canadian CA profession
Dean Neu, Constance Friesen and Jeffery Everett
Accounting, Auditing and Accountability Journal
Vol. 16 No. 1
Conceptual paper
Purpose
Starting from the premise that formal ethical codes and other ethical discourses differ in their audiences, effects and characteristics, analyses how practitioner-directed ethical discourses have spoken and continued to speak about character-based ethics.
Design/methodology/approach
Borrowing from the literature on professions and Pierre Bourdieu's theory of practice, starts from the assumption that editorials in practitioner-orientated publications are a form of cultural good traded on an internal symbolic market. By providing access to symbolic capital, trade in this good acts to bind together members of the accounting profession, yet trade in this good also has the potential to obscure a number of important, underlying social issues. The study is based on a close (textual) reading of editorials in the Canadian Chartered Accountant (subsequently renamed CA Magazine) from 1911 to 1999, and this reading is framed in the light of a number of macro-level and meso-level (contextual) changes.
Findings
It is found that character-based ethical discourses continue to pervade this professional field.
Originality/value
These discourses, however, do not continue without important changes that themselves need to be explained in light of the more widespread, non-professional field.
Keywords: Accountants, Ethics, Professionalism, Canada
Example of a structured abstract for a research paper Structuring international service operations: a theoretical framework and a case study in the IT-sector
Bert Meijboom and Migon Houtepen
International Journal of Operations & Production Management
Vol. 22 No. 8


Research paper
Purpose

What are the reason(s) for writing the paper or the aims of the research?
The specific challenges with which companies pursuing international manufacturing strategies are faced, if their output also contains a service dimension, are addressed.

Design/methodology/approach

How are the objectives achieved?

Include the main method(s) used for the research.

What is the approach to the topic and what is the theoretical or subject scope of the paper?

A theoretical framework is proposed based on three virtually complementary perspectives by integrating international production, demand, and contemporary ICT-based theory. Subsequently, an exploratory case study in a pure service environment is described that illustrates the value of the framework.


Findings

Findings
What was found in the course of the work? This will refer to analysis, discussion, or results.
It is possible, for example, to apply the theoretical framework to case studies in internationally-operating companies delivering a mix of goods and services.
Research limitations/implications

If research is reported on in the paper this section must be completed and should include suggestions for future research and any identified limitations in the research process.

The present study provides a starting-point for further research in the international manufacturing sector.


Originality/value
What is new in the paper? State the value of the paper and to whom.

Moreover, the framework has proven to be useful in improving the European structure of the case company. This is a notable and promising side-effect of the exploratory study, at least from a managerial point of view.


Keywords: Multinationals, Service operations, Location, Decision making, Case studies

Example of a structured abstract for a general review Prioritising for healthy schools activities:
an initial review exercise

Fenella Starkey and Judy Orme
Health Education
Vol. 100 No. 4
General review
Purpose
This paper focuses on one aspect of Health Promotion Service Avon's Schools for Health Project 1997/98, which is the development, implementation, analysis and evaluation of an initial review questionnaire completed by teachers, non-teaching staff, parents and pupils. This provided a baseline audit tool in 13 schools.
Design/methodology/approach
The initial review questionnaire covered topics within the areas of environment, school ethos, staff and pupil wellbeing, curriculum and community.
Findings
Benefits arising from the initial review exercise identified by schools included: giving all school members the chance to put their views across; engaging people in the project and raising awareness of the school's involvement in the project; and giving legitimacy to concerns raised informally by staff.
Practical implications
The importance of ensuring that any questionnaire given to non-teaching staff and pupils is "jargon-free" and "user-friendly" was highlighted by some of the teachers involved.
Originality/value
Helped schools to identify areas for development via the project.

Keywords: Schools, Evaluation, Health, Education, Assessment
How not to write an abstract: examples of poor abstractsWhat is an abstract? One of the best ways of learning to write good abstracts is to look at other people's mistakes. Review the three abstracts below, and compare your reactions to our own comments.

Abstract 1Computer Assisted Learning (CAL) is an area which is rapidly expanding amongst Higher Education institutions as the power of available hardware rises facilitating new and innovative HE teaching and learning environments. The University Institute of recently allocated funds to stimulate a learning technology program which was generally intended to impinge on all 4 Faculties within the insititution. Each faculty was asked to bring forward, software development schemes and bids for equipment and other, necessary resources such as human resources, consumables, etc. The purpose of this paper is to describe the experience of a team of academics in the Department of French, School of Modern Languages within the Faculty of Arts, Humanities and Social Studies at the University Institute of in the development of a Computer-assisted learning software program. Funding was made available from a central source to develop and implement a software program to assist French language learners to acquire vocabulary in "an innovative and measurably effective manner". The software was implemented and tested on a cohort of level 2 students who had, in general, studied French for 8 years, and staff and students were consulted with regards to their reactions.
Permission to use this article is granted by Professor Gabriel Jacobs at the University of Swansea

Comments on Abstract 1Half the abstract is taken up with unnecessary background information about the funding. The full title of the department is unnecessary detail. All this is very wordy, and doesn't relate to what the paper is about. The "purpose" statement could be rephrased: "This paper describes the evaluation of a piece of software designed to assist the acquisition of French vocabulary with a group of level 2 students". There needs to be more description of the methodology – how many students? How was the testing done? What, precisely, was evaluated? What were the findings, and what are the implications of the findings? The language used is vague – what is meant by "other, necessary resources such as human resources, consumables, etc.", what was "demonstrably efficient" about the style of learning? What was the nature of the consultation with staff and students? There are also a number of grammatical errors, e.g. commas in the wrong places (substantiate, software development). "Mock posh" language is used, i.e. the reference to academics (don't need to use this word unless differentiating from administrators). In short, the abstract contains much information which is of only marginal importance, and merely repeats, almost word for word, what is in the body text; the syntax and punctuation is often defective, verbose and trying too hard to write in an "academic" manner. True of much of the paper.

Abstract 2Reviews the manufacturing and processing challenges involved in the later stages of the manufacture of large area full frontal wire mesh coating and describes some of the techniques employed by CSW Packaging Solutions.

Comments on Abstract 2This abstract is far too short and does not provide enough information about the paper. It describes the purpose of the paper and its main subject but gives us nothing on what was done (method) or on results. Specifically, it could have listed the "techniques" mentioned, provided some of the key criticisms and then gone on to implications for practice, i.e. recommendations.

Abstract 3In this article, research as "mass media" (Lerhmann) is appraised. "Videocy" or videoed research results are examined. A form of video research with its roots in action research, Cabalistic methodology and oral anthropology is reported on. The counterparts it produces, wherein disclosure loops are used to produce an effect similar to the fractalizations of reality, achieves a powerful simulation of reality. But is it a "responsible" form of (research) practice?

Comments on Abstract 3We are given the paper's purpose but nothing about the methodology and it doesn't explain the scope of the study. It's too short and last but not least, it leaves us with a question!! No summary or results or conclusions are given. An abstract shouldn't be like an advertisement or cliff hanger in a TV serial. The language is abstruse, it's not long enough, and out of context it's fairly meaningless.

Printed from: http://info.emeraldinsight.com/authors/guides/abstracts.htm
on Tuesday February 23rd, 2010

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

272
发表于 2010-2-23 21:06:47 |只看该作者
[size=+1]HOW TO WRITE AN ABSTRACT: [size=+1]Links and Tips

An abstract is a short summary of your completed research. If done well, it makes the reader want to learn more about your research.
These are the basic components of an abstract in any discipline:
1) Motivation/problem statement: Why do we care about the problem? What practical, scientific, theoretical or artistic gap is your research filling? 2) Methods/procedure/approach: What did you actually do to get your results? (e.g. analyzed 3 novels, completed a series of 5 oil paintings, interviewed 17 students)
3) Results/findings/product: As a result of completing the above procedure, what did you learn/invent/create?
4) Conclusion/implications: What are the larger implications of your findings, especially for the problem/gap identified in step 1?
However, it's important to note that the weight accorded to the different components can vary by discipline. For models, try to find abstracts of research that is similar to your research.

[size=+1]Below are links and sample abstracts that you may find helpful.
[size=+1]LINKS:
This link has a very thorough description of each of the components named above. It is aimed especially at engineers but is relevant for all disciplines.
http://www.ece.cmu.edu/~koopman/essays/abstract.html
This link is especially relevant for natural scientists:
http://darwin.bio.uci.edu/~sustain/Abstract.html

[size=+1]SAMPLE ABSTRACTS:
History/social science:
"Their War": The Perspective of the South Vietnamese Military in Their Own Words Author: Julie Pham (UCB participant in UC Day 2001)
Despite the vast research by Americans on the Vietnam War, little is known about the perspective of South Vietnamese military, officially called the Republic of Vietnam Armed Forces (RVNAF). The overall image that emerges from the literature is negative: lazy, corrupt, unpatriotic, apathetic soldiers with poor fighting spirits. This study recovers some of the South Vietnamese military perspective for an American audience through qualititative interviews with 40 RVNAF veterans now living in San José, Sacramento, and Seattle, home to three of the top five largest Vietnamese American communities in the nation. An analysis of these interviews yields the veterans' own explanations that complicate and sometimes even challenge three widely held assumptions about the South Vietnamese military: 1) the RVNAF was rife with corruption at the top ranks, hurting the morale of the lower ranks; 2) racial relations between the South Vietnamese military and the Americans were tense and hostile; and 3) the RVNAF was apathetic in defending South Vietnam from communism. The stories add nuance to our understanding of who the South Vietnamese were in the Vietnam War. This study is part of a growing body of research on non-American perspectives of the war. In using a largely untapped source of Vietnamese history &endash; oral histories with Vietnamese immigrants &endash; this project will contribute to future research on similar topics.
Humanities:
Violence, Subalternity, and El Corrido Along the US/Mexican Border Author: Roberto Hernandez (UCB participant in UC Day 2001)
The Geopolitical divide that separates the United States and Mexico has long plagued the region with violence and conflict. However, its extent and political nature is often overshadowed and undermined by mainstream information outlets. The boundary inspires polarized reactions: tough on crime/immigration rhetoric from politicians and enforcement officials &endash; exemplified in current border militarization &endash; and appeasement through feel-good news reporting. Such contradictions desensitize and deny the essence and root cause of the conflict &endash; an ongoing sociopolitical, cultural, and economic struggle between the two nations. While information transmission in the north has a U.S. focus, south of the divide knowledge distribution is very Mexico-centered. However, the border region acts as a third space t hat gives birth to a distinct border gnosis, a unique form of knowledge construction among subaltern communities on both its sides. One form of subalternity, corridos, (border folk ballads), has functioned to create an alternative discourse to the borderlands imaginary. This study is an examination of the analysis and critique found in corridos that seek a critical approach to the violence at the nations' shared edges and its ensuing political implications. To illustrate their subaltern function, I will examine two incidents: the 1984 McDonalds shooting in San Ysidro, California, and the 1997 death of Ezequiel Hernández in Redford, Texas. these cases are indicative of the politically charged environment of a border region that in becoming an increasingly militarized zone has also set the stage for a cultural battle amongst different forms of knowledge construction and legitimation.
Biological Sciences:
"The Listeria monocytogenes p60 Protein is not Essential for Viability in vitro, but Promotes Virulence in vivo" Author: Sina Mohammedi, 2002 UC Day nominee and runner-up
Intracellular pathogens (agents which infect host cells), such as Mycobacterium tuberculosis and Listeria monocytogenes, cause very high mortality rates in the United States. Therefore, deciphering the mechanisms through which the pathogens cause disease is of great interest. Listeria infection of mice is a well-developed model system for studying the fundamentals of host-pathogen interactions. In vitro assays in animal cell cultures have helped show that Listeria causes illness by secreting molecules, called virulence factors, to the outside of the bacterial cell in order to affect the host organism. My work involves one such secreted protein, called p60. P60 is an antigen (an agent seen by the host immune system) implicated in regulated bacterial cell wall breakdown. The objective of this study was to examine two questions: first, is p60 essential to the viability of Listeria, as previously published? and second, is p60 a virulence factor in Listeria? To examine these questions, I contructed a Listeria strain lacking p60 (p60-). This new strain displayed no defect in viability. In fact, most standard in vitro pathogenicity assays were normal for p60-. However, when p60- was tested in a mouse (in vivo), a 1000-fold reduction in virulence was observed. This discovery suggests that p60 is indeed a key factor in the disease-causing ability of Listeria, but not essential for viability. Future studies will focus on the precise role of p60 in Listeria pathogenesis. This work increases our understanding of such diseases as tuberculoses, various food poisonings, and meningitis.
Engineering:
"Quantifying the Mechanics of a Laryngoscopy" Laryngoscopy is a medical procedure that provides a secure airway by passing a breathing tube through the mouth and into the lungs of a patient. The ability to successfully perform laryngoscopy is highly dependent on operator skill; experienced physicians have failure rates of 0.1% or less, while less experienced paramedics may have failure rates of 10-33%, which can lead to death or brain injury. Accordingly, there is a need for improved training methods, and virtual reality technology holds promise for this application. The immediate objective of this research project is to measure the mechanics of laryngoscopy, so that an advanced training mannequin can be developed. This summer an instrumented laryngoscope has been developed which uses a 6-axis force/torque sensor and a magnetic position/orientation sensor to quantify the interactions between the laryngoscope and the patient. Experienced physicians as well as residents in training have used this device on an existing mannequin, and the force and motion trajectories have been visualized in 3D. One objective is to use comparisons between expert and novice users to identify the critical skill components necessary for patients, to identify the mechanical properties of the human anatomy that effect laryngoscopy, and thus enable the development of a realistic training simulator. In the future an advanced training mannequin will be developed whose physical properties will be based on our sensor measurements, and where virtual reality tools will be used to provide training feedback for novice users.
More Sample Undergraduate Research Abstracts in the Arts, Humanities, Science and Social Science:
http://www.sccur.uci.edu/sampleabstracts.html (note: These are not UC Day abstracts. Disregard application instructions on that site.)

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

273
发表于 2010-2-23 21:07:19 |只看该作者
How to Write an Abstract

Philip Koopman, Carnegie Mellon University
October, 1997

AbstractBecause 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. This article describes how to write a good computer architecture abstract for both conference and journal papers. Writers should follow a checklist consisting of: motivation, problem statement, approach, results, and conclusions. Following this checklist should increase the chance of people taking the time to obtain and read your complete paper.
IntroductionNow that the use of on-line publication databases is prevalent, writing a really good abstract has become even more important than it was a decade ago. Abstracts have always served the function of "selling" your work. But now, instead of merely convincing the reader to keep reading the rest of the attached paper, an abstract must convince the reader to leave the comfort of an office and go hunt down a copy of the article from a library (or worse, obtain one after a long wait through inter-library loan). In a business context, an "executive summary" is often the only piece of a report read by the people who matter; and it should be similar in content if not tone to a journal paper abstract.
Checklist: Parts of an AbstractDespite the fact that an abstract is quite brief, it must do almost as much work 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. 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:
  • Motivation:
    Why do we care about the problem and the results? If the problem isn't 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 or making progress on the problem? Did you use simulation, analytic models, prototype construction, or analysis of field data for an actual product? What was the extent of your work (did you look at one application program or a hundred programs in twenty different programming languages?) What important variables did you control, ignore, or measure?
  • Results:
    What's the answer? Specifically, most good computer architecture papers conclude that something is so many percent faster, cheaper, smaller, or otherwise better than something else. Put the result there, in numbers. Avoid vague, hand-waving results such as "very", "small", or "significant." If you must be vague, you are only given license to do so when you can talk about orders-of-magnitude improvement. There is a tension here 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 the world (unlikely), be a significant "win", be a nice hack, or simply serve as a road sign indicating that this path is a waste of time (all of the previous results are useful). Are your results general, potentially generalizable, or specific to a particular case?
Other ConsiderationsAn abstract must be a fully self-contained, capsule description of the paper. It can't assume (or attempt to provoke) the reader into flipping through looking for an explanation of what is meant by some vague statement. It must make sense all by itself. Some points to consider include:
  • Meet the word count limitation. If your abstract runs too long, either it will 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 cutting yourself, rather than leaving it to someone else who might be more interested in meeting size restrictions than in representing your efforts in the best possible manner. An abstract word limit of 150 to 200 words is common.
  • Any major restrictions or limitations on the results should be stated, if only by using "weasel-words" such as "might", "could", "may", and "seem".
  • Think of a half-dozen search phrases and keywords that people looking for your 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 (for example, IEEE Computer magazine's articles are generally about computer technology). But, if your paper appears in a somewhat un-traditional venue, be sure to include in the problem statement the domain or topic area that it is really applicable to.
  • Some publications request "keywords". These have two purposes. They are used to facilitate keyword index searches, which are greatly reduced in 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 keywords you 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 of the keyword tuples).
ConclusionWriting an efficient abstract is hard work, but will repay you with increased 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 next one you write.
Further ReadingMichaelson, Herbert, How to Write & Publish Engineering Papers and Reports, Oryx Press, 1990. Chapter 6 discusses abstracts.
Cremmins, Edward, The Art of Abstracting 2nd Edition, Info Resources Press, April 1996. This is an entire book about abstracting, written primarily for professional abstractors.
© Copyright 1997, Philip Koopman, Carnegie Mellon University

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

274
发表于 2010-2-23 23:00:28 |只看该作者
obnoxious
个人觉得比较难记的词
但今天变了
obviously noxious
很明显XX是noxious
-->很反感,令人反感的,不愉快的

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

275
发表于 2010-2-24 22:08:08 |只看该作者
paper困扰中
继续学习中

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

276
发表于 2010-2-24 23:50:45 |只看该作者
又是红宝的“不能解决的”
tractable<MW:easily handled, managed, or wrought >
adj 易于驾驭的(容易管理或控制的)=malleable
【记】tract拉,able:原指牲口拉得动的-温顺的
【类】complaisance:intractable=adeptness:maladroit柔顺不是倔强的=老练不是笨拙的subtle:overlook=tractable:lead微妙的容易忽略=温顺的容易领导testy:annoy=tractable:control易怒的容易被使苦恼=温顺的容易被控制tame:tractable=?   驯服的不是容易管教的=?
【反】headstrong=obstinate=balky=pertinacious(adj 倔强顽固的);incorrigible(adj 无药可救的);insubordinate=intransigent=recalcitrant(adj 非妥协性的)"

incorrigible<MW:not manageable >
adj 积习难改的;(难以控制的)=ineradicable
【记】corrigible(adj 可改正的;顺从的);correct(adj 正确的vt 改正)
【类】incorrigible:reformed=inscrutable:understood难以纠正的无法被纠正=难以理解的无法被理解incorrigible:amend=irradicable:remove无可救药的无法改正=不能根除的无法移动
【反】tractable(adj 易驾驭的;易处理的)"

纸质“红宝”并没有释义括号内容

MW解释出了
tractable<>incorrigible

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

277
发表于 2010-2-25 21:58:19 |只看该作者
输输更健康

dilatory

adj 有意拖延的;磨蹭的
【记】源于:delay(v /n 拖延;耽搁)di,lat放-放下来不做-有意拖延的lat=late迟到-磨蹭的
【类】dilatory:procrastinate=malcontent:complain拖延的导致耽误=不满的导致抱怨
【反】alacritous(adj 活泼的;敏捷的);precipitate(adj 突如其来的)"

spiny  
adj (表面)多刺的;(事情)棘手的
【记】源于:spine(n 脊椎,刺)
【参】spineless(adj 没骨气的;无脊椎的);spinous(adj 多刺的)
【反】smooth(adj 平滑的)"

stodgy
adj 沉闷平庸的=dull=commonplace
【记】源于:stodge(n 油腻乏味的食物)s,todgy=today:一想到今天会死,感到生活是沉闷平庸的
【类】stodgy:conservative=mawkish:sentimental平庸的:守旧的=容易伤感的:多愁善感的(同义)
【反】exciting(adj 令人兴奋激动的)"

stuffy
adj (空气)不新鲜的;枯燥无味的
【记】stuff(n 原料;v 塞满),y-填满浑浊空气的-气闷的"

complacency  
n.  满足; 安心<到了一个place就“满足,安心”了>

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

278
发表于 2010-2-26 22:40:48 |只看该作者
本帖最后由 lghscu 于 2010-2-26 22:46 编辑
虽然单词的复习书籍这么多和繁复,但是万变不离其中,单词这个东西还是要下功夫的,所谓不日进则日退,每天的坚持很重要,不管你背哪本书,你用什么方法,你的基础如何,你的能力,记忆力怎么样,我觉得大多数人都是要下功夫的~~但是什么方法好呢?? 我推崇的方法是长时间的去背,理由不言自明,这样的效果最好,只要坚持,像有些朋友短时间要考,每天的精力都耗在这个上面,时间精力不少搭,但是效果不见得好(牛人除外,我说的是正常人,大多数人),
...
其实我很主张把自己模考的成绩记录下来,尤其是每次都细致的去分析,考试的时候保持一定的兴奋度和敏感度是很必要的,也是很重要的,这样有助于我们的发挥~~我不建议1周模考很多次,那么会疲劳不说,重要的是把自己的状态都弄没了,我第二次的时候是一天一模考,最后10天过去后,成绩也没什么太大的起色,反而是隔了几天模考一次,效果不错~~~建议一周一次,然后好好总结~~每次把自己的不足记录下来,单词,原因等等,有助于积累自己的信心,也帮助自己调整状态


比较不错的经验
http://bbs.taisha.org/thread-942189-1-1.html

GRE真题集中营
一定要留几套完整的题做模拟考用
http://bbs.taisha.org/thread-688957-1-1.html

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

279
发表于 2010-2-26 22:51:52 |只看该作者
本帖最后由 lghscu 于 2010-2-26 22:58 编辑
如果你想成功,一定要下工夫!这是王道!不要想有什么捷径,背单词尤甚。当你实在背不下去的时候,你可以问问自己:“我到底想不想成功?我是不是真的想到美国去?”如果你的答案是肯定的,那么坚持下去吧!20年后回过头来看我们今天走过的路,我们一定是欣慰的,因为我们没有因虚度自己的青春而后悔!

下个学期真的好忙,有的时候连想都不敢想,因为要干的事实在太多了!不过我会对自己说,再忍忍吧,过去就好了,等有朝一日拿到了OFFER,今天所有付出的所有汗水甚至泪水,都是值得的。我们一起加油!


时间肯定还是特别紧张,那就得靠自己的毅力了,考G的同学肯定比别人要累的多,这就需要坚持了。看谁能拼得过别人,谁就能胜利

我可以很负责任的告诉大家,如果想上500,单词背熟再加上一些做题技巧,绝对没一点问题!我就是属于这一类的。如果verbal想上600,阅读一定要过关!我就是没过关的……呵呵。是这样,词汇过关了,类反没问题,填空没问题,不就剩下阅读了嘛!阅读全错,类反错3个,填空错4个都能上600,况且阅读不可能全错。词汇是可以突击的,阅读绝对不行,这是我的切身体会。

我要600+,所以,阅读+词汇一定要过关

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

280
发表于 2010-2-27 10:35:38 |只看该作者
本帖最后由 lghscu 于 2010-2-27 10:36 编辑


尽量只读一遍完整的文章,不要总是回视,特别是长文章。

尽量一次性完成文章后面的题目,不要检查。

尽量先把自己擅长的题型做出来,对于有罗马数字的题目,一般
来说是比较消耗时间的。

对于短文章,一般要控制在5-6 分钟之内完成,不要过多浪费时


尽管我们说阅读是一个投入和产出不成比例的项目,但是它也有一点好处,
那就是一旦到达了某一水平,即便你很久不背单词,也可以保持在那一个水平。


使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

281
发表于 2010-2-27 10:41:31 |只看该作者
一般来讲,如果你不是时间过于充足,建议只需要将所有的阅读文章(NO

题、国内90-99 题)全部做一遍就可以了,大概不会超过150 篇的文章。

尽管我们说阅读是一个投入和产出不成比例的项目,但是它也有一点好处,

那就是一旦到达了某一水平,即便你很久不背单词,也可以保持在那一个水平。

我个人比较喜欢的训练方式是集中训练,不太喜欢那种一天做两篇的方法。

因为集中在一起训练可以看到比较好的效果,而且对于那些技巧的记忆与运用也

是有好处的。

前期做大概10-20 篇文章了解一下阅读的大致情况,就可以开始

限时训练了,以一个Section 作为一个单元,反复的进行限时训练。

一般来说阅读的题目看了答案之后还是比较容易想通的,实在还是不懂可以

上网来讨论。

对于自己错的比较多的文章最好做一下记号,以便临考前集中复习一下。

另外,课余时间可以推荐看一下杂志。

Science 和Nature 在文字的难度上面不如GRE 阅读那么难,但是就论证的结

构方面还是有很大的相似的。

TIME 的文字的难度是足够了,基本上大于GRE 阅读,比较适合复习单词。

也有推荐在做完GRE 阅读之后去做GMAT 以及LSAT 的阅读,一般来说我们的

时间是不足以支持我们去做完这些全部的阅读的。这两种阅读都有很大的专业背

景在里面,个人并不是很推荐作为GRE 阅读的替代品。

在单词背的很好的基础上面,做一定量的题目,自然而然就可以

达到很好的效果,毕竟就所有的填空题以及所有的阅读题而言,出题

的风格并没有太大的改变,套路还是在那里的。

需要再次提醒注意的是,快速而准确的理解所给材料的意思永远

是解决填空和阅读最最关键的技巧

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

282
发表于 2010-2-27 10:53:59 |只看该作者
本帖最后由 lghscu 于 2010-2-27 10:57 编辑
评分的标准可以参看官方指南上面的评分标
准,一般来说对于Q,错2-3 个不扣分,之后是1 题10 分,对于V,
错2 个左右不扣分,之后是4 题50 分,

10 个是700 分,
20 个是600 分,
30 个是500 分

600 分的Verbal 差不多是每个Section 可以允许错10 个题目。
一般而言,
填空7 道题目有5 道题目是比较容易的,尤其是最近几次的考试。

阅读11 个题目,一般来说错4 个左右是比较正常的。
类反20 个题目就只能够错4 个,大概是类比2 个,反义词2 个。


红宝书42-51 这10 个List 收录了近年来GRE Verbal 部分出现
的新词,考前一定要仔细的记忆,因为这些新词的重现率还是很高的。


关于跨区的问题已经讨论了很久了。我个人是不推荐跨区的,如果一定
要跨的话一般来说是在做Q 的时候跨V,一般是留下反义词来跨区,跨区的最
佳时间通常认为是Q 中间的10 分钟。理论上跨区一次就可以当作弊处理,不过
国内的老师一般来说还是会给一次机会。

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

283
发表于 2010-2-27 18:04:54 |只看该作者
本帖最后由 lghscu 于 2010-2-27 18:10 编辑

在Library借到
“GRE句子填空”,陈圣元
“GRE类比/反义”,宋昊
下载到
“张华常考意群电子版PDF”

预约
“GRE词汇考试频率统计及中文解释”
“GRE/GMAT阅读难句教程”
“GRE数学高分快速突破”
“GRE全真模拟试题集”

没有找到
“GRE阅读必备专业词汇”--明天还找不到就去买了,15*0.85=13RMB

准备去书店蹭看
“GRE句子填空15天速战速决”的前面“讲解部分”
-----------
呵呵

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

284
发表于 2010-2-27 19:29:07 |只看该作者

"GRE General Test Practice Book"
开始看

使用道具 举报

Rank: 7Rank: 7Rank: 7

声望
401
寄托币
5013
注册时间
2008-9-29
精华
3
帖子
298

GRE斩浪之魂

285
发表于 2010-2-27 20:33:59 |只看该作者
GRE阅读提倡“边读边想边记”

“边想”,每个人都想做到,但又应该想什么?
1 Main ideas & Supporting ideas

2 Author's own idea & info presented

3 Ask yourself:
-What is this about?
-What are the key points?
-How does the main idea relate to other ideas in the passage?
-What words define relationships among ideas?

-----------from GRE General Test Practice Book

使用道具 举报

RE: 【1006G】【习惯性GRE】--【备考日记】--方法+经验+毅力 [修改]
您需要登录后才可以回帖 登录 | 立即注册

问答
Offer
投票
面经
最新
精华
转发
转发该帖子
【1006G】【习惯性GRE】--【备考日记】--方法+经验+毅力
https://bbs.gter.net/thread-1022563-1-1.html
复制链接
发送
报offer 祈福 爆照
回顶部