Paper Rewriting

Topics:

• Algorithms and Theory
  • Paper: Stefan Hougardy, The Floyd-Warshall Algorithm on Graphs with Negative Cycles, Information Processing Letters, 110 (2010), 279-281, Elsevier. [pdf]
• Artificial Intelligence (AI)
  • Paper: Daya Bassam and Ismail Anis, A Neural Control System of a Two Joints Robot for Visual Conferencing, Neural Processing Letters (2006) 23:289–303, Springer. [pdf]
• Bioinformtaics
  • Paper: Wen Cheng and Changhui Yan, A Graph Approach to Mining Biological Patterns in the Binding Interfaces, Journal of Computational Biology, Volume 24, Number 1, 2017, Pp. 31–39, Mary Ann Liebert, Inc . [pdf]
• Computer Architecture
  • Paper: Vivek Seshadri, Kevin Hsieh, Amirali Boroumand, Donghyuk Lee, Michael A. Kozuch, Onur Mutlu, Phillip B. Gibbons, and Todd C. Mowry, Fast Bulk Bitwise AND and OR in DRAM, Computer Architecture Letters, 14(2): 127-131 (2015), IEEE. [pdf]
• Computer Based Education
  • Paper: Yao-Ting Sung, Kuo-En Chang, and Tzu-Chien Liu, The effects of integrating mobile devices with teaching and learning on students' learning performance: A meta-analysis and research synthesis, Computers & Education, Volume 94, March 2016, Pages 252-275, Elsevier. [pdf]
• Computer Graphics
  • Paper: Juraj Vanek, Jorge A. Garcia Galicia, Bedrich Benes, Radomír Mech, Nathan A. Carr, Ondrej Stava, and Gavin S. P. Miller, PackMerger: A 3D Print Volume Optimizer, Computer Graphics Forum, 33(6): 322-332 (2014), Wiley. [pdf]
• Computer Security
  • Paper: Maryam Mehrnezhad, Abbas Ghaemi Bafghi, Ahad Harati, and Ehsan Toreini, PiSHi: click the images and I tell if you are a human, Int. J. Inf. Secur. (2017) 16:133–149, Springer. [pdf]
• Databases
  • Paper: Olaf Hartig and M. Tamer Özsu, Reachable subwebs for traversal-based query execution, In Proceedings of 23rd International World Wide Web Conference, WWW '14, Seoul, Republic of Korea, April 7-11, 2014, Companion Volume, ACM 2014, pp. 541-546. [pdf]
• Human Computer Interaction (HCI)
  • Paper: D. Rocchesso, S. Delle Monache, and S. Papetti, Multisensory texture exploration at the tip of the pen, Int. J. Human-Computer Studies, 85 (2016), 47-51, Elsevier. [pdf]
• Networks
  • Paper: Ashikur Rahman and Pawel Gburzynski, Hidden Problems with the Hidden Node Problem, In Proceedings of 23rd Biennial Symposium on Communications, 2006, pp. 270-273, Kingston, Ontario, IEEE. [pdf]
• Software Engineering
  • Paper: Oleksii Kononenko, Cheng Zhang, Michael W. Godfrey, Compiling Clones: What Happens? In Proceedings 30th IEEE International Conference on Software Maintenance and Evolution, 2014: 481-485, Victoria, Canada, IEEE. [pdf]

General guideline:

• Try to understand the paper 100%. It may require you to read the paper many times (may be at least 10 times!) again and again. A complete understanding of this paper will give you a clear and complete idea about how a research paper should be written. This will help you when you shall write your own research paper.
• Write your report in your own language. You are free to copy some figures or tables from the paper if necessary. Because, drawing all their figures anew or generating all their tables and data anew by yourself is not possible.
• Try to find positive sides of the paper. For example, the idea of the paper may be very interesting, may be novel, may have been used by many papers later, results might have solved a long standing open problem, writing style is very good and clear, results are deep, etc. Mention them in your report.
• Similarly, try to find its shortcomings. For example, poor writing quality, vague idea, unclear methods, dull theories used, results not deep, survey data not sufficient, many things not clear and could be improved, idea not novel and almost same as previous papers, error in results, confusing, etc. Mention them in your report.
• Make your report easier to understand than the paper, so that a reader can understand the content of the paper by reading only your report and without looking into the paper.
• Add additional examples, figures, data, tables and explanation as necessary to make the report easy to understand. If necessary, if possible, and if applicable, then you may write some simple code or do some little experiment or survey to verify/see yourself the results of this paper.
• If necessary, look into the references in this paper to understand the material of the paper.
• If necessary, look into the papers that have used this paper as a reference. You can use the site "Google Scholar" and "Microsoft Academic" (they will come in Lecture 4) to find the list of papers that have published after this paper and have used this paper as a reference.
• You may need to look into some books or materials to understand the topics and content of the paper. For example, if your paper is on database, then you may need to look into the undergraduate database book for the terms, definitions, theories, and other materials that have been used in the paper.
• Format of the report: Report must be written in LaTeX. Use font size 10~11, full page style, and single column. Make your report about 10 pages. You can use a predefined and freely available LaTeX style file such as llncs from Springer, elsarticle from Elsevier, etc.
• Your report may contain the following sections: abstract, introduction, main results of the paper, method/techniques used in the paper, positive sides of the paper and significance of the results, shortcomings and missing things in the paper, conclusion, references. You may add additional sections if you want.
• While you are looking into the paper and the related references and while you are writing your report, you may think yourself what has been done in other papers that are related to the results of this paper or that have used the results of this paper. Also you can think what can be done in future. But do not include them in your report. You will include them in your upcoming project in this course. In other way to say, this paper will give you a lead for your project. However, in your upcoming project you may deviate (change) from the exact topic of this paper and will get more freedom to formulate your own project and investigate new problems. While you rewrite this paper, think about those things so that during your project you may get benefit from them.

Writing examples: [pdf]