DBMS

Database Management Systems

Indian Institute of Information Technology, Sri City (IIITS)

Instructor: Dr. Prerana Mukherjee

Monday

Wednesday

Friday

9:00AM - 11:00AM

Monday

2:30PM - 04:30PM

A Database Management System (DBMS) is a software system which is designed to effectively store, organize, update, insert and query bulk of data. With the inception of the idea of relational data models since 1970, the DBMS industry has seen growth of approximately $100 billion a year and incrementally increases by about 25% per year. Due to the advent of emerging internet applications and online portals, they heavily rely upon DBMS design and implementation, thus the database market is expected to grow even faster to ensure data integrity, security and ease of updation.

Disclaimer

The following list of topics is very tentative. Based on available time slots, some topics may be dropped or added or reordered. No. of hours may vary as per the requirement of any particular topic(s).

Unit – I (No of hours: 7) INTRODUCTION

Data base system concepts and its architecture, Data models schema and instances, Data independence and data base language and interface, Data definition languages, DML. Overall data base structure. DATA MODELING USING ER MODEL: ER model concept, notation for ER diagrams mapping constraints, Keys, Concept of super key, candidate key, primary key generalizations, Aggregation, reducing ER diagrams to tables, extended ER model.

Unit – II (No of hours: 7) RELATIONAL DATA MODEL AND LANGUAGE

Relational data model concepts, integrity constraints, Keys domain constraints, referential integrity, assertions, triggers, foreign key relational algebra, relational calculus, domain and tuple calculus, SQL data definition queries and updates in SQL.

Unit – III (No of hours: 7) DATABASE DESIGN

Functional dependencies, normal forms, 1NF, 2NF, 3NF and BCNF, multi-valued dependencies fourth normal forms, join dependencies and fifth normal forms. Inclusion dependencies, loss less join decompositions, normalization using FD, MVD and JDs, alternatives approaches to database design.

Unit – IV (No of hours: 7) STORAGE AND FILE ORGANIZATION

File Organization, Indexing and Hashing Overview of file organization techniques, Indexing and Hashing- Basic concepts, Static Hashing, Dynamic Hashing, Ordered indices, Multi-level indexes, B-Tree index files, B+- Tree index files, Buffer management. Introduction to scalable databases.

Unit – V (No of hours: 7) TRANSACTION PROCESSING CONCEPTS

Transaction processing system, schedule and recoverability, Testing of serializability, Serializability of schedules, conflict & view serializable schedule, recovery from transaction failures, deadlock handling. CONCURRENCY CONTROL TECHNIQUES: Locking Techniques for concurrency control, time stamping protocols for concurrency control.

TEXT BOOKS

Silberschatz, H. Korth & S. Sudarshan, Database System Concepts, TMH, 5th Edition, 2010.

R. Elmasri & S.B. Navathe, Fundamentals of Database Systems, Pearson Education, 6th edition, 2010.

REFERENCES BOOKS

C.J.Date, A.Kannan, S.Swamynathan, “An Introduction to Database Systems”, 8th Edition, Pearson Education, 2006.

J. D. Ullman, “Principles of Database Systems”, 2nd Ed., Galgotia Publications, 1999.

R. Ramakrishnan & J. Gehrke, Database Management Systems, 3rd edition, TMH, 2007.

No prerequisite as such. Knowledge on Operating Systems may be helpful. Programming knowledge on web app development may be helpful in project element.

Course grades will be based on the following weightage pattern. This is purely indicative and necessary modification will be made by the faculty depending on the intensity of the different work assigned for various tasks.

Examinations: 60%

Mid Semester - 1 Exam: 10%

Mid Semester - 2 Exam: 10%

End Semester Exam: 40%

Assignments: 10%

Assignments: 10% (3 planned)

Project Work: 30%

Lecture Slides

Provide a hyperlink to the drive.

Topics Covered

Table having columns: Weekly Lecture Dates, Topics with a slider

Scribe Notes

As instructed in the class we would be going for class scribes by 5 students assigned for every week. The scribes would be selected by the instructor. The idea is to encourage the expression skills, technical writing skills and team work amongst the students. Instructionsfor this are outlined as follows:

(1) Students need to pen down the class notes, their intuitions & analysis, information from various web sources on the requisite topics and very nicely outline the ideas.

(2) You can always put out any specific idea that you want to highlight and take-home messages.

(3) All 5 assigned scribes do that in class independently and share notes amongst them at the end of the day. The resultant class notes would be a compiled version of all the assigned scribes and free of any possible redundancies.

(3) You compile them for all 3 days (M,W,F) in a week and write on the document the scribe names and roll nos. on top, date and day for the talk, list of topics covered in class followed by scribe notes on each topic in detail.

(5) You submit the scribe for each week on weekend to the instructor. Deadline would be announced in class.

Note: Strict vigilance on the sources you refer in the scribe. Give proper references against the image sources plus statistics you provide. For rest, textual material you need to paraphrase entirely and put it in your own words. Table with two columns SEC-A |SEC-B under which Week1...Week N with respective hyperlinks to the scribes (for now keep it # in the placeholder)

Projects

(1) Deliverables

Codebase+ReadMe: to be hosted as Github repository.

Report in IEEE/ ACM double-column format (in .docx/.pdf).

Demo (2-min video showing the workflow of the system)+ Live Working Demo during evaluation

App links, Website links

(2) Regulations in Project Work:

Form a team size of 6 inter-section groups are allowed.

Clearly demarcate the work so that during evaluation marks can be alloted as per the work distribution.

Report and code should be free of any plagiarised content from any web sources. In case you take a particular code snippet or text from any web sources for report writing so give proper credits in the reference section as well as cross-reference it in the report draft.

Report should have following subsections:

(i)Abstract: outlining your problem statement, workflow and key results in brief,

(ii) Problem Statement: clearly out line the problem statement, motivation, key challenges, key highlights/contributions in the work, how do you handle the various challenges?

(iii)Methodology: Put ER diagram, UML Class Diagram, USE CASE Diagram, System Design (Architecture Diagram showing work flow), Set of tools used: Front End and Back End, Explanation of the modules in the system

(iv)Results: Snapshots of the UI, Key tables (if any), Results and Analysis, Discussion, Robustness Testing (some performance numbers if you state of your system vis-à-vis already existing systems), Strengths & Drawbacks (if any)

(v) Conclusion & Future Direction

You can record the screen to show the workflow in your system for video.

Note: Additional scoring points would be there on novelty and innovative packaging of the system. Refrain from using projects done in ASE and same project topics. You can use any software for developing your system's front end (refer to syllabus to see few s/w). Database element is must [Any: MYSQL/ORACLE/MongoDB]. Table with columns Project No. |Project Name| DeliverablesReport, Demo Video, Link to website/App.

Project Code: Git Repo Link

Check the attached snapshot of the same.