CSE 225 Topical and Course Project Report


Paper Reading and Participation in Discussions

 

Students are expected to read all of the papers in the syllabus and participate actively in discussion in class.  Classes will be organized to direct questions at individual students (come prepared!), and to have a lively discussion of the issues.  

 

Topical Reports (Sign-up List)

 

For each major section of the course, a two teams of three students each will be identified to write a summary of the area.  Each student in the class will participate in one of these teams.  This summary should include the following elements:

  • Concise definition of the important problems in the area
  • Survey of the major approaches to the problem
  • Assessment of the state of the art in the area
  • Identification of at least four major research problems or challenges to be explored

 

These reports will be approximately 20 pages in length and will cover material for one of the first four course sections (Vision, Dynamic Applications, Resource Sharing, and Configurable Networks).  They are intended to not only reiterate the material in the papers (i.e. a book report), but to cover additional technical papers as needed.  Significant analysis and understanding which is translated into clear exposition is expected.

 

Topical reports are due one week after coverage of the topic has been completed in the course lecture.

 

Project Reports

 

Each student in the class will participate in a course project involving 2-4 students.  This, combined with the topical report, represent the major part of the course work.    In the process of doing a course project, each team will be evaluated on two documents and a presentation.  These are:

  • Project Proposal (due end of 3rd week of class)
    • clear objectives - questions to be answered, research apparatus to be built, code to be understood)
    • the team (who’s on it and contact information – email, phones, etc.)
    • clear responsibilities (who’s going to take lead for what); which will evolve over time
    • Technical Definition of the project
      • Project focus: What are the questions?
      • Infrastructure and Strategy: How are the questions going to be addressed? (i.e. the software, systems, resources and  experiments)
      • Expected Outcomes: What will we know that is new at the end of the project?
    • Related Work Section (summarize background material)
    • Detailed Project Plan
      • Obtaining access to the needed computing resources
      • Obtaining the relevant software
      • What will be built/configured (and software design)
      •  The implementation and testing plan for that design What experiments will be done
      • What are the fallbacks if something doesn’t work out
      • Specific milestones that are clearly defined and provide reasonable time for unexpected problems
  • Project Presentation (last week of class)
    • A 15-minute, Succinct Presentation of the Material in Project Final Report
  • Project Final Report (due at end of classes)
    • Elements from the Project Proposal
    • Description of What was Accomplished
    • Experimental Results
    • Analysis and Summary of Results