Intermediate ProgrammingDepartment of Mathematics and Computer Science Hobart and William Smith Colleges Spring, 2011. Instructor: David J. Eck. Monday, Wednesday, Friday, 3:00--3:55, Gulick 206B. Lab: Thursday, 11:55 to 1:20, Library Multimedia Lab.
About This Course
CPSC 225 builds on the material covered in CPSC 124. In Introductory Programming, you spent most of your time learning about the basic building blocks of programs, including variables, control structures, classes, and methods. Intermediate Programming builds on this work in several directions. A large part of the course will be devoted to more advanced building blocks such as recursion, linked data structures, and Java's Collection Framework. But in addition to this, you will learn more about designing and coding complex, robust, and efficient programs. You will learn to use files, networking, threads, and a few of the more advanced aspects of GUI programming. And you will be introduced to two professional programming tools, the Eclipse Integrated Development Environment and the CVS version control system.
The textbook for the course will consist of Chapters 8 through 13 from my on-line textbook, Introduction to Programming Using Java, Sixth Edition, which can be found on the web at http://math.hws.edu/javanotes6. This a new edition of the book, which has not yet been officially released, and there might be a few changes made to it as the term progresses. The major change from the Fifth Edition is a new chapter devoted to threads. A PDF version of the book, which you can download for reading on your computer, is available at this address:
Labs and Assignments
Reading the textbook is a major part of the homework for this course. I also suggest going over the notes that you take in class, preferably on the same day as the class. Ideally, you should make a neat copy of your notes, filling in details and making sure that you understand everything. It can also be a good idea to write small test programs, on your own, to test your understanding. Anything that you don't understand should be brought up in class or in my office hours.
This course has a required lab component. The labs will reinforce the material that we are covering in class, but they will also introduce new ideas and techniques from time to time. For example, at some point during the term, one of the labs will introduce you to the debugging facilities that are included in the Eclipse IDE. Another lab will introduce CVS, a system that can keep track of multiple versions of a program so that you can easily recover from unwise changes. CVS also makes it easier for several people to cooperate on a programming project.
Every lab will involve some programming. You should not expect to complete the lab during class; completing the labs is the major component of your homework for the course. In most cases, all the work for a lab will be due before the beginning of the next lab period. In a few cases, the lab will get you started on a longer programming project that will be due several weeks later.
At least one lab will require you to work together with one or two other students in the class on a team programming project. Other labs will require you to work on your own. Unless otherwise specified for a particular assignment, you should not get any help on assignments except from me, from teaching assistants, or, when working on a team project, from your teammates.
In addition to programming assignments, there will be a few short writing or design assignments. Your responses to these assignments can be word-processed or hand-written. Labs and assignments together will count for 38% of your grade for the course.
Final Programming Project
In addition to the weekly labs and assignments, you are required to complete a larger-scale final programming project that will be due at the end of the semester. It will count for 12% of your grade for the course. This final project can be either an individual or a team effort; a team project will, of course, have to be more ambitious than a typical individual project. We will discuss the requirements for the project in more detail later in the course, but part of the assignment is to choose the project that you will work on, so you should start thinking about it now!
There will be two in-class tests, which will be given on Wednesday, February 23 and on Wednesday, April 6.
The final exam for the course will take place at a time scheduled by the Registrar's office. This might have to be on Tuesday, May 10, at 1:30 PM. However, there is also an exam time for our lab period, on Saturday, May 7, at 1:30 PM; we will discuss the possibility of using this alternative time for the exam.
Your numerical grade for the course will be computed as follows:First Test: 15% Second Test: 15% Final Exam: 20% Final Project: 12% Labs and Assignments: 38%
I reserve the right to adjust your grade downwards if you miss more than one or two classes or labs without a good excuse. In my grading scale, an A corresponds to 90--100%, B to 80--89%, C to 65--79%, D to 50--64%, and F to 0--49%. Grades near the endpoints of a range get a plus or minus.
There will be student teaching assistants for computer science available in Lansing 310 from 7:00 to 10:00 PM, Sunday through Thursday.
Office Hours, E-mail, and Web
My office is room 313 in Lansing Hall. My office phone extension is 3398. I am on campus most days, and you are welcome to come in anytime you can find me there. My regular office hours will be:MWF, 10:10--11:05 AM and 1:55--2:50 PM Thursday, 10:30--11:30 AM
Office hours are times when I promise to try my best to be in my office. I do not generally make appointments during my office hours, since they are times when I am available to students on a first-come, first-served basis. When necessary, I am happy to make appointments for meetings outside my scheduled office hours.
My e-mail address is email@example.com. E-mail is good way to communicate with me, since I usually answer messages within a day of the time I receive them.
The Web page for this course is http://math.hws.edu/eck/cs225/index_s11.html. I will post weekly readings and assignments on that page.
Statement from the CTL
Disability Accommodations: If you are a student with a disability for which you may need accommodations, you should self-identify and register for services with the Coordinator of Disability Services at the Center for Teaching and Learning (CTL), and provide documentation of your disability. Disability related accommodations and services generally will not be provided until the registration and documentation process is complete. The guidelines for documenting disabilities can be found at the following website: http://www.hws.edu/disabilities
Please direct questions about this process or Disability Services at HWS to David Silver, Coordinator of Disability Services, at firstname.lastname@example.org or x3351.
Here is a very tentative weekly schedule of readings and topics for the course. Note that we will cover some topics from Chapter 11, 12, and 13 as the need arises for lab projects, so that by the time we get to these chapters officially, some of the material will already have been covered.
Dates Reading Topics to be covered Jan. 19, 21 8.3
Brief overview of Intro Programming
Checked exceptions and try..catch
Assertions and Annotations (briefly)
Jan. 24, 26, 28 8.5
Analysis of Algorithms
Jan. 31; Feb. 2, 4 9.1 (finish)
QuickSort and other recursive algorithms
Linked data structures
Feb. 7, 9, 11 9.2 (finish)
Operations on linked lists
Abstract Data Structures (ADTs)
Stacks and queues
Feb. 14, 16, 18 9.3 (finish)
Stacks and postfix expressions
Binary treesBinary sort trees (BSTs)
Feb. 21, 23, 25 9.4 (finish)
Recursive descent parsing (?)
TEST on Wednesday, February 23
Feb 28; Mar. 2, 4 10.1
Generic programming and parameterized types
Iterators and for-each loops
ArrayList and LinkedList
Mar. 7, 9, 11 10.2 (finish)
TreeSet and HashSet
TreeMap and HashMap
SPRING BREAK Mar. 21, 23, 25 10.4
Java Collection Framework examples
Writing generic classes
Mar. 28, 30; Apr. 1 11.1
Streams, Readers, and Writers
Apr. 4, 6, 8 11.3
File programming examples
Introduction to Networking
The Client/Server Model
TEST on Wednesday, April 6
Apr. 11, 13, 15 12.1
Creating and using threads
Race conditions and synchronization
Apr. 18, 20, 22 12.3 (finish)
wait() and notify()
Network programming with threads
Images and resources
Apr. 25, 27, 29 13.2 -- 13.4 Advanced GUI Programming (selections) May 2 END OF TERM Wrap-up and Review