Professional Documents
Culture Documents
Basic rules
e pt
s ic nc
Ba co
ancestor
Each segment can have only one ancestor
descendant
Example of design
1 Conceptual simplicity
01 Complexity of management
po ne
siti ga
ve 2 Database security tiv 02 Lack of structural independence
e
3 Data independence 03 Complexity of programming
04 Restrictions on implementation
4 Data integrity
05 Lack of standardization
5 Efficiency
Hierarchical database model
Structure of data.
Objects - elements Data integration.
of the hierarchy Structural independence of
data.
Data integrity.
Network database model
t
s ic nce
p Basic rules
Ba co
set
notation- member
Network database model
Example of design
1 Conceptual simplicity
po ne
siti ga
ve 2 Support for other types of
relationships
tiv
01 The complexity of the system as
e a whole
3 Flexible data access
02 Lack of structural independence
4 Data integrity
5 Independence
Network database model
--Representation of a
set of logically related Semantics of the model Set theory.
data and their Graph theory.
description in the
form of a network of
records
interconnected by
different types of
relationships.
--Support data
integrity.
Structure of data.
Notation elements. Data integration.
Elements of relationships. Structural independence of data.
Data integrity.
Entity-relationship database model
p t
s ic nce Basic rules
Ba co
weak entity
relationship
Entity-relationship database mode
Example of design
po ne
01 Insufficient opportunities to
siti ga present restrictions
ve 1 Conceptual simplicity tiv
Restrictions of opportunities to
e 02 present relationships
2 Visual presentation
Lack of data manipulation
03 language
Integration with the
3 relational database model 04 Loss of information
content
Entity-relationship database mode
Structure of data.
Entities. Data integration.
Relationships. Structural independence of data.
Attributes. Data integrity.
Relational database model
foreign key
Tables must contain a column with unique data
(primary key)
table scheme
Tables can contain columns with the values of
the primary keys of other tables (foreign key)
Relational database model
Example of design
1 Conceptual simplicity
po ne
siti ga
Design, implementation and Essential requirements for
ve 2 management simplicity tiv 01 hardware and software
e
3 Structural independence 02 Possibility of "early" projects
of data
The problem of "information
Arbitrary queries to the 03
4 database
islands"
5 Powerful DBMS
Relational database model
Set theory.
--Representation of a First order logic.
set of logically related
Semantics of the model Relational algebra.
data in the form of Relational calculations.
relations (tables).
--Data redundancy
control.
--Ensuring data
consistency.
--Support data
integrity.
p t Basic rules
s ic nce
Ba co
Example of design
po ne
siti 1 Adding semantic content
ga 01
Difficult navigation of data
access
ve tiv
The complexity of learning and
2 Semantic content of external e 02 programming
representation
04 Lack of standardization
4 Data integrity
Object-oriented database model
Set theory.
--Representation of a
set of logically related Semantics of the model Graph theory.
Discrete group theory.
data in the form of
objects of different
classes, containing
attributes and
methods.
--Data redundancy
control.
--Support data
integrity.