Table of Contents
Course Objectives
Course Prerequisites
Text
Hints for surviving this course
Students with disabilities
Policy on Academic Dishonesty (Cheating)
Course Attendance/Decorum
Grading
Last Day to Withdraw
Course Schedule
The prerequisites for this course are both M&IS 24060 -- System Analysis I -- and M&IS 24070 -- Principles of System Development. (Or, M&IS 24070.) If you have not taken the prerequisites, you must drop this course.
Hints for Surviving This Course
The following are some suggestions that will help you.
More information on ListServe can be found at HTTP://ACT.KENT.EDU/LISTREQ or at HTTP://WWW.LSOFT.COM/MANUALS/INDEX.HTML
Participation in the ListServe is totally voluntary. If you chose not to be a member, that's fine. All announcements and important messages related to the course will be distributed through the announcement portion of the course home page that is accessible from the World Wide Web.
One note: It is inappropriate to post specific code solutions to homework problems on the ListServe. Anyone doing so will lose his/her ListServe privileges. And, if the posting is particularly egregious, the individual may risk severely and negatively impacting his/her grade. The ListServe is provided to help you learn to solve problems. It is not meant to provide solutions.
In accordance with University policy, if you have a disability and require accommodations to obtain equal access in this course, please contact me at the beginning of the semester or when given an assignment for which an accommodation is required. Students with disabilities must verify their eligibility through the Office of Student Disability Services (SDS) in the Michael Schwartz Student Services Center (672-3391).
It is expected that all work you submit for a grade will be your own. If this is not the case, a failing grade will be assigned for this course and the instructor reserves the right to pursue additional sanctions as provided by University rules and regulations. If you are not familiar with these rules and regulations, you can find them in the current University Phone Directory.
In particular, each of you must submit your own assignments. Should two or more of you submit identical or substantially identical assignments, then I can only assume that one (or more) of you copied from the other(s). In such a circumstance, every student involved will receive a failing grade for the course. Additional sanctions may be pursued in accord with University rules and regulations.
You need to realize that the only way in which you can learn to program is to write programs of increasing complexity. If you submit someone else's work, you are cheating yourself and all other students. I will not tolerate this. Several students have found, in the past, that I am serious about punishing cheating with failure. Don't cheat yourself. I'm available quite a bit and willing to help you when you ask. There are numerous other resources you can call on. It's better not to submit a homework than to submit someone else's.
Class attendance is not required. However, it is strongly encouraged. And, you are responsible for all material covered in class.
A note on class decorum:
I interpret your coming to class as an expression of your interest in learning as much as you possibly can. Certainly, you should assume that this is your classmates' intention in being here. In fairness to your classmates (and me), I expect you to refrain from talking to others, reading newspapers, sleeping, playing radios or CDs, making telephone calls and other similar, possibly disruptive activities. Don't be surprised if I ask you or someone else to leave because of conduct detrimental to the class. If you simply must study for a test later that day, stay home, go to the Library, find a bench outdoors. Don't plan on doing it in class.
Your final grade in this course will be based on your performance in several areas These are shown in the following table
|
Item |
Total Points |
|
Exams |
300 Points |
|
Quizzes |
50 Points |
|
Homeworks |
150 Points |
|
Total Points Possible |
500 Points |
:
A letter grade of A will be earned if you have a total score of 450 points or more. A B will be earned for a total score that is at between 400 and 449 points. For a C, you must have between 350 and 399 points. A D will be assigned with at least 300 and at most 349 points. An F will be assigned to all students receiving a total score that is less than 300 points.
As the semester progresses, I will be posting homework scores on the WEB. You will be able to see them by clicking on the Grades link on the course home page. The last four digits of your social security number will be used to identify you.
The last day to withdraw from this course is Saturday November 2, 2002. Please keep this date in mind.
The following is a tentative course schedule that is subject to modification during the semester. All schedule modifications will be announced in the announcements area of the course web page
|
Week of |
Subject Material
|
Reading |
|
August 27 |
Course Overview |
Chapter 1 |
|
September 3 |
Introduction to Database Development |
Chapter 2 |
|
September 10 |
Data Modeling The Entity-Relationship Model |
Chapter 3 |
|
September 17 |
The Relational Model & Normalization |
Chapter 5 |
|
September 24 |
First Midterm Thursday September 26 |
Chapter 6 |
|
October 1 |
Database Design Continued |
Chapter 6 |
|
October 8 |
Relational Algebra |
Chapter 8 |
|
October 15 |
SQL Continued |
Chapter 9 |
|
October 22 |
Second Midterm Thursday October 24 |
Chapter 10 |
|
October 29 |
Database Application Design Continued |
Chapter 10 |
|
November 5 |
Managing Multi-User Databases |
Chapter 11 |
|
November 12 |
Oracle |
Chapter 12 |
|
November 19 |
Oracle Continued |
Chapter 12 |
|
November 26 |
Multi-Tier Architectures |
Chapter 14 |
|
December 3 |
OBDC, OLE DB and ADO |
Chapter 15 |
|
December 13 |
Final Exam -- Friday December 13, 2002 12:45 - 3:00 p.m. |
|