This page is a course resource for David Hutchens's section of CSCI 162 in Fall 2008.
Beth Katz has an excellent description of how to approach learning in this course. Read it. Do it.
Even if you breezed through CS 161, CS 162 will be more challenging. Plan to spend more time on it.
Note that I expect you to use functions extensively and have good coding style. I don't expect piles of comments, but I want each and every function to have a useful description of its purpose. We'll use the Javadoc format for documentation. Programs at this level are read as much as they are executed. You need to be able to read and understand the code you write. Create it that way rather than making it readable as an afterthought. Eclipse uses the Javadoc comments you write to give you hints about that code; take advantage of that by writing good comments as you create the code.
A good, though rather detailed, article on intellectual property can be found at Franklin Pierce Law Center: Intellectual Property: Practical and Legal Fundamentals.
Examples are in /home/grader/hutchens162/examples on CS. I will update this as we create more examples.
Much of the materials and most of the assignments that I'll be using in this course were developed by Beth Katz