Crow's Foot Notation & 2nd Normal Form: Presenter: Group 2

Crow's Foot Notation
&
2nd Normal Form
Presenter :
GROUP 2
Objectives:
 Explain what is Crow's Foot Notation and

2nd Normal Form.
 Give further knowledge about these two
type of Database Design.
 Show a framework design sample of these
two.
Topic one:
Crow's Foot Notation
Crow's Foot
Notation
 Invented by Gordon Everest, who originally
used the term "Inverted arrow" but now just
calls it "fork". For cardinality, a fork or crows
foot intuitively indicates "many", by its many
"toes".
 A graphical representation used in Entity-
Relationship Diagrams(ERDs) for database
design.
https://carlsonschool.umn.edu/sites/carlsonschool.umn.edu/files/geverest.jpg
Entities – represented as rectangles, where Attributes - attributes of entities are
In Crow's
each rectangle foot notation
represents an entity for Entity-Relationship diagrams
in your (ERDs),
typically depicted entities
as ovals (eclipse)and their
within
database schema. attributes are represented asthefollows:
entity rectangles.
Cardinality is indicated using "crow's foot"

symbols at the end of the
Relationships between entities are shown as relationship lines to represent the minimum
lines connecting the rectangles. and maximum number of instances of one
entity that can be associated with another
entity.
CROW'S FOOT NOTATION ENTITIES
Intersection Entities – used in the
resolution of a many-to-many relationship. Independent Entities – are those which
Dependent Entities – rely upon the
existence of other entities. Some of their
attributes are taken from the identifiers in
This resolution is done in order to store can exist without another entity. Student,
the entities upon which they depend. Class
additional information which doesn't fit seat, instructor, etc., are examples of
is an example of a dependent entity. It
into the attribute list of either entity in the independent entities.
relies upon course and section, and gets
M:M relationship.
two of its attributes from their identifiers.
Example:
Entity
Employee
EmployeeID (PK)
Attributes of FirstName
the LastName
"Employee" Email
entity Indicate it if the primary
Key of the "Employee"
entity.
7
Crow's foot
notation for
Entity-
Relationship
diagrams (ERDs),
symbols
Cardinality
Relationship has two indicators. These are shown on both side of the line.
 The first (Multiplicity) - refers to the maximum number of

times that an instance of one entity can be associated with
instances in the related entity. It can be one or many.
 The second – describes the minimum number of times one

can be related to others. It can be zero or one , and
accordingly describes the relationship as optional or
mandatory.
Relationship degrees make them readable as:
• One-to-one • One-to-many
• Many-to-many
SAMPLE PROBLEM
Consider the following business rules for a patient appointment system:
A doctor can be scheduled for many appointments, but may not have any scheduled at all. Each appointment is
scheduled with exactly 1 doctor. A patient can schedule 1 or more appointments. One appointment is scheduled
with exactly 1 patient. An appointment must generate exactly 1 bill, a bill is generated by only 1 appointment.
One payment is applied to exactly 1 bill, and 1 bill can be paid off over time by several payments. A bill can be
outstanding, having nothing yet paid on it at all. One patient can make many payments, but a single payment is
made by only 1 patient. Some patients are insured by an insurance company. If they are insured, they can only
carry insurance with one company. An insurance compnay can have many patients carry their policies. For
patients that carry insurance, the insurance company will make payments, each single payment is made by exactly
1 insurance company.
CROW'S FOOT NOTATION ADVANTAGES
CLARITY SIMPLICITY FLEXIBILITY
 Crow's Foot notation provides a  It simplifies complex database  Crow's Foot notation is versatile
clear and intuitive way to concepts by using standardized and can represent various types
represent the structure of a symbols and shapes. This of relationships and
database. Entities are depicted simplicity makes it easier to cardinalities. It can handle one-
as rectangles, relationships as create, read, and communicate to-one, one-to-many, and many-
lines, and cardinality using the database designs. to-many relationships with ease.
"crow's foot" symbols, making
it easier for both technical and
non-technical stakeholders to
understand the database schema
EASE OF LEARNING CONSISTENCY EFFICIENCY
 It is relatively easy to learn and  Since it's a standardized  Designing databases using
teach, making it a suitable notation, it promotes Crow's Foot notation can
choice for educational purposes consistency in database speed up the development
and for introducing newcomers
design across different process. It allows for quick
to database design.
projects and among team visualization of the database
members. schema, helping designers
identify potential issues
early on.
COMMUNICATION DOCUMENTATION STANDARDIZATION
 It facilitates effective  Crow's Foot notation serves as  Crow's Foot notation is a widely
communication between valuable documentation for recognized and accepted
different stakeholders involved databases. It provides a visual standard in the field of database
in a project, including representation that can be design. This standardization
developers, database referenced throughout the ensures that database designs
administrators, and business development lifecycle and are consistent and compatible
analysts. They can all easily during maintenance and across various platforms and
grasp the database structure and troubleshooting. organizations.
requirements.
Topic Two:
2nd Normal Form
SECOND NORMAL FORM
Second normal form, or 2NF, applies when database is of the following:

• Already in 1NF
• All partial dependencies on the primary key are removed.
EXAMPLE:
A university from GITTA (Geographic Information Technology Training Alliance) uses the following
relation:
Student (IDSt, StudentName, IDProf, ProfessorName, Grade)
The key attributes IDSt and IDProf are identification keys. All attributes are single valued (1NF).
1. The following functional dependencies exist:

2. The following attribute ProfessorName is functionally dependent o attribute IDProf (IDProf =>
ProfessorName)
3. The attribute StudentName is functionally dependent on IDSt (IDSt -> StudentName )
4. The attribute Grade is fully functional dependent on IDSt and IDProf (IDSt, IDProf, -> Grade)
EXPLAINED:
The table in this example is in first normal form (1NF) since all attributes are single
valued. But it is not yet in 2NF. If student 1 leaves university and the tuple is deleted, then we
lose all information about professor Schmid, since this attribute is fully functional dependent
on the primary key IDSt. To solve this problem, we must create a new table Professor with
the attribute Professor (the name) and the key IDProf. The third table Grade is necessary for
combining the two relations Student and Professor and to manage the grades. Besides the
grade it contains only the two IDs of the student and the professor. If now a student is
deleted, we do not loose the information about the professor.
Summary
• Discuss the whole reported topic and ask classmates if they understand the
lesson.
Sample footer text

GROUP 2 MEMBERS
 LEADER: Claudine Alicaway
 MEMBERS: Alison Grace L. Mernilo
Ira Antonette P. Barbacena
Maria Monica San Jose
Kenneth Asi
Ian Jay Anonuevo
Reginal Fenol
John Eric Troy Jizmundo
Ernesto DM Malate II

Crow's Foot Notation & 2nd Normal Form: Presenter: Group 2

Uploaded by

Copyright:

Available Formats

Crow's Foot Notation & 2nd Normal Form: Presenter: Group 2

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Crow's Foot Notation & 2nd Normal Form: Presenter: Group 2

Uploaded by

Copyright:

Available Formats

Crow's Foot Notation

 Explain what is Crow's Foot Notation and

Cardinality is indicated using "crow's foot"

 The first (Multiplicity) - refers to the maximum number of

 The second – describes the minimum number of times one

Second normal form, or 2NF, applies when database is of the following:

Student (IDSt, StudentName, IDProf, ProfessorName, Grade)

1. The following functional dependencies exist:

Sample footer text

You might also like