Slide 3-1
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
ExercisesApa beda database schema dan database state ?Apa beda logical data independence dan physical
data independence ?Apakah perbedaan two-tier & three-tier
architecture ?Data model merupakan representasi pisik
(physical representation) dari struktur basisdata. [T/F]
DDL biasanya digunakan oleh DBA untuk mengambil (retrieve) atau mengubah (update) data pada DBMS. [T/F]
Pada “two-tier architecture”, agar pemrosesan lebih cepat maka digunakan Application Server disamping Database server. [T/F]
Slide 3-2
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
More Exercise Pak Ali memiliki toko obat dirumahnya. Pada mulanya, Pak
Ali menyimpan informasi tokonya pada sebuah buku besar (jenis, stok, dan harga obat serta penjualannya). Namun semakin hari jumlah obat yang dimilikinya semakin banyak, baik dari segi jenis maupun jumlahnya sehingga buku besar tsb tidak memadai lagi. Untuk melakukan penghematan, Pak Ali memutuskan menggunakan DBMS, ia ingin membeli DBMS dengan fitur minimal dan tentunya dengan harga yg semurah mungkin. Ia berencana menjalankan DBMS tsb sebagai aplikasi stand-alone di PC-nya, dan ia tidak ingin men-share data tsb dengan orang lain. Indikasikan fitur-fitur DBMS apa saja yang seharusnya dibeli oleh Pak Ali ? 1. A security facility.2. Concurrency control.3. Backup dan recovery facility4. A view mechanism.5. A query language.
ER Modeling
The main reference of this presentation is the textbook and PPT from : Elmasri & Navathe, Fundamental of Database Systems, 4th edition, 2004, Chapter 3Additional resources: presentation prepared by Prof Steven A. Demurjian, Sr (http://www.engr.uconn.edu/~steve/courses.html)
Slide 3-4
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Chapter OutlinePhases of Database DesignExample Database Application (COMPANY)ER Model Concepts
– Entities and Attributes– Entity Types, Value Sets, and Key Attributes– Relationships and Relationship Types– Weak Entity Types– Roles and Attributes in Relationship Types
ER Diagrams - NotationLimitation of ER Diagram
Slide 3-5
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Phases of Database Design
Slide 3-6
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Example COMPANY Database
Requirements of the Company (oversimplified for illustrative purposes)
The company is organized into DEPARTMENTs. Each department has a name, number and an
employee who manages the department. We keep track of the start date of the
department manager.
Each department controls a number of PROJECTs. Each project has a name, number and is
located at a single location.
Slide 3-7
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Example COMPANY Database (Cont.)
We store each EMPLOYEE’s social security number, address, salary, sex, and birthdate. Each employee works for one department but may
work on several projects. We keep track of the number of hours per week
that an employee currently works on each project. We also keep track of the direct supervisor of each
employee.
Each employee may have a number of DEPENDENTs. For each dependent, we keep track of their name,
sex, birthdate, and relationship to employee.
Slide 3-8
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
An ER schema diagram for the COMPANY database
Slide 3-9
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Entities & AttributesEntities are specific objects or things in the mini-
world that are represented in the database. Physical existence car, house, employeeConceptual existence course, company, job
Attributes are properties used to describe an entity. For example an EMPLOYEE entity may have a Name, SSN,
Address, Sex, BirthDateA specific entity will have a value for each of its
attributes. For example a specific employee entity may have
Name='John Smith', SSN='123456789', Address ='731, Fondren, Houston, TX', Sex='M', BirthDate='09-JAN-55‘
Each attribute has a value set (or data type) associated with it – e.g. integer, string, subrange, enumerated type, …
Slide 3-10
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Types of Attributes (1)Simple
Each entity has a single atomic value for the attribute. For example: SSN or Sex.
CompositeThe attribute may be composed of several
components. For example: Address (Apt#, House#, Street, City,
State, ZipCode, Country) or Name (FirstName, MiddleName, LastName).
Composition may form a hierarchy where some components are themselves composite.
Multi-valuedAn entity may have multiple values for that attribute. For example, Color of a CAR or PreviousDegrees of a
STUDENT. Denoted as {Color} or {PreviousDegrees}.
Slide 3-11
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Types of Attributes (2) In general, composite and multi-valued attributes may
be nested arbitrarily to any number of levels although this is rare. For example, PreviousDegrees of a STUDENT is a composite
multi-valued attribute denoted by {PreviousDegrees (College, Year, Degree, Field)}.
Stored vs Derived Attibutes Stored – regular attribute Derived -- attribute which is calculated from a stored attribute BirthDate vs Age
Null Values “nothing”, not zero, not blank space! Ex. College Degree for Employee entity
Slide 3-12
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Entities with attribute values
e1: employee c1: company
Slide 3-13
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
A hierarchy of composite attributes
Slide 3-14
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Complex attributesComposite and multi-valued attributes
can be nested in an arbitrary way() for nesting{} for multi valueExample
{Address&Phone ({Phone(AreaCode, PhoneNumber)},Address(StreetAddress(Number, Street,
ApartmentNumber), City, State, Zip))
}
Slide 3-15
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Entity Type
It defines the set of possible entities with the same attributes
For example, ‘employee type’ is the set of employees in the company
Slide 3-16
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Key Attributes of an Entity Type
What makes an entity unique?An employee: SSNA company: nameA project: number, nameA purchase slip may have 2 keys:
date & time
Slide 3-17
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Key Attribute
Selection of the keys is an important part of the database design It affects integrity validation and
performance Declaring an attribute as a key, and
declaring it 'duplicates not allowed' we can prevent users form entering erroneous duplicate data
The key can also maintain integrity by linking the key with a key in another table.
Slide 3-18
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Selection Key AttributeThe key should be an attribute that
doesn't changeExample: ssn, employee_ID, SKU (stock-
keeping-unit), license plate number.The key can't be a null. It must have a
valid valueExample: Actual graduation date for a student
would be a bad choiceAvoid using keys that have intelligence or
codes built inExample: A building code (which might later
be subject to change)
Slide 3-19
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Key Attributes
A key attribute may be composite. For example, VehicleTagNumber is a key of the
CAR entity type with components (Number, State).
An entity type may have more than one key. For example, the CAR entity type may have two keys:VehicleIdentificationNumber (popularly called
VIN) andVehicleTagNumber (Number, State), also
known as license_plate number.
Slide 3-20
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Entity type CAR with Attributes
car1((ABC 123, TEXAS), TK629, Ford Mustang, convertible, 1999, (red, black))
car2
((ABC 123, NEW YORK), WP9872, Nissan 300ZX, 2-door, 2002, (blue))car3
((VSY 720, TEXAS), TD729, Buick LeSabre, 4-door, 2003, (white, blue))
.
.
.
CARRegistration(RegistrationNumber, State), VehicleID, Make, Model, Year, (Color)
Slide 3-21
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Value Sets
Possible values of an attribute.Usually:
NumericTextBooleanEtc.
But can be more specific, for example:Birth date must be > 1850 but before <(now)Sex must be either female or male
Slide 3-22
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Two Other Entity Types
Slide 3-23
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Initial Entity Concept of Company Database
Slide 3-24
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Persons: agency, contractor, customer, department, division, employee, instructor, student, supplier.
Places: sales region, building, room, branch office, campus.
Objects: book, machine, part, product, raw material, software license, software package, tool, vehicle model, vehicle.
Events: application, award, cancellation, class, flight, invoice, order, registration, renewal, requisition, reservation, sale, trip.
Concepts: account, block of time, bond, course, fund, qualification, stock.
Specifying EntityEntity – a class of persons, places, objects, events, or concepts about which we need to capture and store data.
Named by a singular noun
Slide 3-25
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Weak Entity Types
An entity that does not have a key attributeA weak entity must participate in an identifying
relationship type with an owner or identifying entity typeEntities are identified by the combination of:
A partial key of the weak entity typeThe particular entity they are related to in the
identifying entity typeExample: Suppose that a DEPENDENT entity is identified by the
dependent’s first name and birhtdate, and the specific EMPLOYEE that the dependent is related to. DEPENDENT is a weak entity type with EMPLOYEE as its identifying entity type via the identifying relationship type DEPENDENT_OF
Slide 3-26
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Weak Entity Type is: DEPENDENTIdentifying Relationship is: DEPENDENTS_OF
Slide 3-27
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Relationships
A relationship relates two or more distinct entities with a specific meaning. For example: EMPLOYEE John Smith works on the ProductX PROJECT EMPLOYEE Franklin Wong manages the Research
DEPARTMENT.
Relationships of the same type are grouped or typed into a relationship type. For example: WORKS_ON relationship type in which EMPLOYEEs and
PROJECTs participate MANAGES relationship type in which EMPLOYEEs and
DEPARTMENTs participate.
Slide 3-28
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Relationships and Relationship Types
Degree of a Relationship Type is the Number of Participating Entity Types Binary Relationship Between two entities Ternary Relationship Among three entities N-ary Relationship Among N entities
More Than One Relationship Type Can Exist With the Same Participating Entity Types MANAGES and WORKS_FOR are Distinct Relationships
Between EMPLOYEE and DEPARTMENT Entity Types
Relationships are Directional SUPPLIES: SUPPLIER to PARTS SUPPLIERS: PARTS to SUPPLIER
Slide 3-29
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Binary Relationship
Slide 3-30
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Ternary Relationship
Slide 3-31
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
ER DIAGRAM – Relationship Types are:WORKS_FOR, MANAGES, WORKS_ON, CONTROLS,SUPERVISION, DEPENDENTS_OF
Slide 3-32
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Constraints on Relationships
Constraints on Relationship Types( Also known as ratio constraints ) Maximum Cardinality
One-to-one (1:1) One-to-many (1:N) or Many-to-one (N:1) Many-to-many
Minimum Cardinality (also called participation constraint or existence dependency constraints) zero (optional participation, not existence-
dependent) one or more (mandatory, existence-dependent)
Slide 3-33
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
One-to-One WORKS_ON Relationship
WORKS_ONRelationship Instances
EMPLOYEE Set PROJECT Set
Slide 3-34
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Many-to-one (N:1) RELATIONSHIP
e1
e2
e3
e4
e5
e6
e7
EMPLOYEE
r1
r2
r3
r4
r5
r6
r7
WORKS_FOR
d1
d2
d3
DEPARTMENT
Slide 3-35
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Many-to-many (M:N) RELATIONSHIP
e1
e2
e3
e4
e5
e6
e7
r1
r2
r3
r4
r5
r6
r7
p1
p2
p3
r8
r9
Slide 3-36
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Recursive Relationship
We can also have a recursive relationship type.Both participations are same entity type in different
roles.For example, SUPERVISION relationships between
EMPLOYEE (in role of supervisor or boss) and (another) EMPLOYEE (in role of subordinate or worker).
In following figure, first role participation labeled with 1 and second role participation labeled with 2.
In ER diagram, need to display role names to distinguish participations.
Slide 3-37
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
A RECURSIVE RELATIONSHIP SUPERVISION
e1
e2
e3
e4
e5
e6
e7
EMPLOYEE
r1
r2
r3
r4
r5
r6
SUPERVISION
21
1 2
2
1
1
1
2
1
2
2
© The Benjamin/Cummings Publishing Company, Inc. 1994, Elmasri/Navathe, Fundamentals of Database Systems, Second Edition
Slide 3-38
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Recursive Relationship Type is: SUPERVISION(participation role names are shown)
Slide 3-39
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Attributes of Relationship types
A relationship type can have attributes; for example, HoursPerWeek of
WORKS_ON; its value for each relationship instance describes the number of hours per week that an EMPLOYEE works on a PROJECT.
Slide 3-40
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Attribute of a Relationship Type is: Hours of WORKS_ON
Slide 3-41
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Specifying RelationshipExamine every combination of two entities
and see whether there is a possible relationship between them This is often documented using a matrix that lists
the entity names on both axes. A symbol is entered at the intersection of each
row and column to indicate the existence of a possible relationship.
This technique becomes unusable if the model is large.
Look at the requirements documents to find relationships indicated by the documents.
The two techniques can be used together
Slide 3-42
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Structural Constraints – one way to express semantics of relationships
Structural constraints on relationships:
Cardinality ratio (of a binary relationship): 1:1, 1:N, N:1, or M:N
SHOWN BY PLACING APPROPRIATE NUMBER ON THE LINK.
Participation constraint (on each participating entity type): total (called existence dependency) or partial.
SHOWN BY DOUBLE LINING THE LINK
NOTE: These are easy to specify for Binary Relationship Types.
Slide 3-43
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Alternative (min, max) notation for relationship structural constraints:
Specified on each participation of an entity type E in a relationship type R
Specifies that each entity e in E participates in at least min and at most max relationship instances in R
Default (no constraint): min=0, max=n Must have minmax, min0, max 1 Derived from the knowledge of mini-world
constraints Min=0 implies partial participation Min>0 implies total participation
Slide 3-44
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Alternative (min, max) notation for relationship structural constraints:
Examples: A department has exactly one manager and an
employee can manage at most one department.– Specify (0,1) for participation of EMPLOYEE in
MANAGES– Specify (1,1) for participation of DEPARTMENT in
MANAGES An employee can work for exactly one
department but a department can have any number of employees.
– Specify (1,1) for participation of EMPLOYEE in WORKS_FOR
– Specify (0,n) for participation of DEPARTMENT in WORKS_FOR
Slide 3-45
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
The (min,max) notation relationship constraints
(1,1)(0,1)
(1,N)(1,1)
Slide 3-46
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
COMPANY ER Schema Diagram using (min, max) notation
Slide 3-47
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Naming Convention
Choose names (for entity types, attributes, relationship types) that convey the meanings attached to the different constructs in the schema
Use singular names for entity typesUse uppercase for entity type and relation type
namesUse capitalized name for attributesUse lowercase for role namesNouns tend to give rise to entity type namesVerbs tend to indicate names of relationship
types
Slide 3-48
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Design Choices for ER
Design process: iterative process with some common refinements: A concept may be first modeled as an attribute and then
refined into relationship because it is determined that the attribute is a reference to another entity types
An attribute that exist in several entity types may be promoted to an independent entity types
In UNIVERSITY db, STUDENT, INSTRUCTOR & COURSE, each has an attribute Department in the initial design, then create DEPARTMENT entity with DeptName as attribute and relate it to the three entities. Other attribute may be discovered later.
An inverse refinement to the previous case may be applied
If DEPARTMENT exist in the initial design with single attribute and relate only to one other entity, STUDENT. Then reduced it into attribute of STUDENT.
Refinement on specialization, generalization & higher degree relationship see next chapter.
Slide 3-49
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
Data Modeling ToolsA number of popular tools that cover
conceptual modeling and mapping into relational schema design. Examples: Ms. Visio, ER-Win,
DBDesigner, S-Designer (Enterprise Application Suite), ER-Studio, etc.
Serves as documentation of application requirements, easy user interface - mostly graphics editor support
Slide 3-50
Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionRevised by IB & SAM, Fasilkom UI, 2005
SUMMARY OF ER-DIAGRAM NOTATION FOR ER SCHEMAS
Meaning
ENTITY TYPE
WEAK ENTITY TYPE
RELATIONSHIP TYPE
IDENTIFYING RELATIONSHIP TYPE
ATTRIBUTE
KEY ATTRIBUTE
MULTIVALUED ATTRIBUTE
COMPOSITE ATTRIBUTE
DERIVED ATTRIBUTE
TOTAL PARTICIPATION OF E2 IN R
CARDINALITY RATIO 1:N FOR E1:E2 IN R
STRUCTURAL CONSTRAINT (min, max) ON PARTICIPATION OF E IN R
Symbol
E1 R E2
E1 R E2
R(min,max)
E
N