CSE-433 Logic in Computer Science - Assignments

Be sure to read the document on the disciplinary policy for this course. [PDF]
Even when you are allowed to discuss assignments with other students, what you hand in must be entirely your own work. This means that when it comes to writing your code or written solution, it must be entirely your own work. That is, you have to write code and written solution all on your own. Hence you should never look at your classmates' code or written solution, not to mention showing yours to them, even if you have discussed assignments with them.
If you use outside material, you must provide all proper citations:
- "I used the following outside material to complete this assignment: (sources of outside material)."
If we judge that you have copied any part of other students' code or written solution, you will be punished for cheating.
Cheating also includes plagiarism in the sense of stealing someone else's idea.
You should never post code relevant to assignments to the discussion board.

	Out			Points	Assignment

W1	Thu	Sep	2	0	Inductive proofs [PDF]	By class, Sep 9
W2	Thu	Sep	9	0	Type safety [PDF]	By class, Sep 30
P1	Tue	Sep	16	100	Propositional logic [coq1.v]	By class, Sep 30
P2	Thu	Sep	30	100	Inductive set [coq2.v] [coq2.pdf]	By class, Oct 7
P3	Thr	Oct	7	100	Proof terms and first order logic [coq3.v] [coq3.pdf]	By class, Oct 14
P4	Thr	Oct	14	100	Inductive datatypes [coq4.v] [coq4-2.v] [coq4.pdf]	By class, Oct 21
P5	Tue	Oct	26	100	Inductive predicates [coq5.v] [coq5.pdf] Inductive proofs [coq6.v] [coq6.pdf]	By class, Nov 2
P6	Tue	Nov	2	100	Pythagorean theorem [coq7.v] [coq7.pdf]	By class, Nov 9
P7	Tue	Nov	23	100	Type safety of simply-typed lambda calculus [coq8.v] [coq8.pdf]	By 9:30am, Nov 30
P10	Thu	Dec	9	100	Decision procedure [PDF] [sources.cm, prop.sml, prover.sml]	By class, Dec 16

P = Programming, W = Written, (points) = Extra-credit