CS230 Fall 2021
This is a course about data structures and we happen to use java,
an "Object-Oriented" programming language.
Upon completion of this course, students should be able to:
due at 11:59 PM
due at 11:59 PM
Deadline to drop a course
due at 11:59 PM
Indigenous Peoples' Day: no classes
Take-home Exam 1 out
due at 11:59 PM
Take-home Exam 2 outQuiz 10
(Last) Lab 12: Work on your project. Come with your questions!
L23: Binary Search Trees
Reading: LDC Ch 17.1, 17.2, 17.3
Review for the final exam
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 or Cyberduck on a Mac).
Course Group There is a "Google group" per section. 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.
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.
Quizzes: There will be a quiz before each class based on the reading material. Quizzes are due the day before class at 8pm. Once you submit a quiz, you will have access to the correct answers. At that point you may decide to resubmit your quiz. At the end, if you get a grade above 75%, you get credit for that quiz. Otherwise, you do not. At the end of the semester you need to have credit for at least 75% of the quizzes.
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.
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.
Labs Lab and class participation account for 10% of the total course grade. Participation includes (but is not limited to) attendance, active articipation in class discussions, and completing lab tasks.
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:
It is strongly recommended that:
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.
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 copy of work they did together.
Pair-programming tasks are subject to the following ground rules:
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.
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 your instructor. 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 your instructor 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 email@example.com, 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.