15-150: Functional Programming, Spring 2020

Academic Integrity

All students are expected to read, be familiar with, and comply with, the CMU Policy on Academic Integrity.

In addition you must read, be familiar with, and comply with the following 15-150 policy rules:

Any work submitted as a homework assignment or an examination must be entirely your own, developed this semester, and must not be derived in part or whole from work of others. For homework assignments, you may discuss problems with other students who are currently in the course, but only as outlined in the section about cooperative learning below. You may consult a current teaching assistant for this course or a tutor provided by Academic Development, but you should not ask these individuals for detailed help in writing homework solutions.

You must not search the internet (or library or other external source) for homework or exam solutions, and you must not use solutions developed in prior semesters of this course or in related courses. If you took this course in a prior semester you are not allowed simply to hand in verbatim copies of any solutions from before, including your own work. You may consult your own prior work in developing new solutions, but you should write all your work for this semester from scratch.

You must not look at or alter any part of anyone else's homework solution or exam paper. In particular, you must not copy, use as a guide, or cut-and-paste, any homework solutions or exam solutions of another student, or provide such solutions to another student.

You should take appropriate care to prevent other students from cheating, by safeguarding your own work with proper protection to ensure privacy, and by not allowing other students to have access to your files or computer.

If you have any question about what is appropriate, please ask the course staff.

Cooperative Learning

To facilitate overall learning, it is permissible for you to discuss lecture notes and conceptual topics with others. It is also permissible for you to discuss a homework assignment with other students who are currently in the course, provided that you adhere to the following policy:

Citing sources: For each assignment, you should submit a file called collab.txt in which you describe any discussions you had with other students and cite any other sources. (For instance, if you took this course in a previous semester and are referring to any material from that course, including your own work, you should also report that in this file.) Here are two examples of entries that we might expect to see in two different collab.txt files for two students who discussed a problem on an assignment:

Notice that both students should describe the discussion, even if information flows in one direction. Of course, this is an extreme case, and in general we would hope to see examples of entries suggesting a two-way discussion.

We may run automatic code comparison software (such as MOSS) on homework submissions to compare solutions from this semester and solutions from earlier semesters. This software is very good at detecting similarities that suggest collaboration or other cheating during code design, even after an attempt to obfuscate. The signal-to-noise ratio in MOSS reports is usually very distinctive, so we can tell if any part of a student's handed in work is derived from some other source. If MOSS detects a collaboration not reported in collab.txt, that will raise a red flag and may be considered cheating or plagiarism.

Violations of the policy outlined above will be investigated, and may result in zero scores on any assignments brought under suspicion and a report to the university authorities. This may also lead to a disciplinary hearing followed by suspension or expulsion from the university. In short: don't cheat! It isn't worth the risk.

Homework Assignments


Each student has 3 grace days available to them during the course of the semester. You may use a maximum of one grace day on any assignment, and they are applied automatically. To use a grace day on an assignment, submit your work for the assignment by Wednesday at 11:59 PM. Autolab may show this as a penalty late day, but don't worry about that since we'll separately count how many grace days you've used. If you submit past Wednesday at 11:59 PM or attempt to use a grace day when you have none remaining, then you will get a 0 on the assignment.

The semester moves quickly and it is important that you don't fall behind. As a result, in general there will be no extensions on assignments. If you think you really really need an extension on a particular assignment (e.g., due to severe illness or major personal/family emergencies), contact the instructor as soon as possible before the deadline. Please be aware that extensions are entirely discretionary and may not be granted. The instructor will most likely require confirmation from University Health Services or your academic advisor, as appropriate.

Late work without an extension will not be accepted.

Please don't ask for an extension in place of using a grace day.

(The purpose of grace days is so that you can quickly give yourself a 1-day extension, for any reason you choose. This includes out-of-town trips, health issues, lack of time, WiFi problems, car trouble, etc. Grace days are not intended solely as a time-management tool, but a convenient way to give yourself an extension.)


Any source code that you submit must compile cleanly with an unmodified version of the starter code for that assignment. If you submit source code that does not compile cleanly, you will lose a significant amount of credit for that assignment. In particular, the TAs will not grade any of your code.


Each homework assignment will come with a check script. We will not grade assignments that do not pass all of the checks. You should not consider your assignment submitted until you have run the check script and passed all the tests.

The script verifies some very basic properties about your submission: that none of the files have zero size; that all the files are named correctly; that your code compiles with clean copies of any starter code; that any PDFs seem to be valid; etc. In particular, it is not a grading script. Passing the check script means that your assignment will be graded; it does not mean anything about the score you will receive on it.

You should submit written answers as typeset PDFs on Gradescope. Please be sure to select the correct pages for each question on Gradescope. The PDFs that you submit containing your written answers must be valid and complete. Invalid PDFs will not receive credit for anything that might have been in them. Be careful to submit your solution PDF for an assignment, not the assignment writeup or some other PDF; those are invalid submissions.

After submitting an assignment, verify that you submitted everything properly, by examining the submission on Autolab or Gradescope. It is your responsibility to ensure that the assignment was submitted properly. Leave plenty of time for this visual verification; last minute submissions are very very risky.


You can find the official style guide on the tools page. Violating the mandatory style guidelines on a homework will result in losing style points for that assignment. These style deductions are permanent.


There will be two midterms and one final examination in this course. The midterms will be given during a class period, the final as scheduled by the registrar.

You may bring one double-sided 8.5" x 11" page of notes to each examination. You may not refer to any other person or source, besides the course staff, during the examination.

Please bring a pen to the midterms, as we will ask you to write your answers in blue or black ink.
(You may write in pencil on the final exam, if you wish. We will keep the final exams.)

Missed examinations count as zero credit. Showing up late for an examination does not extend the end time of the exam. Except in the case of dire medical or family emergencies, no make-up examinations will be administered.

You must take the midterms and final exams to pass the class. Failure to take an examination will result in a failing grade for the course.


Lab attendance is mandatory and is worth 10% of your grade. If for an official reason (i.e., interview, conference, special academic event, etc.) you cannot attend lab, you can still receive credit by (1) informing your lab TAs before the lab you are going to miss and (2) completing the lab writeup and showing your solutions to a TA (possibly in some office hours) up to a week after the lab.

Taking Notes

Please take notes by writing or typing. Do not record or tape lectures electronically, whether by audio or video.

Specifically: No student may record or tape any classroom activity without the express written consent of the instructor. If a student believes that he/she is disabled and needs to record or tape classroom activities, he/she should contact the Office of Disability Resources to request an appropriate accommodation.

Grading Policy

last modified 15:50, 16 Jan 2020