About this course  [  Description  |  How to Do Well  |  Readings  |  Software  |  Grading  |  Policies  |  Help  |  Learning Objectives  ]

This course teaches imperative programming in a C-like language and methods for ensuring the correctness of imperative programs. It is intended for students who are familiar with elementary programming concepts such as variables, expressions, loops, arrays, and functions. Given these building blocks, students will learn the process and techniques needed to go from high-level descriptions of algorithms to correct imperative implementations, with specific applications to basic data structures and algorithms. Much of the course will be conducted in a subset of C amenable to verification, with a transition to full C near the end. This will be accomplished along three dimensions:

• The main skill you will get out of this course is the ability to write code that is correct by design and accounts for the needs of its application context. You will learn about deliberate programming as a way to write high quality code, about assessing the performance of a program, and about comparing solutions to satisfy deployment constraints.
• As we do so, you will gain exposure to fundamental concepts in Computer Science — as opposed to programming — such as abstraction, correctness, complexity, and modularity. This will also give you a vocabulary to communicate effectively and precisely with other computer scientists.
• Our vehicle for achieving these objectives will initially be C0, a safe variant of C, and later C itself. Using them, you will gain exposure to a number of data structures and algorithms that are used pervasively in computer science. C is the language of choice for system-level code, and both are representative of the popular imperative programming paradigm.

After completing 15-122, you will be able to take 15-213 (Introduction to Computer Systems), 15-210 (Parallel and Sequential Data Structures and Algorithms) and 15-214 (Principles of Software System Construction). Other prerequisites or restrictions may apply.

Prerequisites

You must have gotten a 5 on the AP Computer Science A exam or passed 15-112 (Fundamentals of Programming) or equivalent. You may also get permission from an advisor if you performed very high on the CS Assessment on Blackboard.
It is strongly advised that you either have taken or take at the same time either 21-127 (Concepts of Mathematics) or 15-151 (Mathematical Foundations of Computer Science): historically, students who did not do so ended up learning less, spending considerably more time on the course and earning one letter grade lower than their peers who did, on average.

Past Offerings

N'18 S'18 F'17 N'17 S'17 F'16 N'16 S'16 F'15 M'15 S'15 F'14 M'14 S'14 F'13 M'13 S'13 F'12 M'12 S'12 F'11 M'11 S'11 F'10

Our goals are for you to succeed in this course and to teach you skills and concepts that will contribute to your success in life. To this end, we are providing you with lots of resources and the knowledge that comes from years of experience. Talking to some of the thousands of students who took this course before you, here's some advice that they found particularly useful:

• Do not stress over grades: your goal is to learn new and exciting things. Good grades follow naturally from deep learning (but not necessarily vice versa). ...and employers care about what you know not what grade you got.
• Participate: you will get a lot more from this class if you ask questions and engage with the course staff than if you are a fly on the wall — and it will be more fun.
• Manage your time wisely: allocate sufficient time for homework and learning. Little adjustments can save you a whole lot of time later and have a huge impact on your performance. In particular, use class time to learn, review the material presented in lecture the same day, and schedule time for homework proactively.
• Start homework early: racing against a deadline is so stressful! Starting early will remove that stress, lead to deeper learning and give you time to improve your solution if you feel like it.
• Get all the help you need: we provide plenty of resources to help you succeeed in this course — office hours every day, online help 24-7, and friendly staff when you need them. Take advantage of them: they are there for you! The only thing we ask is that you plan a bit ahead: helping students takes time and there are not enough of us if everybody waits up to the deadline.
• Make time for fun: take a break from studying at least once a day — meet with friends, go for a walk, play sports, whatever gets you to reset your mind.

Feedback

It is our goal to make this course successful, stimulating and enjoyable. If at any time you feel that the course is not meeting your expectations or you want to provide feedback on how the course is progressing for you, please contact us. If we are not aware about a problem, we won't know to fix it. If you would like to provide anonymous comments, please use the feedback form on the course home page or slide a note under our doors. Comments of general interest will be answered on the course discussion board.

There is no textbook for this course. Lecture notes and other resources are provided through the Schedule tab of this page. We do not require students to read lecture notes before lecture, but those who are interested in reading ahead can certainly do so.

The C0 Language

