===== Some Elements for the Methodology and Best Practices ... ===== ==== Few advices to write an interesting paper ==== == Questions that must be answered before all == * What is the added value of the paper ? * What is the gain for the reader ? * What is the purpose of the paper ? * What is the purpose of the reader when he's reading the paper ? * If the reader has to decide something technical thanks to the paper, how the paper can help him ? * Why the reader pay for this paper ? ** One of the relevant measure is how many saved time to apprehend a topic thansk to the paper ** * Example 1 : Introduction to Cloud Computing (one hour of reading for one hour on the web !) : **no gain !** * Example 2 : Comparison between technologies for Tagged Objects and the existing solution on the market (one hour of reading for ten hours on the web !): **90 % of saved time!** == Short is better == * Do you prefer to read a short or a long paper that give you answers ? * If the paper is long, you must know why you need to explain more interesting things to the reader ! ** The student paper will be 3 or 4 pages long ** ==== Some advices about References ==== * References must be used to shortly introduce interesting ideas, studies and analysis that were explained in the referenced paper * Bibliography is better than Webography because published paper are always available. The content of a web site can changed and past release lost. * Don't forget any informations in a reference : title, authors, date, editor, pages, location, url, ISBN, DOI etc. * In case of duplication of figures, the references are not enough. References don't allow to copy something, only to suggest other readings about a topic (Ref :[[https://bucks.blogs.nytimes.com/2010/09/21/when-its-illegal-to-photograph-artwork/| "When It’s Illegal to Photograph Artwork", Jennifer Saranow Schultz, The New York Times, September 21, 2010 (available 022018)]]. * Quality of references must be guarantee, thanks to : * Selection process with reviewer, like for research papers (conferences proceedings and journals) from well-known scientific publishers : IEEE, ACM, Springer Verlag, Elsevier .. * Consortiums bringing together major actors of a technical domain like Standards Organization(ETSI, IEEE standards, IETF, W3C, OASIS, UPnP ...) * Sometimes (but be careful) some white papers comming from well-known research and advisory firms, famous companies with an internal Research Department : (Gartner, Inc., Oracle, IBM, etc.) ==== Main search engines and best practice ==== [[http://ieeexplore.ieee.org/Xplore/home.jsp|IEEE Xplore Digital Library (paid access)]] [[https://dl.acm.org/|ACM Digital Library (paid access)]] [[https://www.elsevier.com/about/open-science|Elsevier Digital Library] [[http://www.springer.com/fr/|Springer Digital Library]] [[http://citeseerx.ist.psu.edu/index|citeseerx (free access)]] [[https://scholar.google.fr/|Google Scholar]] [[https://www.researchgate.net/|Researchgate]] == reference == [[https://community.dur.ac.uk/ebse/resources/notes/tools/SearchEngineIndex_v5.pdf|Digital Libraries and Search Engines for Software Engineering Research: An Overview Mark Turner, Technical report of Keele University, Version 5 – January 2010 ]] ==== Example of Paper Template ==== * **Research Paper (for a comparison between research works) ** * Abstract section must explain at least what is the topic and the purpose of the paper * Introduction section must explain * why this paper and the context of the topic * what is the plan of the paper * "Related works" section must give a list of the research that are significant in the topic adressed by the paper * "Discussion" section must clearly define all the characteristics and the used criteria for comparison. * "Discussion" section must produce a synthesis array with all the compared solutions in columns and all the characteristics in lines, checked or not. * "Conclusion and Perspective" section conclude the discussion with the main ideas of the discussion and what are the hot topics to go ahead. * **Technical Paper ** (for a comparison between technological solutions) * Abstract section must explain at least what is the topic and the purpose of the paper * Introduction section must explain * why this paper and the context of the topic * what is the plan of the paper * "Main Characteritics" section must clearly define all the characteristics of a common description of the solutions. * "Main Characteritics" section must give a list of the technological operationnal solutions, even of the market. * "Discussion" section must produce a synthesis array with all the compared solutions in columns and all the characteristics in lines, checked or not. * "Discussion" section may provide some advices on the bast solutions in various use cases and illustrations * "Conclusion and Perspective" section conclude the discussion with the main ideas of the discussion and what are the hot topics to go ahead. ==== Paper Format ==== ||| [[http://www.acm.org/sigs/publications/pubform.doc | ACM Doc template]] [[http://www.ieee.org/documents/Transmag.doc | IEEE Doc template]] [[https://www.elsevier.com/__data/promis_misc/FINE_FinalTemplate.doc| Elsevier doc template]] {{:cours:acmformat.doc|ACM}} is the chosen format. ** Be careful about the format of the bibliography in each of these templates** ===== Choose your own methodology but ... ===== * Be careful of the quality of the paper you read and you cite * Be careful to give complete references * Be careful to add value in your paper and a personal contribution in the analysis (Don't describe simply a standard technology or a research result without analysis for comparing and criticing them. Papers must introduce original idea in the analysis. ===== Agenda for Deliverables ===== == Before 12/22/18 == Send an email to tigli@unice.fr with a subject like [PAPER MIT 2018][] [Name2>][][] Don't forget to replace <...> by the corresponding string. Ex : <Name1> may give <Tigli> (*) Choose Between RES or ENG betweem brackets according of the topic of your paper : a research Paper (RES) or a technoligical Paper (ENG) == During intermediary Courses with JY Tigli (one hour only) and all the Last one == You'll be able to discuss with the lecturer about your work in progress. == One week after the Last course (exam period) == You must send the paper in a email with the subject : [FINAL PAPER MIT 2018][<Name1>] [Name2>][<RES or ENG *>][<Title of your paper>] with a attached zip file that contains : * your paper in a ACM doc format. The name of the doc file will be <Name1>_<Name2>_Paper.doc * all the other paper your cite in yours ==== Example of topics for papers ==== - Comparison of at least two [[cours:mit_2017_2018:IoT_plateforms|IoT plateforms ]] == References == [[http://www.cs.ucf.edu/~lboloni/Teaching/EEL6788_2008/slides/SurveyTutorial.pdf|Some thoughts about writing a survey paper, Lotzi Bölöni, Feb 2008, Dept of Computer Science of University of Central Florida ]] [[https://www.elsevier.com/__data/promis_misc/525444systematicreviewsguide.pdf|Guidelines for performing Systematic Literature Reviews in Software Engineering. Barbara Kitchenham, und Stuart Charters. EBSE 2007-001. Keele University and Durham University Joint Report, (2007)]] [[https://ac.els-cdn.com/S016412120600197X/1-s2.0-S016412120600197X-main.pdf?_tid=9e578f92-e4dd-11e7-94e6-00000aab0f27&acdnat=1513702795_2ac6724c6091e0496ed91ca516adea38|Pearl Brereton, Barbara A. Kitchenham, David Budgen, Mark Turner, Mohamed Khalil, Lessons from applying the systematic literature review process within the software engineering domain, In Journal of Systems and Software, Volume 80, Issue 4, 2007, Pages 571-583, ISSN 0164-1212, https://doi.org/10.1016/j.jss.2006.07.009.]] === Tools for SLR === [[https://works.bepress.com/aleebrahim/122/download/ | Research Tools: Scientifc Writing Tools for Writing Literature Review and a Paper, Nader Ale Ebrahim, University of Malaya, From the Selected Works of Nader Ale Ebrahim, February 12, 2016]]