1. Lecture 1: Overview of CSCI 485 Shahram Ghandeharizadeh Associate Professor Computer Science Department University of Southern California Presented by: Shahin Shayandeh

2. Logistics Required text book: Required text book:  Database System Concepts, Silberschatz, Korth & Sudarshan, 5 th Edition. Available in the bookstore.  Please start to read Chapter 6 and Section 7.1 for the next lecture Pre-req for the course: Pre-req for the course:  CS201: Data Structures  Knowledge of an object-oriented programming language such as C++, Java, C#

3. Instructor Details Dr. Shahram Ghandeharizadeh Office: SAL 208 E-mail: shahram@usc.edu Phone: 213-740-4781 Office Hours: Tuesdays and Thursdays: 11am to 12 pm Class URL: http://dblab.usc.edu/csci485

4. TA Shahin Shayandeh Office: PHE 328 E-mail: shayande@usc.edu Office Hours: Tuesdays and Thursdays: 2:00 to 3:30 pm

5. Outline Motivation for DBMS Motivation for DBMS An outline for the course material An outline for the course material Grading: Assignments and projects Grading: Assignments and projects

6. Database Management Systems (DBMS) Used almost on a daily basis for either individual or business use. Used almost on a daily basis for either individual or business use. Relational database vendors were one of the fastest growing sectors during the.COM boom! Relational database vendors were one of the fastest growing sectors during the.COM boom!

7. DATABASE & DBMS Database: An integrated collection of data, usually stored on secondary storage, typically describing the activities of one or more related organizations. Database: An integrated collection of data, usually stored on secondary storage, typically describing the activities of one or more related organizations. Database management system (DBMS): A collection of software/programs designed to assist in maintaining and utilizing large collections of data. Database management system (DBMS): A collection of software/programs designed to assist in maintaining and utilizing large collections of data.

8. BEFORE DBMS Data User 1 User 2 Application programs

9. Data managed by DBMS AFTER DBMS User 1 User 2 DBMS Application programs

10. WHY A DBMS? 1. Reduced application development time 2. Data independence: Application programs not dependent on data representation and storage details 3. Data sharing: data is better utilized (discovered and reused), redundancy of data is minimized 4. Data integrity and consistency: one may enforce consistency constraints on data, e.g., number of seats sold ≤ number of seats on the plane × 1.1 5. Centralized control: DBA tunes the database to balance user's needs 6. Security: mechanisms to prevent unauthorized access. These mechanisms are based on content instead of file-oriented approach. 7. Concurrency control: avoids undesirable race conditions that arise with simultaneous access/updates to data 8. Crash recovery: ensures the integrity of data in the presence of failures

11. DBMS ARCHITECTURE User 1 User n … Conceptual schema Physical data DB DBMS

12. Data Models Conceptual Logical Physical

13. Data Models (Example) Build a database to keep the medical records of U.S. residents

14. Data Models Conceptual Logical Physical

15. Challenges Conceptual Logical Physical Abstraction, Inheritance, Encapsulation Reduction to tables with minimal: data duplication, potential for data loss and update anomalies Effective use of a DBMS, Index structures, CC & Crash recovery, Optimization techniques

16. Challenges Conceptual Logical Physical E-R data model Relational Data model, SQL, Relational Algebra Different kinds of storage, A DBMS architecture, Index structures, CC & Crash recovery, Optimization techniques, Techniques to build a DBMS 5 Normal Forms

17. Relational DBMS Why? Why?  Performance!  Reduced application development time  Use of SQL makes access to data more uniform:  Software modularity,  Extensibility

18. Grading Midterm 1: 35% Midterm 1: 35% Midterm 2: 35% Midterm 2: 35% Assignments: 10% Assignments: 10% Project: 20% Project: 20%