Assignments for UCLA Computer Science 35L, Winter 2016

[35L home]

Most assignments are divided into two parts: laboratory exercises and homeworks. Laboratory exercises are expected to be done in the lab session, that is, the week before the assignment is due. You are expected to take lab notes in the form of a log of your actions that contains enough information so that others can reproduce your work.

The last assignment (assignment 10) is special. It is a research and development assignment, where you are expected to do a brief research report and make a presentation to others in the lab. Your instructor will coordinate with you about scheduling your presentations. The material presented is considered to be part of the course and may appear on the final exam, so pay attention to everybody's presentations!

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. In these cases, 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 int type, but it is not OK to impose an arbitrary limit, e.g., a limit of at most 255 characters in a symbol.

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 2–9 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 assignment
2016-01-08 1. Getting to know your system
2016-01-15 2. Shell scripting
2016-01-25 3. Modifying and rewriting software
2016-01-29 4. Change management
2016-02-05 5. C programming and debugging
2016-02-12 6. SSH setup and use in applications
2016-02-22 7. System call programming and debugging
2016-02-26 8. Multithreaded performance
2016-03-04 9. Dynamic linking
2016-03-11 10. Research and development in computing (No late submissions allowed for this assignment.)

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

© 1999, 2003–2016 Paul Eggert. See copying rules.
$Id: assign.html,v 1.99 2016/01/26 01:16:13 eggert Exp $