Term Project

Term project
Groups must be formed by: Friday, October 23, 2020
Proposals due: 11:59 PM, Wednesday, October 28, 2020
Progress reports due: 11:59 PM, Wednesday, November 11, 2020
Complete paper drafts due: 11:59 PM, Monday, November 16, 2020
Presentations: 4:00-6:00 PM, Saturday, November 21, 2020
Final submission: 4:00 PM, Saturday, November 21, 2020

As you know, this course requires you to complete a final project that will determine 15% of your grade. You may choose your own topic related to operating systems to study in more detail than we have as a class. Most projects will involve programming, but the amount and difficulty may vary from topic to topic. You will report on your project through a paper and brief (approximately 20 minute) presentation at a minisymposium to be held at the end of the semester.

You are expected to work in groups of size two or three. Individual projects may be approved on a case-by-case basis, as would groups of size four. Groups must be formed and all repositories created (regardless of group size) by Friday, October 23, 2020.

Through Wednesday, October 21, 2020, we will work toward matching group interests to make sure we end up with a nice variety of projects by contributing to a shared document. Please start thinking about project ideas right away and put those ideas in the document. This document can also help those looking to form groups to find others with similar interests.

These are just ideas, and you should not restrict yourself to this list. I hope everyone can find an appropriate topic that they find interesting. You might also find it useful to browse recent journals and conferences proceedings to get a feel for some current research projects in operating systems.

Rather than creating repositories through the GitHub Classroom mechanism we usually use, each group will create a repository for their project. It should be housed in one group member's GitHub account. Other group members should be granted write access and your instructor should be granted read access (if the repository is private). Send the repository's URL to your instructor as soon as it's ready to go, no later than Friday, October 23, 2020.

By 11:59 PM, Wednesday, October 28, 2020, submit a proposal (by committing and pushing a file proposal.pdf in your repository), at most one page in length, that briefly describes the project you plan to complete and how you plan to go about it. Describe the major milestones for your project, a rough schedule for achieving these milestones, and which milestones you believe are most important for your project to be considered a success. If you will need access to any special hardware or software, include that in your proposal. Your proposal should make it clear that you have an interesting, worthwhile, and relevant topic and that it is feasible in the time available.

By 11:59 PM, Wednesday, November 11, 2020, submit a progress report (committed and pushed as progress.pdf in your repository). This should consist of a detailed outline (or better yet, an early draft) of your paper including sources, and a description of the design and current implementation status of your software, as well as a more specific timetable for completion of the project. You must also submit an annotated bibliography with your progress report, detailing the sources you have considered (likely including some you intend to use and some you do not intend to use).

This is to be a formal research paper, and should be organized as such. You should begin with a title, author list, and abstract. The main body of the paper should be organized into sections including (i) an introduction in which you describe the general topic and the particular aspects you will be examining, (ii) one or more sections comprising your main text, where you describe what you have done, how you have done it, and what you have learned, (iii) a conclusion, which should include ideas for future investigation into your topic which were beyond the scope of your paper, and (iv) a complete list of citations. Citations of web pages are acceptable in some circumstances, but books, articles in conference proceedings or journals, or technical reports are preferred.

Proper English and a good technical writing style are important. Writing well is very difficult - it is an iterative process and cannot be done all at once. Be precise and be concise. Check your spelling and grammar carefully. Most papers will be around 15 single-sided pages, using 1.5 spacing, one inch margins, and a 12-point Times Roman font (or as close as you can come). Please do not adjust margins and font sizes to force a certain length. You are encouraged but not required to use LaTeX to typeset your paper. My LaTeX example in a GitHub repository is already set up with an appropriate format. Length is not important - content and quality are. Papers shorter than 10 pages or longer than 20 pages are acceptable, if the length is appropriate for the content.

Submit a draft, as complete as possible, by committing and pushing a PDF file draft.pdf by 11:59 PM, Monday, November 16, 2020. The more complete this draft, the better feedback you will receive to be able to improve it and the more you can focus on programming over the last week or two. You may also submit additional drafts for feedback, but keep in mind that it may take a day or two to get to them. Submit your final version by pushing and committing a PDF file paper.pdf by 4:00 PM, Saturday, November 21, 2020.

You should submit your source code and instructions on how to build and run it. The software should be described in the paper, and must be well-documented in a form appropriate for the programming language used. Please make arrangements to demonstrate your program(s). Source code should be committed and pushed to your repository and demonstrations completed by 4:00 PM, Saturday, November 21, 2020.

Each group will present a summary of their work to the class. Include background information on your project, the motivation for your project, a description of what you did, and a summary of what you learned. Software demonstrations may also be appropriate. Prepare slides or web pages. Rehearse your presentation, paying special attention to timing. Presentations of 15-20 minutes each will take place during a class minisymposium to be held 4:00-6:00 PM, Saturday, November 21, 2020. All group members must participate in the presentation. Attendance is required for the entirety of all presentation sessions, not just when your group is speaking. Please also submit your presentation materials through a directory in your repository.

This final project accounts for 15% of the course grade. The grade will be based on all aspects of the project, including the proposal (5%), the progress report (5%) and annotated bibliography (5%), the design, documentation, style, and correctness of the software developed (10-30%), the content and writing style of the complete draft (10%) and final version (30-50%) of the paper, and quality of the presentation (15%). The breakdown between software development and the final paper will depend on the amount of programming required for each project. No credit is given for attendance at the minisymposium, but penalties will be applied for missing all or part of it.

Collaboration within a group is unrestricted. Since each group is working on a different project, you are free to discuss your projects with each other. If you wish to use or refer to any software libraries or outside source code beyond the standard language (C, C++, Java) libraries, check with me first. All sources must be cited properly. If in doubt about anything related to Academic Honesty, ask now and avoid problems later!

You have several weeks, so the expectation is for several weeks of work. You will not be able to do a good job if you put it off. I don't expect a Ph.D. thesis, but I do expect much more than your average lab assignment.