| Probable Assignments. The actual ones will appear on the course Piazza | ||
|---|---|---|
| A0 | Assert statement | Learn about the assert statement and practice using
Eclipse. See pinned Piazza note #8. This helpful ppt file about the assert statement comes from Tony Hoare, author of Quicksort (and more!): Assert early and assert often (ppt) |
| A1 | Classes | Practice developing a class. See pinned Piazza note @13 (when it becomes available) genealogies (pdf files): |
| A2 | Functions | Practice writing Java functions, mainly dealing with Strings. |
| A3 | Linked Lists | Introduce you to linked lists. |
| A4 | Recursion on trees | Write methods to process trees in an interesting application. |
| A5 | Heaps | Implement a heap. |
| A6 | GUIs. | Learn about GUIs. |
| A7 | Shortest path | Implement Dijkstra's shortest path algorithm. |
| A8 | NYC Sewer system | Navigate the NYC sewer system to find a ring and pick up coins. |
| Homework | Description | |
|---|---|---|
| HW1 | Presenting algorithms in English; the assignment statement | |
| Rec 1 | Basics | Java applications, packages, API specs, programming with Strings. |
| Rec 2 | Exceptions | |
| Rec 3 | Invariants | Invariant problem set |
| Rec 7 | Iterable | Iterable problem set |
| Rec 8 | I/O | I/O problem set |
Automated Cheating Detection
We use an automated system that uses sophisticated artificial intelligence techniques combined with program analysis tools to notice unusual similarities between programs turned in by different people. These tools really work and are quite hard to fool. So, while it might seem tempting to borrow a solution from a buddy, change the variable names and comments, or reorder the statements, the tools would be very likely to figure out what you did.
The tool we use, called Moss, was developed by a Cornell PhD, now a professor at Stanford, over 20 years ago.
We take cheating seriously, and cheating with an attempt to cover it up is grounds for failing the course outright. Realistically, it is much easier to just do the assigned problems than to get away with handing in code someone else wrote, because short of rewriting that code completely from scratch, we’ll catch it.
So you’ve been warned: It is difficult to get away with cheating in CS2110. Please do your own work, and talk to an instructor, a TA, or a consultant, as often as needed if you get stuck and need help. We’ll get you back on track.