This graduate independent study examines recent research results in verified systems, with specific focus on verified operating and distributed systems software (e.g., CertiKOS, seL4, Verdi, etc.). The independent study is structured as a graduate seminar: weekly readings together with paper reviews and periodic assignments in which students build and extend existing verified systems. As a final project, students will either implement their own verified system (of moderate complexity) or extend an existing verified system in a nontrivial way.
| Component | Percentage |
|---|---|
| Weekly readings + paper reviews | 30% |
| Assignments | 30% |
| Final Project | 40% |
In addition to scheduled assignments, students are required to post reviews of each week's assigned reading.
Post reviews to the Piazza page using the appropriate tag (e.g., w2 for week 2's review).
Reviews should include at least the following sections:
- Summary: What's the paper about?
- Contributions: What's the value of this paper to the research community?
- Pros: What's good about this paper wrt. content, stylistically, or otherwise?
- Cons: What's bad?
Students are required to complete a significant final project (40%) that either extends an existing verified system in an interesting way or implements a verified system from scratch (target and scope to be agreed upon in consulation with the instructor). Students will document their final projects in short technical reports (Week 13). Students will present their final projects in the final two weeks of the semester.
| Instructor/GA | Noninstructor (e.g., Another Student) | |
|---|---|---|
| You | All collaboration allowed | High-level discussion (of the problems, not your code!) allowed but only after you've started the assignment; must be documented in README as described below |
Unless otherwise noted, homeworks are due Tuesdays by 11:59 p.m. Late homework assignments will be penalized according to the following formula:
- Up to 24 hours late: no deduction, for a max 2 late homeworks per student across the entire semester
- Homeworks later than 24 hours, or from students who have already turned in 2 late homeworks, will receive 0 points.
You may discuss the homework with other students in the class, but only after you've attempted the problems on your own first. If you do discuss the homework problems with others, write the names of the students you spoke with, along with a brief summary of what you discussed, in a README comment at the top of each submission. Example:
(* README Gordon Stewart, Assn #1
I worked with X and Y. We swapped tips on how to resolve dependencies when building seL4. *)
However, under no circumstances are you permitted to share or directly copy code or other written homework material, except with course instructors. The code and proofs you turn in must be your own. Remember: homework is there to give you practice in the new ideas and techniques covered by the course; it does you no good if you don't engage!
That said, if we find that you have cheated on an assignment in this course, you will immediately:
- Be referred to the Office of Community Standards (which may take disciplinary action against you, possibly expulsion); and
- Flunk the course (receive a final grade of F).
Students in EECS courses such as this one must adhere to the Russ College of Engineering and Technology Honor Code, and to the OU Student Code of Conduct. If you haven't read these policies, do so now.
If you suspect you may need an accommodation based on the impact of a disability, please contact me privately to discuss your specific needs. If you're not yet registered as a student with a disability, contact the Office of Student Accessibility Services first.