CS 615 - Homework

Homework Assignments

All homework must be completed individually. You may discuss the problems with others but you must turn in your own work. You may either (1) email me your PDF or PS homework file, (2) give me your homework in class, (3) give me your homework during my office hours, or (4) slip your homework under my office door. If the homework assignment includes a programming component, you must email me your code.

Do not make use of any other delivery method for your homework (e.g., carrier pigeons, my faculty mailbox).


  1. Homework 1 Written (last update -- Thu Aug 24 11:07:12 EDT 2006 ).
    Homework 1 Code.
  2. Homework 2 Written (last update -- Thu Sep 7 09:49:48 EST 2006 -- now due Friday ).
    Homework 2 Code.
  3. Homework 3 Written (last update -- Thu Sep 7 10:49:35 EST 2006 ).
    Homework 3 Code.
  4. Homework 4 Written (last update -- Wed Sep 13 14:08:10 EDT 2006 ).
  5. Homework 5.
    1. Homework 5 Written (last update -- Wed Sep 20 13:11:50 EDT 2006 ).
    2. Homework 5 Code.
    3. Download one of the versions of Simplify below and rename it to $TOP/Simplify (i.e., put it in the same directory as nf.ml).
    4. Necula et al.'s CIL: Intermediate Language and Tools for Analysis and Transformation of C Programs (optional)
    5. Detlefs, Nelson and Saxe's Simplify: A Theorem Prover For Program Checking (optional, huge PDF)
    6. Manuvir Das' Unification-based pointer analysis with directional assignments (optional, the GOLF paper)
    7. Bush, Pincus and Seilaff's A Static Analyzer For finding Dynamic Programming Errors (optional, the PREfix paper)
    8. The CIL Manual. In particular, check out the CIL API Documentation (or read cil/src/cil.mli). (optional)
    9. O'Reilly's Developing Applications With Objective Caml (really optional, but if you feel you need extra help with OCaml, this book probably has the answers -- you can also talk to me)
    10. Precompiled x86 CYGWIN version of the Homework 5 code. Use this if you can't get CIL to build yourself; typically that's indicative of other problems, however.

Calls For Papers, Fun Venues, Internships, Summer Activities

Random Somewhat-Related Humor

  1. Research Glossary (note "interesting to me")
  2. The Guru of Chelm (evaluating systems)
  3. How To Prove It (alternative techniques to structural induction)
  4. K-Coward (taking math too seriously)
  5. Hamlet PowerPoint (problems with all-PowerPoint presentations)
  6. Universal Poker (proof theory: why is Truth's opposite "Void"?)
  7. Chess Books (useful background reading)
  8. Polynomial Hierarchy Collapses: Thousands Feared Tractable
  9. Microsoft Patches (exceptional situations and error handling)
  10. C Problem (essential debugging)
  11. USENET Homework (asking for help)
  12. Linux Development Order (requirements engineering)
  13. GCC International (promoting international understanding)
  14. Microsoft Buys TeX (note "What were we thinking?" and "third-party display driver")
  15. Feel-Good Abstraction (at what level should we analyze and design?)
  16. Parametric Worm (Microsoft security explained)
  17. 1776 Computers (historical perspectives)
  18. Security Important (system and user security)
  19. Secure README (security through obscurity)
  20. Tarzan Learns Email (explaining CS to the laity)
  21. Jobs Translated (meanings of terse utterances)
  22. How I Met My Wife (is Wes speaking English?)

Other Similar Courses

Here are some example homeworks from similar courses at other universities (these should actually work as of 5pm Jan 17, but are probably a bit more "implementation-heavy" than what you'll see in this course):