In the first nine weeks, the course uses C0, a safe subset of C augmented with a layer to express contracts. This language has been specifically designed to support the student learning objectives in this course. It provides garbage collection (freeing students from dealing with low-level details of explicit memory management), fixed range modular integer arithmetic (avoiding complexities of floating point arithmetic and multiple data sizes), an unambiguous language definition (guarding against relying on undefined behavior), and contracts (making code expectations explicit and localizing reasoning).

C0 Language Reference C0 Tutorial C0 Library Reference Debugging C0 Programs Testing programs

C0 at CMU C0 on your own laptop

The C Language

In the last six weeks, the course transitions to C in preparation for subsequent systems courses. Emphasis is on transferring positive habits developed in the use of C0, and on practical advice for avoiding the pitfalls and understanding the idiosyncrasies of C. We use the valgrind tool to test proper memory management.

• From C0 to C: Basics tutorial
• C Language Libraries
  • C string library <string.h>
• POSIX library standard — Unix standard library definitions including a library search functionality

Programming Environments

You are welcome to use any programming environment that suits you to write your programming assignments. However, all programming homework will be graded by running them on a Unix system using Autolab — you may want to make sure they work on Andrew Unix. Popular environment choices include emacs, vim and sublime, but you should use what works for you: an environment that allows you to write code quickly and efficiently. Here are some useful links:

Unix	Emacs
Linux Commands Reference Card	Emacs Basics Game for learning emacs shortcuts Emacs Help Guide

This is a 10 unit course.

Tasks and Percentages

• 25 homework assignments: 45%
  • 13 weekly written assignments (due on Gradescope Mondays at 9pm — strict!)
  • 12 weekly programming assignments (due on Autolab Thursdays at 9pm — strict!)
  To encourage good work and integrity, the instructors may invite students to their offices to explain their solutions. Should this happen, the students' explanations will become part of their grades for that homework.
  • Assignments are individual unless explicitly instructed.
• 2 midterm exams: 12.5% each, in class, closed books, on and
• Final exam: 25%, 3 hours, closed books, on
• Labs and quizzes: 5%
  Each lab is graded on a 0-3 point scale, assigned as follows:
  • 3 points for completing all exercises
  • 2 points for completing sufficiently many exercises
  • 1 point for completing some exercises but not quite enough to get a good practice
  • 0 points for not completing any exercise, not showing up, or coming to the wrong section
  Each quiz is graded based on the number of questions it asks. Use the quiz page to test your configuration and take there current quiz (if there is one).
  All you need to earn the 5% grade for this portion of the course is to accumulate 50 points overall. There are many more points than that for grabs, so no sweat if you do poorly in one quiz or miss a lab. Do the math: the course has
  • 13 graded labs
  • a few quizzes (done during lecture and/or recitation)

We are aiming to have homework and exams graded within two days of submission.

Accessing and Monitoring your Grades

Posted grades are accessible by clicking on the Grades tab of this page. After authenticating, you will be able to see your current grades and a projection of where you are headed given your past performance in the class. Use this application to take action if the trajectory does not lead to the grade you are hoping for.

Evaluation Criteria

Your assignments and exams are evaluated on the basis of:

• Correctness: Your arguments should make sense, your proofs should be valid, and your program should work in the reference environment.
• Elegance: Written material should be of the same quality as what a professional would write. No typos, no bad grammar, clarity is paramount. You are also expected to write code with good programming style. See these notes about what constitutes good style.
  For a small subset of assignments, the course staff will review all final submissions by hand. If there are significant style issues, they may give a non-passing grade on style, accompanied by a “FIX STYLE” annotations in their notes. Students who are told to fix their style must address these issues and discuss their revisions with a TA within 5 days of the homework grades being posted. Any TA or instructor can do style re-grading at any office hour; you do not have to go to the TA that assigned the grade.

Late Policy

This is a fast-paced course. The late policy has the purpose to help students from falling behind.

