Exams
| Exam | Time | Info |
|---|---|---|
| MT1 | Thurs, Oct. 16th at 7 PM Pacific | Info |
| MT2 | Thurs, Nov. 20th at 7 PM Pacific | Info |
| Final | Sat, Dec. 13th at 11 AM Pacific | Info |
Homework and Projects
| Item | Title | Due (at 11:59PM Pacific) | Access Link |
|---|---|---|---|
| HW1 | Arrays and C-Strings | Thurs, Sept. 11 | Codio via BSpace |
| PR1 | Twentyone | Thurs, Sept. 18 | Codio via BSpace |
| HW2 | Pointers and Dynamic Memory | Thurs, Oct. 2 | Codio via BSpace |
| PR2 | Connect 4 | Wed, Oct. 8 | Codio via BSpace |
| HW3 | Classes | Thurs, Oct. 23 | Codio via BSpace |
| HW4 | Linked Lists & Vectors | Thurs, Oct. 30 | Codio via BSpace |
| PR3 | Maze Search | Thur, Nov. 6 | Codio via BSpace |
| HW5 | Operators and Copy Semantics | Fri, Nov. 21 | Codio via BSpace |
| PR4 | Streaming Service | Mon, Dec. 1 | Codio via BSpace |
| HW6 | Recursion | Thurs, Dec 4 | Codio via BSpace |
Overview
Each unit will have roughly one homework and projects, spanning 1-2 weeks each. Homeworks are low stakes assignments intended to give you practice with the concepts and skills discussed in lecture. Projects then have you deepend and combine concepts in a larger application.
The due dates above are TENTATIVE. As we work through the semester the schedule may change. Any due changes will be posted here, announced on Edstem and changed on Codio.
Coding and Submission Environment
All assignments will be performed on Codio. Instructions, coding, debugging, and submission will all be delivered and performed on Codio. You are welcome to download relevant source files and code on your own environment, but we will not be able to officially support another environment. In addition, to receive credit, you will run automated tests on your assignments, and that must be done on Codio. So if you work in another environment, you will need to upload your code back to Codio to submit and receive credit. Finally, you must mark your assignment complete on Codio for it to be considered submitted.
Policies
The syllabus defines relevant HW policies and Project policies. Those sections define:
- Deadline and late policy
- Collaboration and Academic Integrity policy
- Regrade policy
Below are some additional policies:
- Compiling and Warnings: Many HW and projects require you to compile your code on your own to a particular executable name before the automated tests will run. In this case, you should ensure there are no compiler warnings. If there are please fix them.
- Style: You must follow the style guide outlined here.
