M-W 11:50-1:20pm Loop, 
Instructor: Gary F. Andrus
Office: 474 CTI (Loop), Phone: (312) 362-8719
E-mail: gandrus@cti.depaul.edu
Web: http://condor.depaul.edu/~gandrus
Office Hours
CTI Lab equipment problems: 312-362-8404

1. Course Description

Information derived from databases is central to the effective operation of any organization. This course will introduce students with the understanding of the methods for the design, development, implementation and administration of desktop databases. Concepts we will cover include:

Design a database: Entity Relation (ER) modeling and normalization techniques
Create and maintain a database using Microsoft Access.
Compose and use queries in Structured Query Language
Create and customize forms and reports
Integrate databases with other sources of data and applications

Prerequisites:   Computer literacy

2. Textbook

    Concepts of Database Management, 6^th Edition,
    Pratt & Adamski.
    Cengage, 2008.
    ISBN 13:978-1-4239-0147-1.

3. Coursework

1. Readings. Readings will be assigned from the text and handouts. 
2. Homework Assignments. Six to ten homeworks will be assigned.
3. Midterm and Final Project.

4. Grading

The grade breakdown will be as follows:

• Homework 40%
• Midterm  25%
• Final project 35%

Grading Scale

5. Approximate Weekly Schedule

6. Email

Email is the primary means of communication between faculty and students enrolled in this course outside of class time. Students should be sure their email listed under "demographic information" at http://campusconnect.depaul.edu/ is correct.

7. Academic Integrity

Each student in this course is expected to abide by the DePaul University Code of Academic Integrity. Any work submitted by a student in this course for academic credit will be the student's own work.

You are encouraged to study together and to discuss information and concepts covered in lecture and the textbook with other students. You can give "consulting" help to or receive "consulting" help from such students. However, this permissible cooperation should never involve one student having possession of a copy of all or part of work done by someone else, in the form of an e-mail, an e-mail attachment file, a diskette, flash drive, or a hard copy.  Unless an assignment is designated as a group project, one student should never submit a copy (or near copy) of another student's work.

Should copying occur, both the student who copied work from another student and the student who gave material to be copied will both automatically receive a zero for the assignment. Penalty for violation of this Code can also be extended to include failure of the course and University disciplinary action.

If you have any questions or doubts about what plagiarism entails or how to properly acknowledge source materials be sure to consult with your instructor.

8. Incompletes

The following paragraphs summarize university and school policy on incompletes: An incomplete is given only for an exceptional reason for not completing the course (e.g., death in the family, serious illness). Any such reason must be fully documented before an incomplete can be given. Any incomplete request must be approved by the Dean of Computer Science. In particular, an incomplete is not given for any of the following reasons:

The company won't pay for the course if I get _____.

My grade point average will suffer if I get _____.

It's past the drop date and I'll have to pay for the course if I withdraw now.

In the unlikely case that an incomplete is given, it must be made up with the original instructor of the class. It is not possible to "sit in" on another faculty member's course and have that person give the grade to turn in. As a result of university and school rules concerning incompletes, incompletes in the School of Computer Science are rarely given.