Assignment A0. Assert statement

It is for you to do as soon as you get Eclipse working and you have been to recitation 01. Purpose of A0: Get you to use Eclipse and learn about the Java assert statement.

For those of you who are interested, we also have ppt slides with notes (as a pdf) written by Sir Tony Hoare on using assert statements --in many programming languages. Tony is one of the significant people in CS, and if you continue with CS courses, you wiill see his name often and read some of his papers dealing with languages, concurrency, and programming. He is Professor Emeritus at Oxford and just retired as principal researcher for Microsoft. He is the author of Quicksort (which you will see later in 2110) and the creator of Hoare Logic for verifying program correctness.

Here, he gives practical hints on using assert statements. Read especially the notes on pages 14-15 about preconditions and postconditions.

A0 handout (pdf)    Assert early and assert often (ppt)

Assignment A1. Classes

The purpose of A1 is to give you practice with developing a class --in this case, one that maintains information about the PhD advisors of a person with a PhD. Along the way, you will practice (1) writing a JUnit testing class, (2) writing assertions for preconditions, (3) writing good method specifications and class invariants and using good conventions in presenting programs, and (4) writing and checking javadoc specifications.

File a1.pdf is the handout for the assignment. The CMS tells you when A1 is due. Get started early.
Gries's PhD genealogy (pdf file)

Assignment A2. Functions

The purpose of A2 is to give you practice writing java functions, mainly dealing with Strings. We found out in earlier semesters of this course that many students did not practice unless forced to, so we have to give this assignment. File contains lots of instructions as well as the specifications and stubs for the functions you have to write. We give you a JUnit testing class; pass all the tests in it and you should get 100/100, unless something is disasterously wrong; we can't think of anything like that at the moment..  a2handout.pdf

Assignment A3. Linked lists

Assignment A3 introduces you to "linked list", a data structure that allows a list to grow to any size and in which operations like insertion and removal of a value can take place in constant time. You will implement a doubly linked list. A3 handout

Assignment A4. Bug propagation

Assignment A4 requires you to write 8 methods to process trees in an interesting application.

Assignment A5. Five in a row

Assignment A5 requires you to build a GUI and AI for a simple game.
handout    release code    javadoc

Assignment A6. Heaps

Assignment requires you to implement a min-heap. in which duplicate values are not allowed and the the priority of an existing value may be changed.
a6handout.pdf   Due date? See the CMS.

Assignment A7. Shortest Paths

Implement Dijkstra's shortest path al Dijkstra's shortest path algorithm.
a7handout.pdf Due date? See the CMS.

Assignment A8.

Temple of Boom. Help Indiana Morrisett find the Orb, pick it up, and scram ---get out of their in time--- while picking up as much gold as possible. A8handout.pdf   Due date? See the CMS.

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 10 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.