Syllabus for Introduction to Computer Science II

Instructor: Dr. John F. Santore
Phone: 508-531-2226
Office: Conant 333

Instructor Web Page:
Course Web Page:

Office Hours for Fall 2013:
Mon 10am-11:00am
Wed: 5:00-5:50pm
Thurs: 12:30pm-1:30pm
Fri: 10-11am
or by appointment

I will take appointments if you cannot make my other office hours, however, I generally have meetings and work prepared for a day or two ahead so plan on about 48 hours from the time I get your request to us being able to meet.

Course Description:

This is the second semester course in computer science. It will build upon the programming and computer science that you learned in your first semester (comp151). Topics will include recursion, basic data structures, inheritance, polymorphism and other object oriented programming topics along with professional responsibilities and the intellectual property considerations which affect our profession and discipline.

Course Outcomes:

    After taking this course the student should be able to:

  1. Design, implement, and test the implementation of “is-a” relationships among objects using a class hierarchy and inheritance
  2. Design and implement programs that require a) multiple classes and structures b) hierarchies of classes that use inheritance and polymorphism
  3. Develop code that responds to exception conditions raised during execution
  4. Design, code, test, and debug simple event-driven programs that respond to user events
  5. Implement, test, and debug simple recursive functions and procedures
  6. Discuss the consequences of software piracy on software developers and the role of relevant enforcement organizations
  7. Understand the uses and limitations of trademark, copyright and patents for intellectual property protection.


Required:   Starting Out with Java: Early Objects (4th Edition) by Tony Gaddis

Class Requirements and grading:

Programming projects: 50%
Exams: 40%
Everything else (quizzes, participation, homework etc): 10%

Project work:

Since you can't really understand a programming language, or the important computer science concepts without working and practicing with them by writing programs in that language, there will be several programming projects in this class.

There will be a number of projects  in this course. Each lab is to be completed individually. You must get a passing grade in the project portion of the class in order to pass this class. Projects are to be turned in on time. Late projects will be penalized 50% for each day that they are late (i.e if you turn it in the day after it is due, your best possible score is 50%, a second day late will receive 25% credit for a perfect lab. It is therefore almost always best to submit whatever you have on time.


There will be two exams, a midterm and a final exam. The midterm be worth 20% of your final grade. The final will be work 20% of your final grade. Exams will be given on at their assigned times. If you have a legitimate reason for missing an exam, see your instructor before the scheduled exam time to arrange for reasonable accommodation. If you miss the exam without prior approval, you will forfeit the exam. (emergency room visits and the like excepted of course)

The midterm exam is scheduled on  Oct 23 or 24th

The final exam will be scheduled by the college.

Exams are your major in class, completely on your own, evaluation of your progress. You must get a passing grade in the exam portion of the class to pass the class

Note that this means you must get a passing grade in both the exam portion of the class and the project portion of the class to pass the class.

Students with special needs:

Anyone who has special needs should contact me in the first week of classes so that reasonable accommodations can be agreed on.

Academic Integrity:

See  for a complete description of the academic integrity procedure at Bridgewater.

Academic integrity will be taken very seriously in this class. All individual work must be your own. If you cheat or otherwise represent the work of others as your own. You will receive an F for the course.

Guidelines for proper academic integrity:

Discussing problems with your classmates can help you understand the problems and kinds of solutions to those problems that you will learn about in this class. In an effort to make in clear what sort of discussions are appropriate and encouraged in this class and which cross the line to academic dishonesty I use the following guidelines: You may discuss any out of class problem I assign in this class with your classmates or other so long as no one is using any sort of recording implement including, but not limited to, computers, pdas, pens, pencils, phones etc. This lets you talk about theoretical solutions without sharing the actual implementations. As soon as anyone in the group is typing, writing etc, all conversations must stop. You may look at someone else's program code only very briefly in order to spot a simple syntax error. As a rule of thumb, if you find yourself looking at someone else's code for more than about 30-45 seconds it is probably time to stop. If you are having trouble with your program, come to the instructors office hours for more help.

All in class exams and quizzes are closed book and closed neighbor. If you are found using a data storage device of any kind during one of these evaluations, you will be failed for the course.

Standards for in class behavior:

You are all adults and are expected to act as adults in this class. While questions are encouraged in this class, if a particular line of questioning is taking us too far afield, I will ask the student to come by my office hours or to see me after class.

Cell phones, pagers, electronic organizers and other devises should be silenced while in class. If you work of EMS or something similar, please turn your cell phones/ pagers etc to vibrate mode so that you are not disrupting others in the class.

In the unlikely case of trouble makers in the class, those who are simply attempting to disrupt the class will be asked to stop; those who will not, will be referred to the college for appropriate action.

I do not take regular attendance. Because of the census day regulations, I'll have to take occasional attendance. You are adults and are paying for this class. If you miss a class, you are expected to get notes from a classmate and familiarize yourself with the material that was covered before returning to class. I do find from dealing with students in the past that attendance at lecture is highly correlated with doing well in my classes.

Tentative Schedule:

Week Topic Assignment
Week 1 Intro and review

Week 2 review part II

Week 3 inheritance and polymorphism

Week 4 interfaces

Week 5 class hierarchies

Week 6 exceptions
Week 7 o-o design and UML

Week 8 recursion and Midterm

Week 9 recursion II

Week 10 searching and sorting
Week 11 Windowed programming and GUi's
Week 12 event driven programming
Week 13 intellectual property and ethics
Week 14 Algorithm selection

Week 15 review