DOC PREVIEW
WUSTL CSE 571S - CSE571 Project Guidelines

This preview shows page 1-2-15-16-31-32 out of 32 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 32 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

2P-1©2009 Raj JainCSE571SWashington University in St. LouisCSE571CSE571Project GuidelinesProject GuidelinesRaj Jain Washington University in Saint LouisSaint Louis, MO [email protected] slides are available on-line at:http://www.cse.wustl.edu/~jain/cse571-09/2P-2©2009 Raj JainCSE571SWashington University in St. LouisOverviewOverview Project Requirements, End-Goal Writing Style Organization List of Acronyms References HTML Style Guidelines Submission2P-3©2009 Raj JainCSE571SWashington University in St. LouisProjectsProjects If you are doing a survey, make sure your report produces a good summary of key current issues and recent developments.  Topics that are 5+ years old should be mentioned only briefly with references to books for further information. Hands-on projects should talk about the concepts/theory used in the project and include the details of the design and use of the software. The software should be well documented in the report and code so that others can use it or improve upon it.2P-4©2009 Raj JainCSE571SWashington University in St. LouisProject RequirementsProject Requirements Comprehensive Survey or hands-on projects Technical Papers, Industry Standards, Products Will be published on my website, Better ones may be submitted to magazines or journals No copyright violations: ⇒ You need to re-draw all figures⇒ You need to summarize all ideas in your *own* words ⇒ Cannot copy any part of text or figure unmodified⇒ Short quotes ok⇒ Any unmodified figures need permissionsAny infringement will result in forfeiture of grades even aftergraduation. See papers in previous courses, e.g., http://www.cse.wustl.edu/~jain/cse574-06/index.htmlhttp://www.cse.wustl.edu/~jain/cse567-06/index.html2P-5©2009 Raj JainCSE571SWashington University in St. LouisEndEnd--GoalGoal Paper that can be published as a survey paper in any magazine, journal, conference2P-6©2009 Raj JainCSE571SWashington University in St. LouisLiterature SearchLiterature Search Finding references: Use Google advanced search options¾ Location 802.11 +filetype:pdf +site:.com Conduct searches in two phases. In the first phase, use the title words of your project. After reading these, conduct another more comprehensive search.  Remove articles that are not useful No limit to the number of references Follow the references in references2P-7©2009 Raj JainCSE571SWashington University in St. LouisWriting StyleWriting Style Readers want to get to the information fast. Keep the nonessential stuff at the end. Check thoroughly for grammar and spelling. Avoid excessive use of abbreviations. Be consistent in case and usage: MOBILE, Mobile, mobile2P-8©2009 Raj JainCSE571SWashington University in St. LouisDiamond Writing StyleDiamond Writing Style Each paper should start with an introduction and end with a summary. Each section should start with a short introduction and end with a summary with a lead in to the next section. The same applies to subsections. All subsections should be of comparable length. Add an appendix with all abbreviations Add a list or discussion of related products2P-9©2009 Raj JainCSE571SWashington University in St. LouisOrganizationOrganization Every paper should have an introduction and a summary. Divide paper in to sections. Every section should have a lead-in paragraph. Header level should correspond to the level in table of contents. Keep all internal references relative. Absolute: http://www.cse.wustl.edu/~jain/papers/x.psRelative: papers/x.ps Try to keep the whole paper in one file “index.html” with figures in fign.gif in the same directory. No Subdirectories. All files names should have eight characters or less for name and 3 characters or less for extension (MS/DOS compatible). The only exception is index.html2P-10©2009 Raj JainCSE571SWashington University in St. LouisOrganization (Cont)Organization (Cont) Title Author Abstract Keywords Table of Contents Introduction Other Sections Summary References List of Acronyms Date Last Modified: Note: This paper is available on-line at http://www.cse.wustl.edu/~jain/cse571-07/ftp/%directory%/index.html2P-11©2009 Raj JainCSE571SWashington University in St. LouisOrganization (Cont)Organization (Cont) File name: Index.html, fig1.gif, fig2.gif, ..., fig.ppt Keep PowerPoint figure source files in the same directory although these may not be referenced in the paper Table of Contents¾ Sections and subsections¾ Numbering n.n¾ 3-7 subsections per section¾ 3-7 sections per paper¾ No page numbers All local links should be lower case. All filenames in lower case.2P-12©2009 Raj JainCSE571SWashington University in St. LouisTitle/Keywords/AbstractTitle/Keywords/Abstract Title¾ Based on Table of contents¾ Searchable Key Search words¾ Based on Table of contents¾ Acronyms and full names Abstract¾ Based on Table of Contents¾ 3-7 sentences Description:¾ One line based on ToC and Abstract2P-13©2009 Raj JainCSE571SWashington University in St. LouisOrganization (Cont)Organization (Cont) See Also:¾ Search our web site for the topic.¾ Look at other current reports on related topics Introduction¾ Explain what the topic is about.2P-14©2009 Raj JainCSE571SWashington University in St. LouisOther SectionsOther Sections Each section less than 3 pages. Each section needs at least one introductory paragraph. Do not start with a subsection. Each subsection at least 1 paragraph. Back to Table of Contents at the end of each section. All sections/subsections should be numbered n. n.n If you borrowed several sentences from some source, italicize the text and indicate the source.2P-15©2009 Raj JainCSE571SWashington University in St. LouisSummarySummary One or more sentences about each issue. Based on Table of Contents Key lessons2P-16©2009 Raj JainCSE571SWashington University in St. LouisReferencesReferences Style of References¾ Author(s), “Title,” Source, date, pages, url¾ The URL should show up as well as have a link.¾ All references should be annotated and have links. Order in the most important first and indicate so In the text point to the end In the end point to actual URL. Provide URL. Find URL for published papers Remove references that are useless. [Authoryy] notation. Exception: Standards, company


View Full Document

WUSTL CSE 571S - CSE571 Project Guidelines

Documents in this Course
IP sec

IP sec

28 pages

Load more
Download CSE571 Project Guidelines
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view CSE571 Project Guidelines and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view CSE571 Project Guidelines 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?