E.g.: "We are currently extending the algorithm to...
blah blah, and preliminary results are encouraging." This statement serves to mark your territory.
Guideline #1: A clear new important technical contribution should have been articulated by the time the reader finishes page 3 (i.e., a quarter of the way through the paper).
Guideline #2: Every section of the paper should tell a story.
Unless there's a good argument against it, the Introduction should consist of five paragraphs answering the following five questions: (Exercise: Answer these questions for the multiway sort example.) Then have a final paragraph or subsection: "Summary of Contributions".
It should list the major contributions in bullet form, mentioning in which sections they can be found.By the time a referee has finished the Introduction, they've probably made an initial decision about whether to accept or reject the paper -- they'll read the rest of the paper looking for evidence to support their decision.A casual reader will continue on if the Introduction captivated them, and will set the paper aside otherwise. Here is the Stanford Info Lab's patented five-point structure for Introductions.Thus, the notes include several exercises for the reader. The material in the abstract should not be repeated later word for word in the paper.Titles can be long and descriptive: State the problem, your approach and solution, and the main contributions of the paper. (Exercise: Write an abstract for the multiway sort example.) The Introduction is crucially important.Whenever possible use a "top-down" description: readers should be able to see where the material is going, and they should be able to skip ahead and still get the idea.In general a short summarizing paragraph will do, and under no circumstances should the paragraph simply repeat material from the Abstract or Introduction.End, if it can be summarized quickly early on (in the Introduction or Preliminaries), or if sufficient comparisons require the technical content of the paper.In this case Related Work should appear just before the Conclusions, possibly in a more general section "Discussion and Related Work".Preliminaries: This section, which follows the Introduction and possibly Related Work and/or Running Example, sets up notation and terminology that is not part of the technical contribution.One important function of this section is to delineate material that's not original but is needed for the paper. Content: The meat of the paper includes algorithms, system descriptions, new language constructs, analyses, etc.