Please enable JavaScript.
Coggle requires JavaScript to display documents.
Introduction to databases - Coggle Diagram
Introduction to databases
1 Introduction to databases
Design
normalization vs denormalization
authorization
object-oriented database systems?
indexes
backup and recovery
Data Models, Schemas, and Instances
Conceptual data models
representational data models
physical data models
object data models
self-describing data models
Schema diagram
Database state or snapshot
Three-Schema Architecture and Data independence
External Level, conceptual Level, internal level
Logical data independence
Physical data independence
The database system environment
DBMS component Modules
Database System Utilities
Loading
Backup
Database storage reorganization
Perfermance monitoring
Monitoring access by users
Tools,Application Environments and Communications Facilities
CASE tools, data dictionary system
PowerBuilder, JBuilder
Communication software(DB/DC)
Centralizaed and Client/Server Architectures for DBMSs
2 Conceptual Data Modeling and Database Design
Chapter 3 Data modeling using ER model
Practice
Using High-Level Conceptual Data Models for Database Design
Conceptual design
data model operations are used to confirm the conceptual schema meets
implementation using a commercial DBMS(logical design)
Physical design
3.4 Relationship Types, Relationship Sets, Roles, and Structural Constraints
Degree of a Relationship(binary/ternary)
Recursive relationships or self-referencing relationships
Constraints on Binary Relationship Types
Cardinality Ratios for Binary Relationships
(1:1, 1:N, M:N)
Participation Constraints and Existence Dependencies
Minimum cardinality constraint
Total == /partial — participation(Existence dependency)
3.5 Weak Entity Types
can only be identified through its owner
a weak entity type normally has a partial key
Weak entity types can sometimes be represented as complex attributes
Naming and design choice
(Min, max) notation vs ratio/single-line/double-line notation
it is not sufficient for specifying some key constraints on higher-degree relationships
3.8 UML Class Diagrams vs ER Model Diagrams
Ways to represent multivalued attribute and
composite attribute
Relationship types are called associations
relationship instances are called links
The (min, max) notations is used to specify multiplicities in UML
In UML, association and aggregation do not have different structural properties,Aggregation is meant to represent a relationship between a whole object and its components.
UML distinguishes between unidirectional and bidirectional associations. Unidirectional association means that only one direction for accessing related objects is needed.
qualified association is used to construct weak entities
3.9 Relationship Types of Degree Higher than two
Choosing between Binary and Higher-Degree Relationships
Some database design tools, which permit only binary relationships, represent a ternary relationship as a week entity type.
It is possible to have a weak entity type with a ternary identifying relationship type
3.9.2 Two notations of specifying structural constraints on n-ray relationships
Chapter4 Enhanced Entity-Relationship Model
3 The Relational Data Model and SQL
4 Database Programming Techniques
5 Object,Object-Relational, and XML:
Concepts,Models,languages, and Standards
6 Database Design Theory and Normalization
7 File Structure,Hashing,indexing,and Physical Database Design
9 Transaction Processing, Concurrency Control and Recovery
8 Query Processing and Optimization
10 Distributed Databases, NoSQL,Systems, and Big Data
11 Advanced Database Models, Systems, and Application
12 Additional Database Topics Security