People:

Instructors:
Viera K. Proulx

Bryan Chadwick

Teaching Assistants: Matthew Ekstrand-Abueg, J. Ian Johnson, Pavel A. Metrikov

Tutors: Corey Hanson, Michael Polep, Griffin Schneider, Jason Shrand, Cassandra Thomas, Jacob Wood

Everyone on the course staff is available for consultations to every student.

Class:

Course lecture times and location:

MoWTh 9:15 am - 10:20 am	in room 108 WVH	Viera K. Proulx
MoWTh 1:35 pm - 2:40 pm	in room 108 WVH	Bryan Chadwick

You must attend lectures on a regular basis.

Lectures are really just interactive group learning sessions. You must bring paper and a pencil or a pen, so you can work out the questions posed during the lecture. If you use a laptop to take notes during the lectures, you must be able to answer questions and participate in the class discussion at any time.

Labs: The lab CS 2511 is an integral part of the course. The labs start on Tuesday, January 11th and meet in 212 WVH. You must attend all labs. The purpose of labs is to give you some hands-on experience with the actual tools, and to illustrate some of the principles from the lectures with hands-on examples. You must finish all the lab work - at home, if you do not have enough time during the lab hours. This work should be included in your electronic portfolio.

Computing Environment: The first assignment uses DrRacket Intermediate Student with lambda language.

Introductory assignments will use FunJava language within the Eclipse IDE. Details will be given during the second lab.

During the remainder of the semester we will use Eclipse IDE with the standard Java language. Optionally, you may choose to use another IDE (e.g. NetBeans) or work directly from the command line.

Assignments: There will be a problem set each week, comprised of two parts: etudes (or practice problems, or portfolio problems), and pair programming assignments.

The etudes will be a series of practice problems that every students must be able to solve. You will work on these problems on your own, and keep the solutions in an electronic portfolio. You may ask the instructor to have an informal portfolio review at any time during the semester - to make sure you are doing well, your code is well organized, and readable. However, there will be a formal review of the portfolio once during the semester.

Use the sample code from the labs, lecture notes, and assignments as a guide for the code organization. Remember: someone else should be able to read your code as a well-written book.

In the assignments you will apply the concepts and techniques to a new situation. They will be done with a partner and will be graded on a weekly basis.

The assignments will consist of a well-structured specific programming projects that may be based on the work done in the previous week(s), or they may be open-ended creative projects where you can practice your design skills.

There will be one final project at the end of the semester. You will present this project during the final week of classes to your instructors and your peers.

Due Dates: Tuesdays at 10:00 pm, unless otherwise specified.

We will not accept late homework.

Getting Credit for Assignments: There will be a short quizzes during some lectures or labs. They will not be announced beforehand. The goal of the quiz is to determine that you understand the basic concepts covered so far, and to assure that you are keeping up with the textbook reading.

If you fail a quiz, you must see the TA or the instructors as soon as possible to go over the quiz and review the concepts you may not understand. You will not get credit for the current homework or any subsequent homeworks until you see the TA or the instructor.

Pair Programming: You must work on your homework problems in pairs. You will be assigned a homework partner during the first lab. Homework pairs will change after the fourth and after the eighth week of the semester.

Keep a log documenting the times you and your partner met and worked together and when do you plan to meet next. If the planned meeting does not happen, write down an explanation. If you are having difficulties working with your partner, see your TA or the instructor and bring your log to document the problems you may have.

Pair programming means that you and your partner study the problem sets individually and possibly even sketch out solutions. Then you meet and jointly develop solutions to each problem. One of you--the driver--types, and the other one--the co-pilot--looks over the driver's shoulder. When something isn't clear, it is the co-driver's responsibility to question the approach. You must switch roles during such a problem solving session.

Every partner must be able to solve every homework problem in the end.

Warning: You must be able to solve every homework problem on your own.

Are you sure you have read the warning?

You are free to collaborate at will with others on the problem sets. If you do so, you must acknowledge all collaborators on your cover page. Failure to do so may result in reductions of your homework grade.

If you are having difficulties working with your partner, please inform your TA or the instructor. Bring in your log of meetings with your partner to help explain the problems you may have.

Portfolio: You should keep a neat record of all your work in the form of an electronic portfolio. It should be organized as follows:

1. Cover web page with your name, course name, and links to the directories listed below.
2. an electronic journal that records your reading, work done on problem sets, and the meetings with your partner
3. a directory/folder for the etudes with a web page listing the contents
4. a directory/folder for the graded problem sets (including the creative projects) with a web page listing the contents
5. a directory/folder for the lab projects with a web page listing the contents
6. optionally, a directory/folder in which you keep copies of any other programs you have written while studying for the course.

You are required to finish every lab, even if you did not have the time to finish it during the lab time.

We will review your portfolios once during the semester. The review will be during the last two weeks in February, or in the early March..

Exams: We will have three exams to assess your progress. The first exam will be given during the lectures on February 10th. The second exam will be given during the lectures on March 10th. The third exam will be scheduled for three hours on Monday, April 11th, 6-9pm. The room for the third exam is TBA.

The exams will test material similar to that assigned in weekly homeworks. You will take the exams by yourself. Collaboration is not tolerated. If you make sure that you can do every the homework problem on your own, the exams will be easy. If not, you will probably have a difficult time with the exams.

Grades: You will get a grade for your homework and a grade for your exams. Both must be passing grades; otherwise you cannot pass the course. For the final grade, we will assign a weight of 35% to the homework grade, a weight of 55% to the three exams (10%, 15%, 30%), and 5% for the portfolio review, final project (including the presentation), and class participation. The remaining 5% are up to the instructors' whim.