Relational Database Systems CSC 425

Syllabus

OBJECTIVES: To define and illustrate the design and implementations of the various database structures; to examine the logical and physical data structures necessary to support these designs; and to examine the logical abstractions necessary to understand their significance. The student will  use relational algebra, relational calculus and SQL to setup and maintain typical database structures. The student  will use database theory of dependencies and normalization to properly design  and implement typical database applications.

 

 

 

OBJECTIVE/DESCRIPTION

TOPICS

    1. Fundamental concepts of files and databases
    2. The different database models – hierarchical, relational, network
    3. Relational databases
    4. Conceptual data models – Entity-Relationship model, UML model
    5. Normalization
    6. Database system development methodology
    7. SQL language commands and queries, query optimization
    8. Development of Web-based database systems
    9. Transaction management and concurrency control
    10. Distributed database management systems
    11. Text databases
    12. Multimedia databases
    13. Data warehousing concepts
    14. Data mining concepts
    15. Object-oriented databases

 

 

 

 

TEXT:required

Database Systems, A Practical Approach to Design, Implementation, and Management, Thomas M. Connolly and Caroline E. Begg, 4/e Pearson, 2005, ISBN: 0-321-29401-7


Reference texts: not required
Fundamentals of Database Systems. Elmasri and Navathe, Benjamin Cummings, Second Edition, 1994

Database Systems Concepts., Henry F. Korth and Abraham Silberschatz, McGraw Hill , 3/e 1997

EVALUATION: There will be 3 exams including the final. Each exam will count 25% of the final course grade, 10% will come from periodic homework problems/assignments, 15% will come from a database project. The final grade will be based on the above grades as follows:

 A >= 90%
 B >= 80%
 C >= 70%
 D >= 60%
 F < 60%

 CONTENT: Chapters 1 - 13.


Class Attendance:Mandatory. Refer to Mississippi College Policies and Procedures  for details. Since this is a MWF class, you may not miss more than 25%, 12 classes, without penalty of an automatic grade of  F. When a student must miss class for whatever reason, it is his/her responsibility to present a valid excuse to the instructor as soon as possible. All previously assigned work, exams, and quizzes are to be made up within one week. If missed assignments or exams or tests are not made up within the week , then the student will get a grade of  0 on the requirement. Should the student find it impossible to make up the requirements within one week upon returning to normal class attendance, then a mutual agreement with the instructor of the class must be obtained as soon as reasonable regarding times for completion of the  delinquent course requirements. The last day to drop this course is Monday, March 28, 2005 . Courtesy dictates that when a planned absence is known in advance,  the instructor should be apprised as soon as possible and a mutual agreement on make-up work can be set. Failure to do so can result in a grade of 0 on missed work and exams.

 

Last day to drop this course: Monday, March 28,2005


Academic Integrity:(Academic Honesty) While collaborative work outside class is beneficial, even encouraged, the student should be careful to note that using someone else's work is cheating. All problem sets/ programs submitted for grading must be your own intellectual property. Discussion of ideas, concepts, understandings is acceptable. Working together directly or jointly to complete graded assignments , programs or problems, is the same a cheating on an in class exam.

Academic Integrity Policy: online here  This statement on academic honesty in computer science courses is an addendum to the Mississippi College policy 2.19 found at http://www.mc.edu/publications/policies/academic/219.wpd  In a computer science class individual effort is expected.  Student misconduct not only includes cheating on tests, but also extends to copying or collaborating on programming assignments, projects, lab work or research unless otherwise specified by the instructor.  Using other people's accounts to do your work or having others do your work is prohibited. Close proximity in lab does not mean sharing solutions.   NOTE: Discussing logical solutions to problems is acceptable, exchange of code, pseudocode, designs, or procuring solutions from the Web, other texts, the Internet or other resources on or off  campus is not acceptable.      First offense: grade of 0 for all parties involved unless the "guilty" party can be determined
     Second offense: grade of F in the course 

 Graduate Credit: Any student taking CSC 425 for graduate credit (Z) will be expected to read selected papers (4-5) provided by the instructor. The student will be required to answer two to three questions concerning each paper. All answers must be done using word processing software (typed). In addition, each student will do a research paper on a selected topic from database systems. This paper will be from 10 - 15 pages in length, double-spaced and include appropriate references. The research should be restricted to scholarly journals, papers, and books on current trends in database systems.

The following syllabus is designed for a course where the goal is to teach students how to use databases to construct applications. Details of database internals are kept to the minimum. _____________________________

The course shall be supplemented by assignments or a project. The project will involve the design and implementation of a practical application using SQL (and other development tools such as graphical user interfaces or forms packages) on a relational database system. Such as Oracle, PostgreSQL, or MySQL. Guidelines for the project can be found here.

SCHEDULE of Topics (Tentative)

Day

Date

Subject

Rreading (Text)

R

1/13

Introduction to databases

Chapter 1

T

1/18

Database models

Chapter 2, Appendix F

R

1/20

Relational database model

Chapter 3

T

1/25

Relational algebra and calculus

Chapter 4

R

1/27

Entity-relationship modeling

Chapter 11,

T

2/1

Conceptual data modeling

Chapter 14

R

2/3

Math Science Tournament

No Class

T

2/8

Normalization

Chapter 13

R

2/10

Logical data modeling

Chapter 15

T

2/15

Physical database design: Example of database design

Chapter16

R

2/17

SQL commands

Chapter 6

T

2/22

SQL queries

Chapter 5

R

2/24

Exam 1

Chapters 1-6,11-16

T

3/1

Web database development

Chapter 28

R

3/3

''

''

T

3/8

''

''

R

3/10

Transaction management

Chapter 19

T

3/15

''

''

R

3/17

Query Optimization Techniques

Chapter 20

T

3/29

Exam 2

Chapters 19,20,28

R

3/31

Distributed databases

Chapter 22

T

4/5

''

''

R

4/7

Object oriented databases

Chapter 25

T

4/12

''

''

R

4/14

Data warehousing

Chapter 30

T

4/19

Data mining

Chapter 32

R

4/21

Database Project Due

''

T

4/26

Spatial Databases

Handout(s)

R

4/28

FINAL EXAM 8:00 AM

 

 

 

 

 

This HTML document is still under construction.
For further information contact:

Dr. Glenn Wiggins

Last updated Jan 9, 2005.