CIS 421 Database Management Systems (4 Credit Hours) Prof. Qiang Zhu. (http:/ /www-personal.engin.umd.umich.edu/~qzhu) Office Loc Phone Number: (313) 593-4998, E-Mail: qzhu@umichedu 213 CIS Office Hours: 2:00 - 3:50pm T. & Th,, 9:00 - 10:00pm W., also by appointments Course Meeting Times and Format: 4:00 -5:45pm T. & Th, Lecture Classroom: SSB 1205 Prerequisite: CIS 350 Course Description: This course introduces the fundamental concepts and methods necessary for designing, using, and implementing database systems. Topics covered include: database environment, ER model, relational data model, object-oriented database, object- relational database, database design and methodology, database languages, query processing and optimization, concurrency control, database recovery, and database security Program Goals The program goals of this course are to obtain: An ability to analyze a problem, and identify and define the computing requirements appropriate to its solution, An ability to design, implement and evaluate a computer-based system, process, component, or program to meet desired needs. Course Objectives The objectives of this course are to obtain: An ability to analyze data and functional requirements for an enterprise in the real world, An ability to create an ER diagram for an enterprise (conceptual database design), An ability to design and implement a query processing algorithm (algorithm. design) An ability to design queries for real-world problems (database application design), Anability to design sample relational databases (logical and physical database designs). University Attendance Policy PauA student is expected to attend every class and laboratory for which he or she has registered. Fach instructor may make known to the student his or her policy with respect to absences in the course. It is the student's responsibility to be aware of this policy, The instructor makes the final decision to excuse or not to excuse an absence. An instructor is entitled to give a failing grade (E) for excessive absences or an Unofficial Drop (UF) for a student who stops attending class at some point during the semester. Academic Integrity ‘The University of Michigan-Dearborn values academic honesty and integrity. Each student has a responsibility to understand, accept, and comply with the University’s standards of academic conduct as set forth by the Code of Academic Conduct /http:/ /www.umd.umichedu/policies st-rights/), as well as policies established by each college. Cheating, collusion, misconduct, fabrication, and plagiarism are considered serious offenses, and may be monitored using tools including but not limited to Turnitin, Violations can result in penalties up to and including, expulsion from the University. At the instructor's discretion, the penalty may be a grade of zero on the assignment up to and including recommending that the student be expelled from the University. Itis the sole responsibility of the student to understand and follow academic guidelines regarding plagiarism. The University of Michigan-Dearborn has an online academic integrity tutorial ~—sthat_- «canbe accessed at h mich.edu/aim, Required Materials: Text: Fundamentals of Database Systems, 7th Ed, R. Elmasri and SB. Navathe, Addison-Wesley Langman, Inc., 2016. Reference: Database Systems Concepts, 6th Ed., A. Silberschatz, et al., McGraw-Hill Companies, Inc, 2010. Assignment and Grading Your grade in this course will be determined by your scores on 3 exams (including two term exams and a cumulative final exam) and several assignments/ projects. The 2 term exams will count for 35%, the final exam will count for 30%, the assignments/ projects will count for 35%. Late work will be penalized (5% each working day, weekends count as 5%), as will evidence of cheating in any form. Course Outline (tentative): 1 Introduction (1.1 -1.9, 21-27 in text)— data, database, schema, instance, database system, benefits of database approach, data independence, data models, database languages, database users, DBMS components, database system architectures, DBMS classification Entity-Relationship Model (3.1 -3.7, 5.9 - 3.11, 4.1 -4.5.2,4.7.3-4.74 intext) — database design procedure, entities, relationships, constraints, weak entities, specialization/ generalization, constraints on specialization, hierarchies/attices, categories, aggregation Relational Model (5.1 - 5.4, 9.1 -9.3 in text) — domains, relation schema and instance, integrity constraints, database schema and instance, ER to relation mapping rules |. Relational Database Languages (8.1 - 8.3, 844-88, 6.1 - 6.6, 7.1, 7.3 ~7.5, 10.1 - 10.23, Appendix C in text) — relational algebra, tuple relational calculus, domain relational calculus, SQL, QBE, database programming Relational Database Design (14.1 - 14.5, 15.1 - 15.3 in text) — functional dependencies, Armstrong axioms, relation decompositions, INF, 2NF, 3NF, BCNF, database design principles and algorithms (00 and OR Databases (12.1 - 12.5 in text) — ODMG object model, object database conceptual design, ODL, ODQ, SQL3 for OR database Query Processing and Optimization (18.1, 183 - 18.5, 19.1 - 19.2.1, 19.3.1 - 195 in text) — query processing procedure, query processing algorithms, heuristic-based optimizer, cost-based optimizer . Transaction Management (20.1 - 20.5.3, 21.1 -21.2, 22.1 - 22.3 in text) — transaction concepts, transaction properties, schedule, serializability, 2PL concurrency control, deadlock handling, other concurrency control techniques, failure types, recovery concepts, log-based data recovery techniques Database Security (30.1 in text) — security types, control measures, database security and DBA, access control, disclosure types, relationship between information security and privacy ‘Term exam 1: in class on October 15, 2015 (tentative) Term exam 2: in class on November 24, 2015 (tentative) Final exam: 3:00 - 6:00pm on Thursday, December 17, 2015