15-122 Principles of Imperative Computation
|Asst 0||Mon May 21||0||Getting Started||Wed May 23 at start of lecture|
|Asst 1||Thu May 24||50||Assignment 1 Theory||Written||Mon May 28 at start of lecture|
|Writeup UPDATED Starter Code fixed image||Programming||Monday May 28 11:59pm|
|Asst 2||Mon May 28||50||Assignment 2 Theory||Written||Thu May 31 at start of lecture|
|Writeup Starter Code||Programming||Thu May 31 11:59pm|
|Asst 3||Thu May 31||50||Assignment 3 Theory||Written||Thur June 7 at start of lecture|
|Writeup Starter Code||Programming||Thur June 7 11:59pm|
|Asst 4||Wed June 6||50||Assignment 4 Theory, LaTex||Written||Tues June 11 at start of lecture|
|Writeup Starter Code||Programming||Tues June 11 11:59pm|
|Asst 5||Mon June 11||50||Assignment 5 Theory, LaTex||Written||Thu June 14 at start of lecture|
|Writeup Starter Code||Programming||Fri June 15 11:59pm|
|Asst 6||Thu June 14||50||Assignment 6 Theory, LaTex||Written||Mon June 18 at start of lecture|
|Writeup Starter Code||Programming||Mon June 18 11:59pm|
|Asst 7||Mon June 18||50||Assignment 7 Theory, LaTex||Written||Fri June 22 at start of lecture|
|Writeup Starter Code||Programming||Fri June 22 11:59pm|
|Asst 8||Thu June 21||100||Assignment 8 Theory||Written||none|
|Writeup UPDATED Starter Code||Programming||Thur June 28 at 11:59pm|
The university policies and procedures on academic integrity will be applied rigorously.
The value of your degree depends on the academic integrity of yourself and your peers in each of your classes. It is expected that, unless otherwise instructed, the work you submit as your own will be your own work and not someone else's work or a collaboration between yourself and other(s).
Please read the University Policy on Cheating and Plagiarism carefully to understand the penalties associated with academic dishonesty at CMU. In this class, cheating/copying/plagiarism means copying all or part of a program or homework solution from another student or unauthorized source such as the Internet, knowingly giving such information to another student, or giving or receiving unauthorized information during an examination. In general, each solution you submit (quiz, written assignment, programming assignment, midterm or final exam) must be your own work. In the event that you use information written by another person in your solution, you must cite the source of this information (and receive prior permission if unsure whether this is permitted).
Your course instructor reserves the right to determine an appropriate penalty based on the violation of academic dishonesty that occurs. Violations of the university policy can result in severe penalties including failing this course and possible expulsion from Carnegie Mellon University. If you have any questions about this policy and any work you are doing in the course, please feel free to contact your instructor for help.
We will be using the Moss system to detect software plagiarism.
It is not considered cheating to clarify vague points in the assignments, lectures, lecture notes, or to give help or receive help in using the computer systems, compilers, debuggers, profilers, or other facilities.
All handins of written assignments are on paper at the beginning of lecture (9:00am) on the due date. Assignments handed in after this time will receive no credit. There are no late days or partial credit for late written assignments.
All handins of programming assignments are electronic via hand-in scripts on the university's linux systems. You may submit programs multiple times until they are due without penalty, but only your final hand-in will be graded.
All programming assignments are due at 11:59pm on the specified due date. There are no late days for the summer version of this course.
Exceptions to the policies above will be granted only in exceptional circumstances and must be discussed with and approved by the course instructor in advance.
Grading criteria are stated separately with each assignment.
Grading for written assignments is based on the correctness of the answer and the presentation of your reasoning. Strive for clarity and conciseness, but show how you arrived at the answer. If you cannot solve a problem, explaining your approach and why you failed is encouraged. Such answers will be given partial credit.
The most important criterion for programming assignments is always correctness. Buggy code is useless, and is likely to get a low score. It is important that your code be readable and well-organized. This includes proper use of contracts, invariants, and clear comments.
Grades are based primarily on the total score for the class out of 1000 points. There are no predetermined cut-offs, but 900 and above is guaranteed to be an A, 800 and above a B, etc. The teaching staff will decide on grade boundaries at the end of the year. We will use intangibles, such as participation in class and recitation for those close to grade boundaries.