Spring 2020 CS230
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:
Lecture: Java constructs, conditionals, iteration
Reading: LDC Ch 3 & 4. (Optional: 3.6 Formatting Output; 3.7 Enumerated Types.)
Ch 1, Ch 2 Quiz due
Lecture: Arrays of Objects and 2D arrays!
Reading: LDC Ch 7 & 8
Ch 5 Quiz due
Ch 7 Quiz due
Presidents' Day - No Classes
MONDAY Schedule,no lab
Ch 8 Quiz due
Deadline to DROP a spring course at 11 PM
Take-Home Exam 1 OUT
Take-Home Exam 1 DUE at 5pm
Lecture: Queues (continued)
Reading: LDC Ch 15.1 - 15.5
Lecture: Analysis of Algorithms
Reading: LDC Ch 12
Ch 14 Quiz due
Preparation for Project
Take-home Exam 2 out
Lecture: Depth-First Search
Take-home Exam 2 due at 5:00PM
Prerequisites The prerequisite for CS230 is CS111, Computer Programming and Problem Solving.
Computers All programming in CS230 will be done using the BlueJ Java Development Environment. 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, we 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. 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 ftp program (like Fetch on a Mac).
Course Group Please add yourself to the CS230 google group. 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, feel free to 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 (not the newer, 3rd edition). It is on reserve in the Science Library. It is required that you read the relevant sections prior to class and complete the reading quizzes (linked on the schedule) by the time listed on the schedule.
Java Documentation Being able to understand and use the official Java Documentation is a characteristic of every successful programmer. Become familiar with it!
SI Materials Your SI has 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.
Lectures and Labs There are two 75-minute lectures each week that will introduce the main content of the course. Every student is also 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.
Lectures are held on Mondays and Thursdays at 11:20-12:35 AM (section 01 in SCI L180 with Prof. Metaxas), at 2:20-3:35PM (section 02 in SCI L180 with Prof. Lerner).
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 leader,Annabel Rothschild , is trained and highly experienced in tutoring CS230. She will offer two study sessions each week throughout the semester. During SI sessions she will cover problem set solutions and review important concepts. SI sessions are open to all students enrolled in the course. We highly recommend attending one of the SI sessions every week, as well as reviewing the handouts used in SI sessions.
Final Project: During the last few weeks of the semester, project teams work on an extended programming project. More details will be released as the semester progresses.
Exams: There will be two in-term, non-collaborative, take-home, self-scheduled exams. There will be a self-scheduled final exam during exam period. On mid-term exams you can use the course handouts and your personal notes only. 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.
Assignments For assignments, 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.
Participation Lecture and lab participation has a weight of 10% of the total course grade. Participation includes attendance, submitting reading quizzes, active articipation in class discussions, and completing lab tasks and questionnaires.
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:
Late Assignment Policy for any and all assignments, you could use a 48 hour extension, no questions asked. To do so, please invite your lecturer and lab instructor to a calendar event which takes place at the new due date, including your name and the assignment you're taking the extension on in the title of the event. 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. 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 solutions to an assignment are distributed before you have turned in, you are bound by the Honor Code not to examine them.
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.
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, the work you turn in should be that of your partnership only. Do not copy or plagiarize 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.