595/700 Guidelines

  1. You must take CSS 509/510. Rare exceptions may be made, but you will have to prove to me that your technical writing skills are superb.
  2. Your proposal should be thorough enough that I understand the background of what you are going to do, why you are going to do it, what you are going to do and how you will evaluate if you have completed your project sufficiently. I want to see that you have thought this through and have a plan. Make sure that your proposal looks professional. I do not want to see a poorly organized document. Make sure your schedule is in the form of a table and is easy to read.
  3. Make sure you include a schedule of what you plan to do on a week-by-week basis
  4. Estimate the time you expect to spend on each task at a # of hours granularity. The capstone or thesis should be 400 hours total
  5. Make sure to include the defense date in your schedule
  6. Make sure to include a final report in your schedule
  7. You must meet with me to give me a mock presentation. Include this in your schedule.
For Thesis
  1. I am only chairing theses for students that have regularly attended my research meetings (contact me if you would like to begin attending them) or worked with me on a 600 project. There may be exceptions on a case-by-case basis, but these are rare.
  2. You must use LaTeX.
  3. You must store your thesis and any code you write in a private VCS that you share with me.
  4. The thesis must be spread over at least two quarters.
For Project
  1. You'll need to convince me that the project is worth doing. You must present and defend your motivation, design, and project plan to me.
  2. This option must be spread over two quarters. Exceptions may be made if you've already worked on this in a class with me or in 600 with me.