• There are no late days for written assignments, but written homework will be accepted up to 12 hours past the deadline and eligible for 50% of the points. Gradescope handles late submissions automatically — you don't have to email the course staff, just turn in the assignment between 1 second late and 12 hours after the deadline.
• Each student has 3 late days for programming assignments but you may use at most one late day for each individual assignment. This means that for exactly 3 programming deadlines you can turn in your assignment within 24 hours after the deadline. Autolab handles these late days automatically — you don't have to email the course staff, just turn in the assignment between 1 second late and 24 hours after the deadline. You can find how many late days you have used by clicking on "Gradebook" in Autolab.

  We strongly advise students not to use late days in the first half of the course. Later assignments are more challenging and many courses have lots of deliverables towards the end of the semester. The second half of the semester is where late days are most needed.

Aside from this, there will be no extensions on assignments in general. If you think you really really need an extension on a particular assignment, contact the instructors as soon as possible and before the deadline. Please be aware that extensions are entirely discretionary and will be granted only in exceptional circumstances outside of your control (e.g., due to severe illness or major personal/family emergencies, but not for competitions, club-related events or interviews). The instructors will require confirmation from University Health Services or your academic advisor, as appropriate.

Nearly all situations that make you run late on an assignment homework can be avoided with proper planning — often just starting early. Here are some examples:

• I have so many deadlines this week: you know your deadlines ahead of time — plan accordingly.
• It's a minute before the deadline and the network is down: you always have multiple submissions — it's foolish to wait for the deadline for your first submission.
• My computer crashed and I lost everything: Use Dropbox or similar to do real-time backup — recover your files onto AFS and finish your homework from a cluster machine.
• My fraternity/sorority/club has that big event that is taking all my time: Schedule your extra-curricular activities around your classes, not vice versa.

Grade Appeals

We make mistakes too!
After each exam and homework assignment is graded, you will be able to access your score by clicking on the Grades tab of this page. We will make the utmost effort to be fair and consistent in our grading. If you notice any grading mistake, proceed as follows:

• Blatant grading mistakes (e.g., the rubric says X, and you wrote X exactly) can be corrected by any TA in office hours.
• For any other grading issues, you must request a regrade:
  • Compose a properly typed letter explaining where and why you think there was a mistake in grading. Make sure to specify which homework or exam this appeal is for. Write at most 3 lines for each response you are disputing. Date and sign your letter by hand.
  • Hand-deliver a signed hardcopy of this letter to in . Slide it under her door if she is not in.

Verbal, email or handwritten requests will not be accepted.

All regrade requests must be recieved within 5 days of the work being handed back on Gradescope or Autolab, which we will announce in a Piazza post.

Final Grades

This class is not curved.

What follows is a rough guide to how course grades will be established, not a precise formula — we will fine-tune cutoffs and other details as we see fit after the end of the course. This is meant to help you set expectations and take action if your trajectory in the class does not take you to the grade you are hoping for (see also the Grades tab on this page). So, here's a rough, very rough heuristics about the correlation between final grades and total scores:

• A: above 90%
• B: 80-90%
• C: 70-80%
• D: 60-70%

This heuristic assumes that the makeup of a student’s grade is not wildly anomalous: exceptionally low overall scores on exams, programming assignments, or written assignments will be treated on a case-by-case basis. In particular, no student will get an A with an exam average below 80% (no matter how high his/her total score). Furthermore, students who are unable to demonstrate a basic proficiency with the C language in the last few programming assignments will receive a D in the class (this is because 15-122 is a prerequisite to 15-213, a very C-intensive course). For reference, almost a quarter of the students who received a B in Fall 2014 had a 90-100% average on programming assignments, an 80-90% average on written homeworks, and a 70-80% average on exams.

Precise grade cutoffs will not be discussed at any point during or after the semester. For students very close to grade boundaries, instructors may, at their discretion, consider participation in lecture and recitation, exam performance and overall grade trends when assigning the final grade.

Academic Integrity

You are expected to comply with the University Policy on Academic Integrity and Plagiarism (see also The Word and Understanding Academic Integrity).

The university policies and procedures on academic integrity will be applied rigorously. All students are required to fill out a form as part of their first assignment indicating that they understand and accept this policy.

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 is your own work and not someone else’s work or a collaboration between yourself and other(s).

You are allowed to discuss homework assignments at a high level with other students. However, in order to ensure that the work you submit is still your own, we insist that you adhere to a whiteboard policy regarding these discussions:

