Course Overview

Prerequisites The prerequisite for CS230 is CS111, Computer Programming and Problem Solving. If you have not completed successfully CS111, you must obtain permission by the instructor in order to enroll to this course. Students with significant programming experience (including knowledge of Java), also need the permission of the instructor to enroll in CS230.

Computers All programming in CS230 will be done using BlueJ. If you want, you can use your own computer but you will have to maintain the software, and be prepared to use the department's machines if yours has problems. Sorry, the course instructors will not be able to help you trouble-shoot your own computer.

Course Directory The CS230 course directory is located at /home/cs230 on the cs server, tempest. This directory contains material relevant to the class, including course software, and online versions of assignments and programs. Any required material of the course Java software will be placed in the download folder inside the /home/cs230 directory and you can access it using an sftp program (like Fetch on a Mac).

Course Group There is a "Google group" per section, named CS230-F19@wellesley.edu. If you have registered in the course, you have been automatically added to a group and you should have already received an email. This group has several purposes. We will use it to make class announcements, such as corrections to assignments and clarifications of material discussed in class. We encourage you to post questions or comments that are of interest to students in the course. Please do not post significant amounts of Java code (i.e. more than one or two lines of code) in your messages on the group! The instructors and TAs will read messages posted in the group on a regular basis and post answers to questions found there. If you know the answer to a classmate's question, please do post a reply yourself. The course group is also a good place to find people to join a study group. You should plan on reading group messages on a regular basis.

Textbook Regular readings will be assigned from the required text, Java Foundations, by Lewis, DePasquale and Chase, 2nd edition. We will be using the 2nd edition (though if you have access to a newer edition is fine). We recommend you buy your own paper copy because it can be useful for your future reference as well. It is strongly recommended that you read the relevant sections twice a week.

Java Documentation Being able to understand and use the official Java 7 Documentation is a characteristic of every successful programmer. Become familiar with it!

SI Materials The SIs have shared this Google Drive folder of materials with you, so here's a helpful link to make it easier for you to in find it. This folder will include all the handouts they have shared with you in SI.

Class Notes: In the syllabus, each lecture is linked to printable class notes (pdf). If you would like to use them to keep notes feel free to print them before class or just download them on your device.

How to succeed in CS230

Your instructors want you to succeed, and we will do all we can to help you learn the material and become a strong programmer. From your side, here are a few things you can do to succeed in this course.

• Programming is hard: Do not blame yourself for your mistakes; just give yourself more time!
• Programming is a skill: The best programmer has made every mistake in the books!
• Prepare to spend at least 15 hours every week.
• When working on course materials, turn off your social media.
• Attend all lectures, quit all social media while in class.
• Attend all labs, quit all social media while in class.
• Read the book twice a week and complete the weekly Quizes.
• Read the book and slides BEFORE attempting to do the homework.
• Read homework description immediately, start thinking about it ASAP, not 1-2 days before it is due!
• Start homework early, be prepared to make mistakes. That's how you learn a skill!

Course Requirements

Lectures and Labs There are two 75-minute lectures each week that will introduce the main content of the course. Every student is required to attend one 110-minute lab each week. Lab work will include exercises to review and reinforce the lecture material and to develop general programming, testing and debugging skills. The labs will also provide further opportunity to ask questions about course material. See the course catalog about the lecture and lab times of the course. In labs you will be working either with a partner, or individually. In general, be aware that labs contain more tasks than can reasonably be done in the available class time. Solutions to lab exercises will be provided at the end of the day; you are encouraged to study these solutions. At the end of the day of your lab, each student is required to submit whatever lab work they have worked on until then. These submissions will be part of the student's participation grade (see "Grading Policy").

Supplemental Instruction (SI) Supplemental Instruction (SI) is an academic support program offered for selected Wellesley courses. Our academic SI leaders are trained and highly experienced in tutoring CS230. They will offer a study session each week throughout the semester. During SI sessions they will cover problem set solutions and review important concepts. SI sessions are open to all students enrolled in the course. We highly recommend attending the SI session every week, as well as reviewing the handouts used in SI sessions.

Project: During the last few weeks of the semester, project teams of 2 students work on an extended programming project from scratch. Your instructors will provide the general description of the project and you will have to write the specifications and implement it based on the specifications.

Exams: There will be three non-collaborative exams. The first and the second are take-home exams, and the last is a final self-scheduled exam. The take-home exams will require the use of a computer. You are not allowed to collaborate with anyone else on any of the exams, including the take-home exams. The dates of the exams are listed on the schedule. Please mark the exam dates in your calendars as they are not flexible.

Grading Policy

Assignments For assignments, normally a subset of assigned problems will be graded. The full credit of the assignment will be based on the graded subset. After assignments are submitted, sample solutions will be provided for all assigned problems during the SI sessions.

Labs and Quizzes Lab participation and weekly quizzes account for 15% of the total course grade. Participation includes (but is not limited to) attendance, active articipation in class discussions, and completing lab tasks and quizzes.

Final Grades Your final grade for the course will be computed as a weighted average of several components. The relative weight of each component is shown below:

• Lab participation and Quizes: 15%
• Assignments: 25%
• Project: 10%
• Exam 1 (take-home, 2 consecutive hours): 15%
• Exam 2 (take-home, 3 days): 15%
• Final Exam (self-scheduled): 20%
• Total: 100%

