Assignments for UCLA Computer Science 97, spring 2020

[97 home]

Most assignments are divided into two parts: laboratory exercises and homeworks. Laboratory exercises are expected to be done with more assistance from the TAs and LAs.

Submit your assignments electronically on CCLE.

You are expected to do your homeworks by yourself. You can share ideas and discuss general principles with others in the class, but all the code and writings that you submit must be your own work; do not share them with others. Please see Grading for more details. Consult a TA or the instructor if you have any questions about this policy.

Typically, labs and homeworks are done on GNU/Linux based systems running on your own computer, either natively or in a virtual machine. In some cases, though, they are done on the SEASnet GNU/Linux servers. Also, even when you develop on your own system, you should test on the SEASnet GNU/Linux servers as that's what we use to grade. When running on SEASnet, take care to not run commands like su and sudo that would make it appear to the system administrators that you might be trying to break into the system.

Any programs that you write must behave robustly. Among other things, this means they must avoid arbitrary limits on the length or number of any data structure, including symbols, strings, and line length. It is OK to impose a non-arbitrary limit, e.g., because your computer runs out of memory or because of the limited range of the C ptrdiff_t type, but it is not OK to impose an arbitrary limit, e.g., a limit of at most 255 bytes in a line.

Please stick to coding styles used in the course material rather than inventing your own style, as this saves work for the grader.

Assignments are due by 23:55 on the specified date (i.e., five minutes before midnight at the end of the day).

Assignments 3–4 and their schedule are tentative. Before the week that each of these assignments is to be done, these assignments might change. Any such changes will be noted in the news.

due % of total grade assignment
2020-04-13   0.75% 1a. Editing and scripting (except Exercise 1.7 and Python scripting)
2020-04-16   0.75% 1b. Editing and scripting (Exercise 1.7 and Python scripting)
2020-04-28   0.75% 2a. Change management (Laboratories A and B)
2020-04-29   1.00% One-page project proposals due
2020-05-02   0.75% 2b. Change management (Homework)
2020-05-05   1.00% Initial project schedule and plan
2020-05-08   0.25% First feedback survey (no late submissions)
2020-05-13   1.00% 3. Chorus lapilli
2020-06-03   1.00% 4. Low-level refactoring and performance
2020-06-04 Project source code
2020-06-05 Project final report

See the project page for the overall structure of the project. Remaining due dates and homeworks are to be determined.

Please see the grading policy for how assignments are treated when late.