• You are not allowed to take any notes, files, pictures or other records away from the discussion, nor shall you memorize answers.
• Writing code or pseudo-code on a whiteboard is never permitted. You may only draw diagrams.
• You are not allowed to write any code on a computer while discussing ideas with another student
• You must wait some time (4 hours is a safe heuristic) before writing up or coding your own solution.

For example, you may work on a homework at the whiteboard with another student, but then you must erase the whiteboard, go home, wait 4 hours, and write up your solution individually. We take your ability to recreate the solution independently as proof that you understand the work that you submit.

This policy is our attempt to balance the tension between the benefits of group work and the benefits of individual work. We ask that you obey the spirit of the policy, as well as the letter: ensure that all work you submit is your own and that you fully understand the solution. This is in your best interest: the exams constitute a significant part of your final grade, they will be timed, and they will draw heavily on the terminology, concepts, and techniques that are exercised in homework. It is unlikely that you will be able to do well on the exams if you do not take full advantage of the learning opportunity afforded by the homework assignments. Moreover, we will aggressively pursue violations.

Please read the University Policy on Academic Integrity carefully to understand the penalties associated with academic dishonesty at Carnegie Mellon. 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, having someone else do a homework or take an exam for you, knowingly giving such information to another student, reusing answers or solutions from previous editions of the course, 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). It is considered cheating to compare complete or partial answers, copy or adapt others' solutions, or sit near another person who is taking (or has taken) the same course and complete the assignment together. Working on code together, showing code to another student and looking at another student's code are considered cheating. If you need help debugging, go to office hours or make a post on Piazza. It is also considered cheating for a repeating student to reuse one's solutions from a previous semester, or any instructor-provided sample solution. It is a violation of this policy to hand in work for other students.

Your course instructor reserves the right to determine an appropriate penalty based on the violation of academic dishonesty that occurs. Penalties are severe: a typical violation of the university policy results in the student failing this course, but may go all the way to 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 the instructors for help.

We will be using the Moss system to detect software plagiarism. Whenever a programming assignment is similar to a homework from a previous course edition, we will running MOSS on all submissions of that edition as well.

It is not considered cheating to clarify vague points in assignment writeups, lectures, lecture notes, or to give help or receive help in using the computer systems, compilers, debuggers, profilers, or other facilities, but you must refrain from looking at other students' code while you are getting or receiving help for these tools. It is not cheating to review graded assignments or exams with students in the same class as you, but it is considered unauthorized assistance to share these materials between different iterations of the course. Do not post code from this course publicly (e.g., to Bitbucket or GitHub).

Repeat Students

If you took this course in full or in part in a past semester, we ask that you archive your previous work and do not look at it. In particular, copying one's own solutions from an earlier semester is a violation of the academic integrity policy and will be persecuted as such. Doing so may save time close to a deadline but it will not have the effect of learning the material, which will be a serious handicap in exams.

Class presence and participation

Active participation by you and other students will ensure that everyone has the best learning experience in this class. We may take participation in lecture and recitation into account when setting final grades. Fire safety rules require that we never exceed the stated capacity of a classroom or cluster. For this reason, we require that you attend the lecture, lab, and recitation you are registered for.

Laptops and mobile devices

As research on learning shows, unexpected noises and movement automatically divert and capture people’s attention, which means you are affecting everyone's learning experience if your cell phone, pager, laptop, etc, makes noise or is visually distracting during class. Therefore, please silence all mobile devices during class. You may use laptops for note-taking only, but please do so from the back of the classroom. Do not work on assignments for this or any other class while attending lecture or recitation.

Students with disabilities

If you wish to request an accommodation due to a documented disability, please inform your instructor and contact Disability Resources as soon as possible (). Once your accommodation has been approved, you will be able to request extra-time for each exam separatelyby filling this form a week in advance.

Personal Health

Take care of yourself.

Do your best to maintain a healthy lifestyle this semester by eating well, exercising, avoiding drugs and alcohol, getting enough sleep and taking some time to relax. This will help you achieve your goals and cope with stress.

All of us benefit from support during times of struggle. You are not alone. There are many helpful resources available on campus and an important part of the college experience is learning how to ask for help. Asking for support sooner rather than later is often helpful.

