Scribd
Upload
67 views

APDIS107 Lecture 3

The document discusses database modeling and conceptual data models. It defines database models as collections of logical constructs used to represent data structures and relationships within a database. Database models have three components: the structural part defines rules for constructing databases; the manipulative part defines allowed data operations; and integrity rules ensure accurate data. Common conceptual data models include the entity-relationship model, semantic model, functional model, and object-oriented model. The relational, network, and hierarchical models are examples of record-based logical data models. Relationships in conceptual models can be one-to-one, one-to-many, or many-to-many. The document assigns questions on database relations, their properties, SQL, and simple queries.

Uploaded by

Aileen P. de Leon
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
67 views

APDIS107 Lecture 3

The document discusses database modeling and conceptual data models. It defines database models as collections of logical constructs used to represent data structures and relationships within a database. Database models have three components: the structural part defines rules for constructing databases; the manipulative part defines allowed data operations; and integrity rules ensure accurate data. Common conceptual data models include the entity-relationship model, semantic model, functional model, and object-oriented model. The relational, network, and hierarchical models are examples of record-based logical data models. Relationships in conceptual models can be one-to-one, one-to-many, or many-to-many. The document assigns questions on database relations, their properties, SQL, and simple queries.

Uploaded by

Aileen P. de Leon
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

DATABASE DESIGN AND MODELING Lecture # 3

MODELS – are simplified abstractions of real-world events or conditions. For example,


such abstractions will enable us to explore the characteristics of entities and the
relationships that can be created among such entities. If the models are not logically
sound, the database designs derived from them will not deliver the database system’s
promise of effective information drawn from an efficient database.

Good models yield good database designs that are the basis for good
applications.

DATABASE MODELS

Database Model – collection of logical constructs used to represent the data structure
and the data relationships found within the database.

- an integrated collection of concepts for describing and manipulating data,


relationships between data, and constraints on the data in an organization. A
data model represents the organizational itself. It should provide the basic
concepts and notations that will allow database designers and end-users
unambiguously and accurately to communicate their understanding of the
organizational data.

THREE COMPONENTS OF DATA MODELS:

a. STRUCTURAL PART – consisting of a set of rules according to which databases can


be constructed.

b. MANIPULATIVE PART – defining the types of operation that are allowed on the
data(this includes the operations that are used for updating or retrieving data from the
database and for changing the structure of the database).

c. SET OF INTEGRITY RULES – ensures that the data is accurate.

CATEGORIES OF CONCEPTUAL MODELING:

a. OBJECT-BASED DATA MODELS – use concepts such as entities, attributes and


relationships.

ENTITY – is a distinct object(a person, place, thing, concept, event) in the


organization that is to be represented in the database.

ATTRIBUTE – is a property that describes some aspect of the object that we


wish to record.
RELATIONSHIP – is an association between entities.

COMMON TYPES OF OBJECT-BASED DATA MODEL

a. Entity-Relationship
b. Semantic
c. Functional
d. Object-oriented

b. RECORD-BASED DATA MODELS – the database consists of a number of fixed-


format records possibly of differing types. Each record type defines a fixed number of
fields, each typically of a fixed length.

THREE PRINCIPAL TYPES OF RECORD-BASED LOGICAL DATA MODEL:

a. RELATIONAL DATA MODEL – is based on the concept of mathematical


relations. In the relational model, data and relationships are represented as
tables, each of which has a number of columns with a unique name.

b. NETWORK DATA MODEL – data is represented as collections of records, and


relationships are represented by sets. Compared with the relational model,
relationships are explicitly modeled by the sets, which become pointers in the
implementation. The records are organized as generalized graph structures with
records appearing as nodes and sets as edges in the graph.

c. HIERARCHICAL DATA MODEL – is a restricted type of network model. Data is


represented as collections of records and relationships are represented by sets.
However, the hierarchical model allows a node to have only one parent. A
hierarchical model can be represented as a tree graph, with records appearing
as nodes, also called as segments, and sets as edges.

c. PHYSICAL DATA MODELS – describe how data is stored in the computer,


representing information such as records structures, record orderings, and access
paths.

THREE TYPES OF RELATIONSHIPS OF CONCEPTUAL MODEL

1. ONE-TO-MANY RELATIONSHIP

A painter paints many different paintings, but each one of them is painted by only
that painter. Thus the painter(the “one”) is related to the paintings(the “many”).
Therefore, the database designers label the relationship “PAINTER” paints PAINTING”
as 1:M, Similarly, a customer account(the ”one”) might contain many invoices, but
those invoices(the “many”) are related to only a single customer account. The
“CUSTOMER generates INVOICE” relationship would also be labeled 1:M.
2. MANY-TO-MANY RELATIONSHIP

An employee might learn many job skills, and each job skill might be learned by
many employees. Database designers label the relationship “EMPLOYEE learns
SKILL” as M:N. Similarly, a student can take many courses, and each course can be
taken by many students, thus yielding the M:N relationship label for the relationship
expressed by “STUDENT takes COURSE”.

3. ONE-TO-ONE RELATIONSHIP

A retail company’s management structure may require that each one of its stores
be managed by a single employee. In turn, each store manager – who is an employee
– only manages a single store. Therefore, the relationship “EMPLOYEE manages
STORE” is labeled 1:1.

ASSIGNMENT:

a. What is DATABASE RELATIONS?


b. List down and discuss PROPERTIES OF RELATIONS.
c. Define what SQL is and its objectives.
d. Importance of SQL
e. Name simple/basic queries through examples

You might also like