15-122 Principles of Imperative Computation
|Asst 1||Thu Aug 26||50||Homework 1 handout||Written||Thu Sep 2 at start of lecture|
|Homework 1 starter code||Programming||Thu Sep 2 11:59pm|
|Asst 2||Wed Sep 8||50||Homework 2 handout||Written||Tue Sep 14 at start of lecture|
|Homework 2 starter code||Programming||Tue Sep 14 11:59pm|
|Asst 3||Fri Sep 17||50||Homework 3 handout||Written||Thu Sep 23 at start of lecture|
|Homework 3 starter code||Programming||Fri Sep 24 11:59pm|
|Asst 4||Tue Oct 5||50||Homework 4 handout||Written||Tue Oct 12 at start of lecture|
|Homework 4 starter code||Programming||Tue Oct 12 11:59pm|
|Asst 5||Fri Oct 15||50||Homework 5 handout||Written||Thu Oct 21 at start of lecture|
|Homework 5 starter code||Programming||Fri Oct 22 11:59pm|
|Asst 6||Wed Oct 27||50||Homework 6 handout||Written||Tue Nov 2 at start of lecture|
|Homework 6 starter code||Programming||Tue Nov 2 11:59pm|
|Asst 7||Wed Nov 10||50||Homework 7 handout||Written||Tue Nov 16 at start of lecture|
|Homework 7 starter code||Programming||Wed Nov 17 11:59pm|
|Asst 8||Sat Nov 20||100||Homework 8 handout||Written||none|
| Homework 8 starter code,
Homework 8 code update,
Some homework 8 test cases
|Programming||Fri Dec 3 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. Every student has up to 3 late days to use for any programming assignment throughout the semester. On any given assignment, you may use at most one late date, so if the assignment is due on 11:59pm on Thursday the last possible time to hand in an assignment is 11:59pm on the next day (Friday). Late submissions from students who have exhausted their late days will receive no credit.
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.
Detailed 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.