1 / 34

ICS 434 Advanced Database Systems

ICS 434 Advanced Database Systems. Dr. Abdallah Al-Sukairi sukairi@kfupm.edu.sa Second Semester 2003 - 2004 (032) King Fahd University of Petroleum & Minerals Information & Computer Science Department. Outline. The Relational Data Model: Version 2 Advanced Data Modeling

sadah
Download Presentation

ICS 434 Advanced Database Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ICS 434Advanced Database Systems Dr. Abdallah Al-Sukairi sukairi@kfupm.edu.sa Second Semester 2003 - 2004 (032) King Fahd University of Petroleum & Minerals Information & Computer Science Department

  2. Outline • The Relational Data Model: Version 2 • Advanced Data Modeling • Databases on the Web • Client-Server Architecture • Client-Server Databases & Tools • The System Catalog • Query Processing and Optimization • Transaction Processing • Concurrency Control • Recovery • Administration & Security • Distributed Databases • Database Replication • Object-Oriented Databases • Data Warehousing and Data Mining • Other Emerging Database Technologies

  3. 2. Advanced Data Modeling

  4. The Entity-Relationship (ER) Model • Introduce by Peter Chen in 1976 • In 1988 ANSI chose ER model as the standard model for IRDS • Elements of the the ER model: • Entities • Relationships • Attributes

  5. Entities • Classes of real-world objects, represented by rectangles

  6. Relationships • Relate two or more entitiesrepresented by diamonds • Degree • recursive • binary • n-ary

  7. ... Relationships • Minimal and Maximal cardinality (min, max) • min-card ( participation ) • optional - 0 • mandatory - 1 • max-card ( cardinality ratio ) • 1 to 1 • 1 to N • N to N

  8. Example

  9. Employee ID Name B_Date Attributes • Properties of entities or relationships • single-valued • multi-valued • simple • composite • domain

  10. ... Attributes • minimal and maximal cardinality • min-card 0 optional 1 mandatory • max-card 1 single-valued N multi-valued • (0, 1) is the default • Keys (identifiers) • simple or composite • internal or external(strong entity) (weak entity)

  11. Problem with ER Model • The Entity Relationship Model in its original form did not support the generalization abstraction • Extended Entity-Relationship (EER) Model

  12. Generalization Hierarchies • Generalization vs. Specialization • Coverage of generalization • total ( t ) or partial ( p ) • disjoint ( d ) or overlapping ( o )

  13. Inheritance • Subset entities inherit all the properties of the generic entity

  14. ER-to-Relational Mapping • Entity Relation • 1:1 Relationship Foreign Key • 1:N Relationship Foreign Key • M:N Relationship Relation • Multi-valued Attribute Relation • Ternary Relationship Relation

  15. Generalization Hierarchy Mapping • Superclass C with attributes {K, a1, .... ,an}m subclasses {S1, S2, .... ,Sm} • Option A • relation L for C • relation Li for each subclass Si with attributes = {k} U {attributes of Si} • works for any constraints • Option B • relation Li for each subclass Si with attributes = {K, a1, .... ,an} U {attributes of Si} • Works only with disjoint and total constraints

  16. ... Generalization Hierarchy Mapping • Option C • a single relation with attributes = {K, a1, .... ,an} U {attributes of S1} U .... U {attributes of Sm} U {t} • (t = type attribute to indicate the subclass, more than one is needed when overlapping) • Preferable if only few specific attributes exist

  17. What is UML? • UML (Unified Modeling Language) • An emerging standard for modeling object-oriented software • Resulted from the convergence of notations from three leading object-oriented methods: • OMT (James Rumbaugh) • OOSE (Ivar Jacobson) • Booch (Grady Booch) • Supported by several CASE tools • Rational ROSE • Together • ...

  18. Structural View Implementation View Class Diagrams Object Diagrams Component Diagrams User View Use Case Diagrams Sequence Diagrams Collaboration Diagrams Statechart Diagrams Activity Diagrams Deployment Diagrams Behavioral View Environment View Different Views in UML

  19. Class Diagrams: Static Structure “A class diagram is a graphic presentation of the static view that shows a collection of declarative (static) model elements, such as classes, types, and their contents and relationships.”

  20. is a set of Class Diagrams: Example 1 Review Specification Name 1 this is a comment 1 1 Review Criteria * 1 Name Review Item 1 1 Grading Criteria 1 1 * * Alternative Subpart Sequence Simple Review Item * 1 is subpart of of 1 1 1 Review Item Iteration Constraint 2..*

  21. Class Diagrams: Multiplicity Constraints • Denote a Set of Non-Negative Integers • Common Forms • 0..1 • 1..1 abbreviated as 1 • 0..* abbreviated as * • 1..* • General Form • i..j, k..l, m..n, … , z..*

  22. is a set of Class Diagrams: Attributes Review Specification Name 1 {A Simple Review Item is neither an Alternative, Subpart, or Sequence} * * Alternative Simple Review Item Review Item 2..* Name Review Criteria Grading Criteria * 1 Sequence * Subpart 1 is subpart of of Sequence of Review Item Iteration Constraint

  23. Class Diagrams: Associations Academic Department 1 {subset} 1 of {ordered} 2..* 1 Faculty Member 1 is married to 1 Person Department Chair # Spouse:Dependant 1 0..4 0..4 Class Section Faculty Member teaches Section of Class during given Semester {A Faculty Member can teach at most 4 sections of any Class during a given Semester} * Semester

  24. term : Semester section: Integer Class Class Diagrams: Associations Qualified Association taught by Faculty Member 0..4 1 Specialization between Associations 1 2..* Faculty Member Academic Department 1 2..* CS Faculty Member CS Department

  25. Class Diagrams: Generalization/Specialization University Person {root} {overlapping, complete} … Faculty Staff Student graduation status {disjoint, incomplete} <<implementation>> Undergraduate Graduate Dog

  26. Database Application System Life Cycle • System Definition • Design • Implementation • Loading or Data Conversion • Application Development or Conversion • Testing and Validation • Operation • Monitoring and Maintenance

  27. The Database Design Process Requirements Collection and Analysis Data driven Process driven Process Requirements Transaction Design Database Requirements Conceptual Design Conceptual Schema (ER Model) Logical Design ( Model Mapping & Normalization ) frequencies performance constraints Set of Normalized relation Physical Design TransactionImplementation DDL Statements

  28. Requirements Collection and Analysis • Identification of user groups and application areas • Review of existing documentation • Analysis of the operating environment and the processing requirements • Questionnaires and interviews

  29. Conceptual Design • A high-level data model (semantic data model) with the following characteristics: • Expressiveness • Simplicity • Minimallity • Diagrammatic Representation • Formality

  30. Approaches to Conceptual Database Design • Centralized • View integration • View (schema) integration • Identifying correspondence and conflicts among the views: • Naming conflict • Type conflict • Constraint conflict • Modifying views to confirm to one another • Merging views • Restructuring • Strategies

  31. Example: UML

  32. Example:EER

  33. Example: Relational Database Schema

  34. Some of the Currently Available Automated Database Design Tools

More Related