List of assignments

Common questions about assignments

Written by Pat Hanrahan

What is the expected assignment workload?

There are 7 assignments over the quarter, one per week. Students in previous quarters report spending between 10 and 20 hours completing each assignment. The assignments generally build on each other, so it is hard to skip an assignment. The last assignment will be a project, and you will have two weeks to do the project. The final project is more open-ended than the assignments, and most students will spend more than 20 hours on their final project.

What programming environment and tools are used?

Students will use their own laptop for the assignments. If you use a Mac laptop, you will be using the Terminal program and unix command line tools. If you own a Windows laptop, you will install a virtual machine running Ubuntu linux and you will use the virtual machine for your assignments.

When developing on the Raspberry Pi, you will compile programs on your laptop and download them to the Raspberry Pi. We use a suite of open-source cross-development tools for arm processors. These include the binutil packages of tools, as well as gcc and gdb. Other tools such as make and git will also be used for development. You will also be expected to become proficient using a unix text editor such as emacs or vi, and become proficient using the unix shell.

Assignments are distributed to students as git repositories. Students edit, compile, and debug their assignments on their laptop. When they are finished, they hand in the assignment by committing their files into their personal git repository and creating a pull-request.

When the pull-request is created, code is run through a sanity check to ensure the code compiles. Students should ensure their code aligns with cs107e required assignment directory structure so it passes sanity check and may be evaluated by the graders.

What is the policy on late assignments?

Students are given a few self-granted grace days, a penalty is applied for further late work, and there is a hard deadline after which no further late work will be accepted. Read our detailed late policy for the nitty-gritty mechanics.

What is the assignment collaboration policy?

The programming assignments are to be done individually and should represent independent, original work. We adhere to the Stanford and CS department Honor Code policies, and offer specific examples of its application to CS107E coursework in our course collaboration policy.

The final project can be done solo or in teams of 2 or 3. If working in a team, all partners are expected to contribute equally to the effort.

How do I submit an assignment?

Assignments are submitted online using git. Consult assignment 0 for information about how to use git.

How are assignments graded?

Each assignment will have a clear specification of what the program should do.

We will also look at your code and assess the code quality. Good code should be decomposed into small, clear, well-named functions so that no code is repeated and it is easy to follow the intent of each function. Code quality will be graded on a bucket system where code that needs improvement falls in the [-] bucket, code that meets our expectations is in the [ok] bucket, and exceptional code falls in the [+] bucket. We will also provide comments throughout your code to help you improve your code quality. Please incorporate our feedback into future assignments; it will improve your grade and more importantly your coding style.

Assignments will have a basic part (typically scored out of 10 points) and various extensions (worth 3-5 points depending on how challenging). You are expected to do the basic part of each assignment, and attempt some of the extensions. You can do as many extensions as you want to accumulate additional points.

If we are unable to compile your assignment as is, through some fault of yours (for example, if your assignment fails to compile on CI and you should have fixed it), we will automatically deduct 1 point from the basic part of your grade from that assignment.

As mentioned above, the assignments build on each other. If you do not complete the basic part of an assignment, you may have trouble completing the next assignment. To help you in these situations, we have written reference implementations of the libraries you need. If your version doesn’t work, you can fall back on our version.

The last assignment requires you to use code from many of the previous assignments. To encourage you to complete all assignments and fix any bugs within them, if you hand-in the last assignment using only your own code, we will award you bonus points for building a complete working system.

Course grades will be assigned using the following criteria:

A. All labs attended. Excellent assignments: each submission is complete and fully functional on the basic part of the assignment and 3 or more of the assignment extensions were attempted and successfully completed. You also need to get the full system bonus for using all your own code on the last assignment. Your code quality grades should average toward the [+] bucket. Final project must be outstanding.

B. All labs attended. Solid assignments: each submission is complete and functional on the basic part of the assignment. Your code quality grades should average at/above the [ok] bucket. Good final project.

C and below. All work is not completed satisfactorily.