CSC 3990 -- Feedback on Paper Summaries


1.       In a summary report, do not say "we", "I" or "you". Here are some examples of what not to do:


 I liked how the research focused on […]” à

“One positive aspect of this research is the focus on […]”


I have questions about

            “It is unclear whether […]”

            “The paper does not address the problem of […]”


I feel that, with some further research […]” à

“It may be possible that further research […]”


Personally, I found the proposed solutions to be […] à

            “The proposed solutions are […]


2.       Avoid uncertainty. Present the results in a clear and unambiguous way. Here are some examples (drawn from your summaries) of what not to do:


“The authors try to show […]”à

“The authors show”


The authors claim that […]”à

“The authors show that […]” 

  (No claim ever goes in print without supporting evidence)


“The paper attempts to solve the problem of wireless mobile localization […]”à

“The paper addresses the problem of wireless localization”

  (The localization problem is huge; this paper focuses on a small sub-problem)


3.       Eliminate comments on the clarity and quality of presentation, or other comments that would fit under reviewer’s tasks. Examples:


This paper was well written

The work is original, and significant.

The paper is well organized


4.       Avoid acronyms! You should always first spell out an acronym, and use it only when you find yourself repeating the same thing over and over again. Examples:


“The authors describe the design and implementation of VUST

à What does VUST stand for?

à Expand to “Villanova University Speech Transcription” on first use.

    Then it is OK to use the VUST acronym throughout the rest of paper.


5.       Do not summarize each section in the paper individually. We are interested in the content and contribution of the paper, not its physical form. Examples of what not to do:


“The paper started with […]”

“The paper ended with a test in a live class lecture […]”

6.       Do not use contractions (such as "don't").

7.      The problem statement should be as clear and accurate as possible. Someone reading your problem statement should be able to start working on the problem right away. Here is an example of an appropriate statement:


Assistive speech recognition tools can be a valuable asset in the classroom for students with hearing disabilities. Developing a low-cost, accurate speech translation system poses a number of challenges, such as filtering background noise, separating multiple voices and sensing variations in speakers’ pace and accent.  This paper analyzes various assistive speech recognition platforms, seeking to design one with minimum cost and maximum accuracy.


8.       Once the problem has been defined, your summary should state the main result up front:


The authors describe the design and implementation of a low-cost assistive speech recognition system, called Villanova University Speech Transcription (VUST). Experimental results show that, with a reasonable amount of training, the VUST system could achieve over 90% accuracy, which is within the acceptable accuracy range for practical systems.


9.       Proposed solutions should briefly describe the methods used to solve the problem. A few students have been unable to distinguish the results from the proposed solutions.


10.   In a future work section, identify results that could be pursued further.