If you or anyone you know experiences any academic stress, difficult life events, or feelings like anxiety or depression, we strongly encourage you to seek support. Counseling and Psychological Services (CaPS) is here to help: call 412-268-2922 and visit their website. Consider reaching out to a friend, faculty or family member you trust for help getting connected to the support that can help.

If you or someone you know is feeling suicidal or in danger of self-harm, call someone immediately, day or night:

CaPS: 412-268-2922

Re:solve Crisis Network: 888-796-8226

If the situation is life threatening, call the police:

• On campus (CMU Police): 412-268-2323
• Off campus: 911

If you have questions about this or your coursework, please let us know.

Communication

For assistance with the written or oral communication assignments in this class, visit the Global Communication Center (GCC). GCC tutors can provide instruction on a range of communication topics and can help you improve your papers and presentations. The GCC is a free service, open to all students, and located in Hunt library. You can make tutoring appointments directly on the GCC website. You may also visit the GCC website to find out about communication workshops offered throughout the academic year.

Computational Thinking

Students who complete this course should be able to explain abstraction and other key computer science concepts, apply these fundamental concepts as problem-solving tools, and wield contracts as a tool for reasoning about the safety and correctness of programs. In particular, we expect students to be able to:

1. develop contracts (preconditions, postconditions, assertions, and loop invariants) that establish the safety and correctness of imperative programs.
2. develop and evaluate proofs of the safety and correctness of code with contracts.
3. develop and evaluate informal termination arguments for programs with loops and recursion.
4. evaluate claims of both asymptotic complexity and practical efficiency of programs by running tests on different problem sizes.
5. define the concept of programs as data, and write programs that use the concept.
6. defend the use of abstractions and interfaces in the presentation of algorithms and data structures.
7. identify the difference between specification and implementation.
8. compare different implementations of a given specification and different specifications that can be applied to a single implementation.
9. explain data structure manipulations using data structure invariants.
10. identify and evaluate the use of fundamental concepts in computer science as problem-solving tools:
    1. order (sorted or indexed data),
    2. asymptotic worst case, average case, and amortized analysis,
    3. randomness and (pseudo-)random number generation, and
    4. divide-and-conquer strategies.

Programming Skills

Students who complete this course should be able to read and write code for imperative algorithms and data structures. In particular, we expect students to be able to:

1. trace the operational behavior of small imperative programs.
2. identify, describe, and effectively use basic features of C0 and C:
   1. integers as signed modular arithmetic,
   2. integers as fixed-length bit vectors,
   3. characters and strings,
   4. Boolean operations with short-circuiting evaluation,
   5. arrays,
   6. loops (while and for),
   7. pointers,
   8. structs,
   9. recursive and mutually recursive functions,
   10. void pointers and casts between pointer types,
   11. contracts (in C0), and
   12. casts between different numeric types (in C).
3. translate between high-level algorithms and correct imperative code.
4. translate between high-level loop invariants and data structure invariants and correct contracts.
5. write code using external libraries when given a library interface.
6. develop, test, rewrite, and refine code that meets a given specification or interface.
7. develop and refine small interfaces.
8. document code with comments and contracts.
9. identify undefined and implementation-defined behaviors in C.
10. write, compile, and test C programs in a Unix-based environment using make, gcc, and valgrind.

Algorithms and Data Structures

Students who complete this course should be able to describe the implementation of a number of basic algorithms and data structures, effectively employ those algorithms and data structures, and explain and interpret worst-case asymptotic complexity arguments. In particular, we expect students to be able to:

1. determine the big-O complexity of common code patterns.
2. compare common complexity classes like O(1), O(n), O(n log(n)), O(n2), and O(2n).
3. explain the structure of basic amortized analysis proofs that use potential functions.
4. apply principles of asymptotic analysis and amortized analysis to new algorithms and data structures.
5. recognize properties of simple self-adjusting data structures.
6. recognize algorithms and data structures using divide-and-conquer.
7. describe and employ a number of basic algorithms and data structures:
   1. integer algorithms,
   2. linear search,
   3. binary search,
   4. sub-quadratic complexity sorting (mergesort and quicksort),
   5. stacks and queues,
   6. pseudo-random number generators,
   7. hash tables,
   8. priority queues,
   9. balanced binary search trees,
   10. disjoint-set data structures (union/find), and
   11. simple graph algorithms.