Note that each assignment corresponds to about 3% of your final grade, and each lab to about 1% of your final grade. There is no arbitrary limit on the number of A's, B's, C's etc., and every student will be assigned the grade they earn and deserve according to the grading standards of the college.

Assignments in CS230

There will be weekly assignments in which you will write Java programs that emphasize concepts discussed in class. Many of the assignments will be challenging. You are required to work with a partner on the marked task(s) on each of the assignments. Keep in mind that programming often consumes more time than you expect. Start your assignments early! This will give you time to think about the problems and ask questions if you hit an impasse. Assignments are due as indicated on the class schedule.

It is strongly recommended that:

• You start reading the assignment as soon as it becomes available.
• You should not start working on it, however, until you have reviewed the class handouts and have resolved your questions by referring to the relevant chapters in the textbook.
• You re-read carefully the assignment and, using paper and eraser, you sketch the solution.
• Only after you have a reasonable understanding of the assignment and sketched the solution you start coding on the computer.
• Avoid using online technical sites (such as stack overflow, etc) when you try to code. While they may be rarely useful, they are not geared towards novice programmers and it is more likely they will confuse you. All of the answers that you need to work on your assignment are in the handouts, the book and the labs.

In other words, we strongly discourage from writing code as soon as you read the assignment, before you read the relevant material and using pen and pencil to sketch a solution. We also strongly discourage from searching the web for solution related to your assignments: using such code would be a violation of the honor code and is likely to lead you to confusion.

A running program is just the beginning. A program submitted that runs correctly on a particular input earns only 60% of the total grade. Careful testing that covers both the basic functionality and border cases will earn another 20% of the grade, if the testing is demonstrated. The remaining 20% of the grade is earned for good design that implements OOP, documentation that includes top-of-the-file description, method explanation, and in-line explanation as needed. Good programming style is also expected, including following the CS230 style guide.

Late Assignment Policy. For any and all assignments, you could use a 48 hour extension, no questions asked. However, if those two extra days are not sufficient for you to complete the assignment, you are required to contact the instructor and discuss a plan for completing the assignment before the assignment is duw. We will work together to make sure that plan is a reasonable and effective so that it supports both your learning and your health.

If the formal solutions to an assignment are distributed before you turn in a late assignment, you are bound by the Honor Code not to examine these solutions.

Here is overview on our collaboration policy, and it is followed by a more detailed explanation below:

• Assignments: Pairs of students.
• Project: Teams of 2 students
• Exams: Absolutely no collaboration

We believe that collaboration fosters a healthy and enjoyable educational environment. For this reason, we encourage you to talk with other students about the course material and to form study groups.

Programming assignments in this course can be challenging. Also teamwork is the norm in the CS industry. Given the above, some of the assignment work is required to be done with a partner, while some is required to be done individually. In each assignment tasks will be clearly marked as either "individual" or "pair-programming". The two team members must work closely together on the pair-programming tasks, and turn in a single hard copy of work they did together.

Pair-programming tasks are subject to the following ground rules:

• Each team member has to read the assignment problems, think of how to go on solving it, and sketch some solutions, before meeting with their partner.
• While working together, the work must be a true collaboration in which each member of the team will carry her own weight. It is not acceptable for two team members to split the work between them and work independently.
• The fact that team members have to program together means that you need to carefully consider a potential partner's schedule before forming a team. You cannot be an effective team if you cannot find large chunks of time to spend at a computer together!
• Except for the first assignment, when submitting an assignment, you have to decide on your partner for the next assignment.
• Working with different partners is a good way to build community in the class. We strongly recommend that you pair up with several other students during the semester.

In general, teams are allowed to discuss assignment tasks with other teams and exchange ideas about how to solve them. However, there is a thin line between collaboration and plagiarizing the work of others.

Each team or individual student must compose their own solution to each task. Discussing strategies and approaches with classmates and receiving general debugging advice from them is acceptable and encouraged. However you (and your partner) are required to write and debug all of your code. Furthermore, you should never look at another student's code. For example, it is OK to borrow code from the textbook, from materials discussed in class, and from other sources as long as you give proper credit. However, it is unacceptable and constitutes a violation of the Honor Code (1) to write a program together with someone not part of your team and turn in two copies of the same program, (2) to copy code written by your classmates, (3) to read another student's or team's code (4) to view assignments, exams and solutions from previous terms of CS230 or (5) to make any of the assignments, exams and solutions available to others online or off-line. In keeping with the standards of the scientific community, you must give credit where credit is due. If you make use of an idea that was developed by (or jointly with) others, please reference them appropriately in your work. It is unacceptable for students to work together but not to acknowledge each other in their write-ups.

Disability Accommodations

If you have a disability or condition, either long-term or temporary, and need reasonable academic adjustments in this course, please contact Disability Services to get a letter outlining your accommodation needs, and submit that letter to me. You should request accommodations as early as possible in the semester, or before the semester begins, since some situations can require significant time for review and accommodation design. If you need immediate accommodations, please arrange to meet with me as soon as possible. If you are unsure but suspect you may have an undocumented need for accommodations, you are encouraged to contact Disability Services. They can provide assistance including screening and referral for assessments.

Disability Services can be reached at disabilityservices@wellesley.edu, at 781-283-2434, by scheduling an appointment online at their website , or by visiting their offices on the 3rd floor of Clapp Library, rooms 316 and 315.