1/43
Looks like no tags are added yet.
View Level
this abstraction level improves user engagement by giving many views or perspectives a single database. It is accessible to all viewers and is the simplest and most basic level.
Logical / Conceptual Level
This abstraction level describes what data is kept in the database and how those data are connected to one another.
attempts to describe the full or complete database set by defining what tables should be built and what the relationships between those tables should be.
Physical Level
This abstraction level defines how data is stored, data structures for storing data, and data access procedures at the lowest level of abstraction for dbms.
Data Model
A diagram that displays a set of tables and the relationships between them
Model
an abstraction of a real-world object or event
Useful in understanding complexities of the real-world environment
1971
creation date of ER Models
Peter Chen
proposed the ER Diagrams in 1971 to create a uniform convention that can be used as a conceptual modeling tool.
Entity Relationship Diagram
is a data modeling technique used in software engineering to produce a conceptual data model of an information system
Blue print
official documentation
Data Model
modeling revolves around discovering and analyzing organizational and users data requirements.
ERD
The major activity of this phase is identifying entities, attributes, and their relationships to construct model
Rectangles
This Entity Relationship Diagram symbol represents entity types
Ellipses
represents attributes
Diamonds
represents relationship types
Lines
links attributes to entity types & entity types with other relationship types
Primary Key
underlines the attributes (primary keys)
Double Ellipses
represents multi-valued attribute
Entity
anything (people, places, objects, events, etc.) about which we store information (e.g. supplier, machine tool, employee, utility pole, airline seat, etc.).
Entity Instance
A single occurrence of an entity. (Diagram with 6 instances)
Weak Entity
A type of entity that does not have any unique key for the attribute tuples.
Attribute
It contains a piece of information that describes an entity.
Key Attribute
An attribute that uniquely identifies an entity from an entity set.
Composite Attribute
An attribute that is composed of several other attributes.
Multivalued Attribute
An attribute that can possess more than one value.
Derived Attribute
An attribute that can be derived from other attributes of the entity.
Relationship
The diamond shape showcases a relationship in the ER diagram
How to find Relationships?
Typically indicated by a verb connecting two or more entities
Ex: Employees are assigned to projects.
Cardinality
The number of occurrences in one entity which are associated to the number of occurrences in another
One-to-One Relationship
When a single element of an entity is associated with a single element of another entity.
One-to-Many Relationship
When a single element of an entity is associated with more than one element of another entity.
Many-to-One Relationship
When more than one element of an entity is related to a single element of another entity.
Many-to-Many Relationship
When more that one element of an entity is associated with more than one element of another entity.
Identifier
Attributes that uniquely identify entity instances.
Composite Identifiers
are identifiers that consist of two or more attributes.
Crow’s Foot Notation
Known as IE notation (most popular)
Discovering Business Rules
After reviewing and studying the interview and various forms, develop a draft business rules - does not need to be bi-directional and less precise wording…
Sources of Business Rules
Direct interviews with internal & external stakeholders
Site visitations (collect data) and observation of the work process or procedure
Review and study of documents (Policies, Procedures, Forms, Operation manuals, etc.)
Business Rule 1
The data can be considered significant only after business rules are defined.
Without them, it cannot be considered as data for RDS but just records.
Simple Attribute
Cannot be subdivided
Ex: Age, Gender, Marital Status
Composite Attribute
Can be further subdivided to yield additional attributes
Ex1: ADDRESS → Street, City, State, Zip
Ex2: PHONE NUMBER → Area code, Exchange number
Derived Attribute
Is not physically stored within the database. Instead, it is derived by using an algorithm
Ex1: Late Charge of 2%
MS Access: InvoiceAmt * 0.02
Ex2: AGE can be derived from the date of birth and the current date.
MS Access: int(Date() — Emp_Dob)/365)
Single-Valued Attribute
Can only have a single (atomic) value.
Examples:
A person can have only one social security number.
A manufactured part can have only one serial number
A single-valued attribute is not necessarily a simple attribute.
Part No: CA-08-02-189935
Location: CA, Factory#:08, shift#: 02, part#: 189935
Multi-Valued Attributes
Can have many values.
Examples:
A person may have several college degrees.
A household may have several phones with different numbers
A car color
Procedure of ERD
Relatively simple representations of complex realworld data structures.
Data modeling is an iterative process.
“complete” and “100% error free” model is not possible!
Only “Optimized” model is possible….