. At the end of the course students should be able to:
• understand the fundamental syntax & computer programs
• understand the fundamental control and loop (iteration) structures
• program simple algorithms, such as counting, summing, and finding maximum/minimum
• Implement, test, and debug simple recursive functions and procedures
• understand the basic data structures used in programming (such as arrays and array lists).
• Demonstrate knowledge of OOP concepts: instance variables, methods, objects and classes.
• argue effectively about the merits and possible unintended consequences of a computing implementation
• effectively write or present about the impact of computing on society. Students should extrapolate from historic lessons learned from unintended consequences of computing to the current computer solutions.
exam is scheduled on Thursday Oct 23rd, 2014
The final exam has been scheduled by the University. Don't make any international flight plans before the final.
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.
See http://catalog.bridgew.edu/content.php?catoid=7&navoid=486 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.
For those who find that they are in over their heads:
Computer Science is a hard subject. Most people can master it only with hard work. A few may well find themselves in over their heads without realizing it earlier. Getting an excellent grade in this course (an 'A' or a 'B') will require you to earn it through your performance in the regular course material. For those having exceptional difficulty, I will offer the opportunity to do an extra credit scholarly paper later on in the semester. The paper will be worth up to a 5% increase in your grade, but it cannot raise your grade above a 'C'.
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
|Week 2||Introduction to programming, numbers and computer
|Week 3||using objects and graphics
|Week 4||Sequences, collections and file I/O
|Week 5||Functions and Parameter Passing
|Week 6||selection/decision structures
|Week 7||Repetition and boolean|
|Week 8||review and exam
|Week 9||Using object II
|Week 10||Recursion||Project 6
|Week 11||Computing and Society
|Week 12||Putting it all together to make more interesting
ethical considerations in computer science
|Week 15||Review and slip time