IST481:  Database Systems
Course Syllabus
Spring 2001, MWF 10:00 am – 10:50 am, PH 207

Instructor

:  Brian M. Morgan

Office

Prichard Hall 212

Phone Number 

:  (304) 696-6469

Fax Number

:  (304) 696-6533

Office Hours

:  M, W, F – 9-10
   M, W – 11-12, 3:15-4:30
   T, R – 3-5
   Other times by appointment

E-Mail

:  brian.morgan@marshall.edu

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 people’s 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 instructors reserve 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 5% per day (including weekends).  

Exams: There are three exams: The first will come after Week 5, the second after Week 10 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 Spring of 2001 is March 16, 2001.  

University Holidays:
The class is officially dismissed on the following dates:
            MLK Jr. Day:            January 15, 2000
            Spring Break:  March 19, 2001
                                           March 21, 2001
            April Break:            April 13, 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:

January 8

Overview of Course with Syllabus
Introduction to WebCT
Overview of Access??

January 10

Chapter 1

January 12

Chapter 1
Assign Homework 1 – Chapter 1 Problems, #’s 1, 2, 3, 4, 5, 16, 20

January 17

Chapter 2

January 19

Chapter 2
Introduction to Semester Project
Assign Homework 2 – Chapter 2 Problems, #’s 1, 4, 5, 7

January 22

Chapter 3 – SQL

January 24

Chapter 3

January 26

Chapter 3
Homework #1 Due

January 29

Oracle SQL
Assign Homework 3 – Chapter 3 Problems, #’s 18, 19, 20, 21, 22, 23 – I will supply you with the database in Access so that you can check your work

January 31

Chapter 4

February 2

Chapter 4

February 5

Chapter 4
Homework #2 Due

February 7

Chapter 4
Review for Exam 1

Assign Homework 4 – Chapter 4 Problems, #’s 1, 2, 3

February 9

Exam 1

February 12

Chapter 5

February 14

Chapter 5
Assign Homework 5 – Chapter 5 Problems, #’s 18, 19, 20
Homework #3 Due

February 16

Chapter 6

February 19

Chapter 6
Project Deliverable 1 Due

February 21

Chapter 6

February 23

Chapter 7
Homework #4 Due

February 26

Chapter 7

February 28

Chapter 8

March 2

Chapter 8

March 5

Chapter 8
Homework #5 Due

March 7

Chapter 15, section 8 - Introduction to Oracle

March 9

Introduction to Oracle

March 12

Introduction to Oracle

March 14

Oracle continued

March 16

Chapter 9

March 26

Chapter 9
Chapter 10

March 28

Chapter 10
Review for Exam 2

March 30

Exam 2

April 2

Chapter 11

April 4

Chapter 11

April 6

Chapter 11
Project Deliverable 2 Due

April 9

Chapter 12

April 11

Chapter 13

April 16

Chapter 13

April 18

Chapter 15

April 20

Chapter 14

April 23

Chapter 14

April 25

Chapter 14
Project Deliverable 3 Due

April 27

Dead Week – Review

April 30

Final Exam – 10:15 am – 12:15 pm

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 400-level course, a considerable amount of development 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 programming.  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.