IST365: Database Systems
Course Syllabus
Fall 2001, TR
Instructor |
: Brian M. Morgan |
Office |
: Prichard
Hall 212 |
Phone Number |
: (304) 696-6469 |
Fax Number |
: (304) 696-6533 |
Office Hours |
: M: 1:00 4:00 W: F: |
E-Mail |
Textbooks:
The following textbook is required for the course:
Database Systems Design, Implementation and Management (4th ed.), by Rob and Coronel; Thomson Learning; ISBN: 0-7600-1090-0, 2000.
Computer
Requirements:
Supplemental materials can be found contained within the WebCT environment (http://webct.marshall.edu/). I will be sending class announcements,
updates, etc. using your WebCT account (will discuss during the first
lecture). Access to a WWW browser is required
(Netscape 4.0 or higher or Internet Explorer 5.0 or higher) and Adobe Acrobat
Reader (available for download through the class WebCT site).
Course
Description:
Covers the logical and physical structures of data stored and retrieved
from a relational database. Exposure to distributed databases, database
administration and structured query language will also be done.
Credit:
The course is three (3) credit hours. It includes classroom
lectures, exams, and homework assignments and projects. Students will
participate in projects that illustrate the implementation of concepts in
general applications.
Pre/co-requisites:
IST263 (Programming Practicum) or permission.
Desired Objectives/Outcomes:
By the end of this course, you should be able to:
-
Identify problems for which database solutions are
suitable
-
Construct conceptual and logical data models based
upon a set of information requirements
-
Translate data model specifications for a relational
database
-
Discuss and show and understanding of the fundamentals
of SQL
-
Discuss the significance of database security and
integrity
-
Implement a database application using Oracle and
Access as a front-end
Instruction method:
There will be 3 contact hours of classroom lecture per week. Projects covering the
major topics are part of the course.
Students may work on their assignments in University computing
facilities.
Evaluation method:
Evaluation of student's performance will be based on the quality of your
performance on projects, exams, and class and web-based participation.
Grading Policy:
Final grades are based on performance in assignments, exams, and attendance as
indicated below.
2 in-class Exams |
30% |
Final Exam |
20% |
Homework Assignments |
15% |
Semester Project |
25% |
Attendance & Participation |
10% |
Assessment
of Projects:
The
grading of all projects will take into account the following:
1.
Although the most important attribute of a program is
correctness, grading will take into consideration efficiency, documentation,
etc.
2.
Although interactions with other students are
encouraged, you must compose your own answers, unless otherwise noted.
Individuals
who utilize other peoples thoughts or ideas must provide appropriate
references to said resources. Failure to
provide such documentation will result in a failing grade for the assignment,
and may result in a failing grade for the course.
In
determining the overall grade for a project, you can expect the following
grades based on performance:
A
Excellent work that meets and/or exceeds all of the requirements for the
project, the project is well-documented and completed efficiently.
B Good
work that meets all of the requirements of the project, but may have errors in documentation
or contains errors in logic.
C
Average work that meets all of the requirements of the assignment, but is
missing one or more of the items in its entirety that is mentioned in terms of
an A grade.
D Below
average work which fails to meet one or more of the requirements of the
assignment.
F
Unacceptable work which fails to meet two or more requirements for the project.
Final letter grades
are determined based on the following grading scale:
90-100% |
A |
80-89% |
B |
70-79% |
C |
60-69% |
D |
Below 60 |
F |
The instructor reserves the right to change these values depending on the overall class performance and/or extenuating circumstances.
Policy Statement:
Assignments and Project: The course includes a number of homework assignments
and a semester-based project. All assignments are due at midnight on their due
date and must be submitted through the WebCT Dropbox. Late assignments will
be penalized at the rate of 10% per day (including weekends).
Exams:
There are three exams: The first will come during Week 6, the second
after Week 11 and a comprehensive Final exam (as scheduled). Exact dates and
times of exams will be announced in class.
Make-up Exams and Late Penalty: Make‑up exams
will not be given except under unusual circumstances and
satisfactory written justification. Any
student who misses an exam due to an unexcused absence will receive a grade of
zero for that exam with no opportunity for make-up or substitution. University excused absences or those
occurring with a good reason will be excused.
Make up exams must be taken within one week of the original scheduled
date. The decision whether to give a
make up exam rests with the instructor.
Attendance Statement:
Class attendance is mandatory and is a required part of the course. Those needing to miss class for a legitimate
reason must contact me via telephone/voice mail or e-mail prior to the class
meeting for it to be excused. See
grading policy.
Withdrawal Policy:
The University withdrawal policy is followed in this course.
The last day to drop an individual course for the Fall of 2001 is October 26,
2001.
University Holidays:
The class is officially dismissed on the following dates:
Fall Break: November
20, 2001
November
22, 2001
Topics and Methodology:
The following outline delineates the tentative class schedule with topics to be
addressed during the course. Please
note this is a tentative schedule and it may change upon class progress:
August 21 |
Overview of Course and Syllabus Introduction to WebCT Overview of Access?? |
August 23 |
Chapter 1 Assign Homework 1 Chapter 1 Problems, #s 1,
2, 3, 4, 5, 15, 22 |
August 28 |
Chapter 2 |
August 30 |
Chapter 2 Introduction to Semester Project Assign Homework 2 Chapter 2 Problems, #s 8,
9, 10, 21, 22, 23, 24, 25 |
September 4 |
Chapter 15 Introduction to Oracle |
September 6 |
Oracle Homework #1 Due |
September 11 |
Oracle Chapter 3 SQL |
September 13 |
Chapter 3 |
September 18 |
Chapter 3 Assign Homework 3 Chapter 3 Problems, #s 1,
5, 11, 12, 18, 19 Homework #2 Due |
September 20 |
Chapter 4 |
September 25 |
Chapter 4 Assign Homework 4 Chapter 4 Problems, #s 4,
5 Review for Exam 1 |
September 27 |
Exam 1 |
October 2 |
Chapter 5 |
October 4 |
Chapter 5 Chapter 6 Assign Homework 5 Chapter 5 Problems, #s 1,
2, 3, 4 Homework #3 Due |
October 9 |
Chapter 6 Project Deliverable #1 Due |
October 11 |
Chapter 7 Homework #4 Due |
October 16 |
Chapter 7 Chapter 8 |
October 18 |
Chapter 8 Homework #5 Due |
October 23 |
Chapter 8 |
October 25 |
Chapter 9 |
October 30 |
Chapter 9 |
November 1 |
Catch Up Review for Exam 2 |
November 6 |
Exam 2 |
November 8 |
Chapter 10 |
November 13 |
Chapter 10 Chapter 11 |
November 15 |
Chapter 11 Project Deliverable #2 Due |
November 27 |
Chapter 12 |
November 29 |
Chapter 13 |
December 4 |
Chapter 13 Project Deliverable #3 Due |
December 6 |
Dead Week Review for Final |
December 11 |
Final Exam 8:00 am 10:00 am |
For each topic
discussed in the textbook, specific experience of other students and the
instructor will be discussed to enhance the characteristics involved. Hands-on projects for the course will be
based on creating real-world databases.
Additional material may also be covered in the class.
Every student is
responsible for all materials presented in class, including lectures, notes,
and handouts. In case you are not
present for a class, it is your responsibility to contact the instructor and
receive information about the material presented in that class. Class attendance is very important.
Effort Required:
As a 300-level course, a considerable amount of work and research effort is
required of the student. For every one
hour in class, the student is expected to put in an effort of at least 3 hours
outside the class for studying and completing assignments and projects. Upon background and preparedness, some
students may have to put in additional effort.
Communication:
The Bulletin Board facility of WebCT and private E-mail will be used to make
any general announcements, last minute changes, etc. It is mandatory that you monitor your WebCT
course messages at least once a day.