This class will meet Wednesdays 6:00-8:40 in Moakley 216.
In this class your grade will depend on three components:
Exams: In this class there will be two exams, A midterm and a final. The midterm will be worth 20% of your grade and is tentatively scheduled on Oct 19th. The final will be worth 30% of your grade and will be scheduled by the college.
Labs: There will be several labs in this
course. In these labs you will have the opportunity to practice
database concepts hands-on. We will use a mysql database running on
campus, you will write your programs on eagle, the Computer Science
group's UNIX compute server.
Other: Before exams, and at other times, I will give quizzes to the class. I may also give some homeworks or other assignments. These assignments are not worth a large part of your grade, but do give excellent preparation for parts of the class that are worth alot.
Anyone who has special needs should contact me in the first week of classes so that reasonable accommodations can be agreed on.
See http://www.bridgew.edu/Handbook/PoliciesProcedures/academicmisconduct.cfm 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.
For those projects assigned as group projects, you may discuss and work together with anyone in your group as much as you like. You must still follow the guidelines above when discussing with people outside of your group though.
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.
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.
| Week |
Topic covered |
Addendum |
| Week 1 |
Syllabus and Introduction to
databases /accounts |
|
| Week 2 |
Introduction to relational
databases / mysql |
|
| Week 3 |
SQL |
|
| Week 4 |
Types and relations |
|
| Week 5 |
Theory: Relational algebra |
|
| Week 6 |
Theory: Relational calculus |
|
| Week 7 |
Midterm |
|
| Week 8 |
Integrety |
|
| Week 9 |
Views |
|
| Week 10 |
Dependancies |
|
| Week 11 |
Semantic Modeling | |
| Week 12 |
Transaction: Recovery |
|
| Week 13 |
Concurrency |
|
| Week 14 |
Security |
|
| Week 15 |
Optimization or Decision Support. |