SYLLABUS
College of Computing and Software Engineering
Department of Computer Science
CS 6070: Databases
Spring 2025
Course Information
Class meeting times: Tuesdays (virtual, asynchronous) and Thursdays, 18:30-19:45
Modality: Hybrid; Location: Engineering Technology Center Room 310
Syllabus and detailed schedule is posted on course web site: https://drcs.codes/databases/ksu/cs6070/schedule.html.
Instructor Information
Name: Christopher Simpkins
Email: christoper.simpkins@kennesaw.edu
Office Location: Norton Hall Room 330
Office phone: N/A
Office Hours: Thursdays, 15:30-17:30 in R2-330 (during January in Room J123)
Preferred method of communication: E-mail
Course Description
This course provides in-depth coverage of database management systems, database processing, data modeling, database design, development, and implementation. Particular emphasis is placed on the relational approach to database management and processing. This course includes implementation of current DBMS tools and SQL. Ethical and security topics related to databases will be discussed.
Prerequisites:
- CS 5000 Foundations of Programming
Credit Hours: 3-0-3
Course Materials
Required Texts:
- FoDS: Fundamentals of Database Systems by Elmasri and Navathe, 7th Ed, https://www.pearson.com/en-us/subject-catalog/p/fundamentals-of-database-systems/P200000003546/9780137502523
Course Learning Outcomes
At the end of the course, students should be able to:
- explain fundamental concepts such as data independence, three-level database architecture, and database system components
- create a conceptual entity-relationship model from a list of database system requirements
- model data using the relational data model
- manipulate relational data using relational algebra
- map conceptual ER schemas to relational schemas
- design databases using functional dependencies and normal forms
- implement a databases design using the data definition language in Structured Query Language (SQL)
- populate a database, manipulate data in the database, and query the database using SQL
- use a professional relational database management system such as MySQL
Course Requirements and Assignments
- 3 Project Deliverables
- Midterm Exam
- Final Exam
Evaluation and Grading Policies
- Project: 60%
- Exams: 40%
Each assignment will be graded on a 100 point scale which you may consider a percentage with respect to the grading scale below. Some assignments may have more than 100 points, in which case the points in excess of 100 are "extra credit."
In general, every attempt will be made to provide grades and feedback within two weeks of the submission deadline of an assignment. All grades to date will be posted before midterm so that students may make informed decisions about course withdrawals, and before finals week so that students may budget their final exam study time appropriately.
GRADING SCALE:
- 90: A
- 80: B
- 70: C
- 60: D
- 60: F
Midterm Grades: A midterm grade will be assigned by the midterm grade due date identified on the academic calendar. This midterm grade is for assessing mid-semester performance at least one week prior to the last day to withdraw without academic penalty. You may view your midterm grade in Owl Express. Note that only your final grade will be officially recorded on your academic transcript.
Course Policies
Assignment Submission and Make-up Policies
Assignments are due at 23:59 local time on the due date. Late submissions are not accepted except in exceptional, documented cases beyond the student's control such as illness, death in the family, or natural disasters.
In the case of missed exams, make-ups will be given accoring to the same policy regarding exceptional cases for assignments.
Academic Honesty
Academic dishonesty cannot be tolerated. You may discuss any of the assignments with your classmates (or anyone else) but all work for all assignments must be entirely your own. Any sharing or copying of assignments will be considered cheating. By the rules of the College of Computing and Sofwate Engineering (CCSE), the instructor is obligated to report any incidents of cheating to the department. The first incident of cheating will result in the student getting a final grade of F for the course. The second incident, by CCSE rules, will result in a semester suspension from the College.
Attendance Policy
Class attendance is required and very important for successful completion of the course. Students are expected to attend every class and participate in the discussion of ideas developed by others in the class. Peer feedback is essential and is part of the grade assigned to each of the course assignments stated above. Excused absences must be planned for, when possible, and justified with documentation. The student is responsible for making up missed class sessions. Late arrival that causes disruption, early departure that causes disruption, excessive conversation among students (a disruption in its own right), inappropriate use of electronic devices that cause disruptions and other actions that disrupt the classroom are unacceptable.
Email Policy
Students must use their official KSU email address and put the course number, CS 6070, in the subject line of the email when sending email pertaining to the course.
Classroom Behavior
All students are reminded to conduct themselves in accordance with the Student Code of Conduct, as published in the University Catalog. Every KSU student is responsible for upholding the provision. Students who are in violation of KSU policy will be asked to leave the classroom and may be subject to disciplinary action by the University.
Instructional Continuity Plan
Kennesaw State University (KSU) may decide to close campuses, operate on a delayed schedule, or transition to remote instruction for inclement weather or in case of emergency.
The University will announce campus closures, delayed schedules, or remote instruction through KSU Alerts sent to your cell number on file and to your university email account. In addition, announcements will be posted on KSU’s home page: www.kennesaw.edu.
Our class continuity plan includes:
- Communication: Please check D2l Brightspace or e-mail for necessary instructions.
- Virtual Classes: If in-person classes are not possible, we may transition to virtual classes using MS Teams.
- Assignments and Assessments: Deadlines for assignments and assessments may be adjusted to accommodate the emergency situation.
We understand that emergencies create unique challenges. If you need additional support during an emergency, reach out via Brightspace or e-mail. The university also offers resources such as counseling and academic support, which can be accessed remotely.
Policy on the Usage of Artificial Intelligence
AI Use Allowed, but Not Required:
In this class, you are welcome to use AI for any purpose. However, you should note that all AI generative tools still tend to make up incorrect facts and fake citations, code generation models tend to produce inaccurate outputs, and image/art generation tools can produce copied work or offensive products. You will be responsible for any inaccurate, biased, offensive, or otherwise unethical content you submit regardless of whether it originally comes from you or an AI tool. If you use an AI tool, its contribution must be credited in your submission. The use of an AI tool without acknowledgement is cheating and constitutes a violation of the KSU Code of Academic Integrity.
Department or College Policies
Students are expected to be aware that the Computer Science department has certain policies in place that govern practices within the department including:
- "B" or better grade is required for CS 1321/L and CSE 1322/L and their equivalent transfers. All courses used toward any undergraduate degree in the computer science must be completed with an assessed performance grade of "C" or better. This means that all prerequisite courses from the CS Department must have been completed with a "C" or better in order for a student to enter the next course in a sequence.
- All requests for course overloads must be made through the College advising office and with the approval of the Program coordinator and department chair. The instructor of any course is not permitted to authorize course overloads.
- All requests for prerequisite bypasses must be made through the College advising office and with the approval of the Program coordinator and department chair. The instructor of any course is not permitted to authorize course overwrites.
- All students are encouraged to register their current choice of major using the department major change process. Students who are not recorded under their intended major may find that they may be limited from registering for courses they require to complete their intended program of study.
Institutional Syllabus Policies, Procedures, and Resources
Federal, BOR, & KSU Required Syllabus Policies and Student Resources: https://www.kennesaw.edu/curriculum-instruction-assessment/academic-program-planning-development/resources/student-syllabus-resources.php
Course Schedule
Detailed course schedule: https://drcs.codes/databases/ksu/cs6070/schedule.html.
Weekly Summary:
Week | Content Covered | Assignments | Exams |
---|---|---|---|
Week 1: 01-07,01-09 | Introduction to Databases,Database Concepts | ||
Week 2: 01-14,01-16 | ER Models | ||
Week 3: 01-21,01-23 | EER Models | Assigned: Project | |
Week 4: 01-28,01-30 | Conceptual Design Process | ||
Week 5: 02-04,02-06 | Relational Model | ||
Week 6: 02-11,02-13 | Relational Algebra | Due: Project Phase 1 | |
Week 7: 02-18,02-20 | Midterm Review | Midterm Exam | |
Week 8: 02-25,02-27 | ER - Relational Mapping | ||
Week 9: 03-04,03-06 | Basic Relational Design,DB Workshop | ||
Week 10: 03-11,03-13 | Spring Break - No Class | ||
Week 11: 03-18,03-20 | SQL DDL,SQL CRUD | ||
Week 12: 03-25,03-27 | SQL Queries | Due: Project Phase 2 | |
Week 13: 04-01,04-03 | Advanced SQL | ||
Week 14: 04-08,04-10 | Relational Design | ||
Week 15: 04-15,04-17 | Advanced Relational Design | Due: Project Phase 3 | |
Week 16: 04-22,04-24 | NoSQL Databases,Storage and Indexing |