Scribd
Upload
45 views17 pages

UML and CODD's Rules

The document discusses Entity-Relationship (E-R) modeling and its comparison to the Unified Modeling Language (UML). It describes various E-R notation styles including Chen diagrams and IDEFIX notation. It also explains that UML class diagrams are similar to E-R diagrams but with differences in how relationships, cardinalities, and generalizations are depicted. The document provides examples of how constructs in E-R diagrams compare to their representations in UML class diagrams.

Uploaded by

SAQUEBA MAHIR
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
45 views17 pages

UML and CODD's Rules

The document discusses Entity-Relationship (E-R) modeling and its comparison to the Unified Modeling Language (UML). It describes various E-R notation styles including Chen diagrams and IDEFIX notation. It also explains that UML class diagrams are similar to E-R diagrams but with differences in how relationships, cardinalities, and generalizations are depicted. The document provides examples of how constructs in E-R diagrams compare to their representations in UML class diagrams.

Uploaded by

SAQUEBA MAHIR
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 17

Summary of Symbols Used in E-R Notation

Database System Concepts 7.1 ©Silberschatz, Korth and Sudarshan


Symbols Used in E-R Notation
(Cont.)

Database System Concepts 7.2 ©Silberschatz, Korth and Sudarshan


Alternative ER Notations
 Chen, IDE1FX, …

Database System Concepts 7.3 ©Silberschatz, Korth and Sudarshan


Alternative ER Notations

Chen IDE1FX (Crows


feet notation)

Database System Concepts 7.4 ©Silberschatz, Korth and Sudarshan


UML

 UML: Unified Modeling Language


 UML has many components to graphically model
different aspects of an entire software system
 UML Class Diagrams correspond to E-R Diagram, but
several differences.

Database System Concepts 7.5 ©Silberschatz, Korth and Sudarshan


 • Class diagram. A class diagram is similar to an E-R
diagram. Later in this section we illustrate a few
features of class diagrams and how they relate to E-R
diagrams.
 • Use case diagram. Use case diagrams show the
interaction between users and the system, in particular
the steps of tasks that users perform (such as
withdrawing money or registering for a course).
 • Activity diagram. Activity diagrams depict the flow of
tasks between various components of a system.
 • Implementation diagram. Implementation diagrams
show the system components and their
interconnections, both at the software component level
and the hardware component level.

Database System Concepts 7.6 ©Silberschatz, Korth and Sudarshan


Database System Concepts 7.7 ©Silberschatz, Korth and Sudarshan
Database System Concepts 7.8 ©Silberschatz, Korth and Sudarshan
Database System Concepts 7.9 ©Silberschatz, Korth and Sudarshan
ER vs. UML Class Diagrams

*Note reversal of position in cardinality constraint depiction

Database System Concepts 7.10 ©Silberschatz, Korth and Sudarshan


ER vs. UML Class Diagrams
ER Diagram Notation Equivalent in UML

*Generalization can use merged or separate arrows independent


of disjoint/overlapping
Database System Concepts 7.11 ©Silberschatz, Korth and Sudarshan
UML Class Diagrams (Cont.)

 Binary relationship sets are represented in UML by


just drawing a line connecting the entity sets. The
relationship set name is written adjacent to the line.
 The role played by an entity set in a relationship set
may also be specified by writing the role name on the
line, adjacent to the entity set.
 The relationship set name may alternatively be
written in a box, along with attributes of the
relationship set, and the box is connected, using a
dotted line, to the line depicting the relationship set.

Database System Concepts 7.12 ©Silberschatz, Korth and Sudarshan


 A simple class diagram for a commercial software application, in UML notation. The diagram
shows five classes: Customer, Corporate Customer, Personal Customer, Order and Order Line.
Every class is divided into three sections: name (shaded), attributes and methods (in cursive).
Classes might relate to each other inheritance. These relationships are denoted by decorated
links connecting two classes. For instance, the fact that the one customer can place more than
one order is represented by a single relationship between 'customer' and 'order'. The numbers
at the end-points of the link are the multiplicity of the relationship, telling how many objects
will participate in the relationship. In the example, the customer is related to 'n' orders, but
every order is only related to a single customer. Another typical relationship in UML
diagrams is inheritance. This applies when two classes are similar but have different features.
In the figure, both corporate customer and personal customer are related to the customer class
by an inheritance relationship, indicating that they are able to place orders but in different
ways.

Database System Concepts 7.13 ©Silberschatz, Korth and Sudarshan


E.F Codd

Database System Concepts 7.14 ©Silberschatz, Korth and Sudarshan


Database System Concepts 7.15 ©Silberschatz, Korth and Sudarshan
Database System Concepts 7.16 ©Silberschatz, Korth and Sudarshan
Database System Concepts 7.17 ©Silberschatz, Korth and Sudarshan

You might also like