Number and Title of Course: MIS380 – Database Systems and Applications in Business

Instructor: Dr. Wayne Summers
Office: SCA207B

Office phone: (505) 454-3230 Department phone: (505) 454-3295

Office Hours: 9-9:50 A.M. MW; 3:00-3:50 P.M. TR; via e-mail, net-meetings and by appointment

E-mail address: summers_wayne@ColumbusState.edu

homepage: http://csc.ColumbusState.edu/summers

Catalog Description of Course: Database Systems and Applications in Business (3 credits) Understanding and skill in building and manipulating files and databases in a given hardware/software (operating system) environment. The focus is on building databases that are representative of organizational entities (real things and events) so tha users (user processes) can examine them.

Course Prerequisite: MIS233 - Introduction to Information Systems or permission of instructor.

Required Textbook(s):Database Processing, Sixth Edition by David Kroenke; Prentice-Hall Publishing, 1998 (0-13-737842-4).

Supplementary Books and Materials

Educational Outcomes

  1. Students should be able to model user’s requirements
  2. Students should be able to translate user’s requirements into a database design
  3. Students should be able to translate their design into a functional relational database in a variety of different applications

Major Topics

  1. Introduction to Database Processing and Database Development
  2. Data Modeling
    • Entity-Relationship Model
    • Semantic Object Model
  3. Relational Database and Database Application Design
  4. Database Implementation with the Relational Model
  5. Multi-user Database Processing

Instructional Methods and Techniques

  1. The on-campus class will meet for three fifty-minute lecture/discussion/lab periods each week. [Internet students will be expected to meet with the instructor and other students via e-mail and group discussions held weekly].
  2. The lectures should be conducted using state-of-the-art multimedia techniques including a computer projection system.
  3. There will be facilities for demonstrating software and access to computer networks in the classroom.
  4. Notes will be available via the WWW from the instructor’s computer.
  5. The projects will stress hands-on applications by the students. Each student will be expected to attend all sessions. Students and the instructor will share their experiences of designing, coding, and testing their databases. Class participation by all is expected. The emphasis will be on database design and implementation.

Assignments for Course

  1. Readings from the textbook(s)
  2. Outside reading from popular computing and information technology periodicals like PC-Week, PC-Magazine, etc.
  3. Frequent lab assignments

Evaluation

  1. Midterm(s) and Final Exams over the lectures and readings.
  2. Homework including lab assignments on material discussed in class and lab.

Class Attendance: Class attendance is the responsibility of the student, and it is the student's responsibility to independently cover any material s/he may miss. Class attendance and participation may also be used in determining grades. You should attend all lab sessions. Attendance will be taken.

Exams and Assignments: There will be one midterm exam and one comprehensive final exam. Exams cover material from the text as well as laboratory activities. The lectures may not cover all the material in the textbooks. There will be frequent lab assignments. The assignments will be expected to be complete and robust, including good user interfaces. Late assignments will be subject to up to a 25% deduction in points per day. No credit will be given for assignments that are more than one week late.

Course Evaluation (tentative):

Grades may be determined according to this scale:
A 90% - 100% B 80% - 89%
C 70% - 79% D 60% - 69%

Honor Policy: Cheating will not be tolerated. Any student caught cheating will be given a zero on the assignment or exam. Repeat offenders will be given an F for the course and may suffer expulsion from the university. All work must be your own. You may discuss the material in the course and help one another, however, I expect any work you hand in for a grade to be your own. Plagiarism will result in, at best, an "F" for the assignment. A simple way to avoid inadvertent plagiarism is to talk about the assignments, but don’t read each other’s work or write solutions together. Keep scratch paper and old versions of assignments until after the assignment has been graded and returned to you. If you have any questions about this, please see me immediately.

COURSE OUTLINE (tentative)

DATE Chapter / Description Assignment
Week 1: 1 – Introduction to Database Processing
Week 2: 2 – Introduction to Database Development Access
Week 3: 3 – Entity-Relationship Model ER-Diagram/Tourbus
Week 4: 4 – Semantic Object Model Salsa
Week 5: 5 – Relational Model and Normalization
Week 6: 6 – Database Design using E-R Models
Week 7: 7 – Database Design using Semantic Object Model Salsa
Week 8: 8 – Database Application Design
MIDTERM EXAM (March 13)
Salsa
SPRING BREAK
Week 9: 9 – Foundations of Relational Implementation
Week 10: 10 – Structured Query Language
Week 11: 11 – Relational Implementation for Personal Databases Salsa & Access
EASTER BREAK
Week 12: 12 – Introduction to Multi-User Database Processing Database Exercise
Week 13: 16 – Internet, Intranet, and Multimedia Database Processing Salsa
Week 14: 15 – Sharing Enterprise Data Database Exercise
Week 15: 17 – Object-Oriented Database Processing Salsa
Week 16: FINAL EXAM (May 14, 1:30 p.m.)