Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
An overview of database design using unified modelling language (uml) class diagrams and their translation into database schemas. Topics include the history of uml, the process of translating uml diagrams into database schemas, functional dependencies and normal forms, file access methods, query optimization, and transactions and recovery. The document also mentions the use of sql and the relational model in the context of database design.
Typology: Slides
1 / 68
This page cannot be seen from the preview
Don't miss anything!
Lecture 4: Overview of Database Design and DBMS Implementation
Modelling with UML Translating a UML Class Diagram to a Database Schema Normal Forms and Bottom-up Schema Synthesis File access methods Query Optimisation Transations and Recovery
There will be NO LECTURE next Wednesday 6 August (and probably other Wednesdays in lab-weeks, stay tuned)
There will be NO LECTURE next Wednesday 6 August (and probably other Wednesdays in lab-weeks, stay tuned) Greg will be taking the Tuesday 9am lab, not the Thursday 9am one as previously speculated Some people have not yet enrolled in a lab group, please do so before next week
There will be NO LECTURE next Wednesday 6 August (and probably other Wednesdays in lab-weeks, stay tuned) Greg will be taking the Tuesday 9am lab, not the Thursday 9am one as previously speculated Some people have not yet enrolled in a lab group, please do so before next week Why only 5 enrolments in the Friday 9am group???
UML Model
Relational Model
Computer
translation
DBMS implemention
Last Thursdays lectures introduced the middle of the three conceptual levels Today we overview the top and bottom
UML Model
Relational Model
Computer
translation
DBMS implemention
Last Thursdays lectures introduced the middle of the three conceptual levels Today we overview the top and bottom This material will be covered in the 2nd half of the course
The entity-Relationship model, and its diagrams, were introduced by Chen in 1976 to simplify database design This began a huge research field “conceptual modelling”, which aims to capture requirements using “real world” concepts (entity, relationship) rather than computer or mathematical concepts
conceptual modelling and object oriented ideas used by “methodologists” around 1990
conceptual modelling and object oriented ideas used by “methodologists” around 1990 Mid 1990’s, main methodologists join forces creating the Unified Modelling Language (UML) Complete systems created using just UML and tools (way of the future?)
conceptual modelling and object oriented ideas used by “methodologists” around 1990 Mid 1990’s, main methodologists join forces creating the Unified Modelling Language (UML) Complete systems created using just UML and tools (way of the future?) Many diagram types, but we will only use simple class diagrams, mostly equivalent to ER
conceptual modelling and object oriented ideas used by “methodologists” around 1990 Mid 1990’s, main methodologists join forces creating the Unified Modelling Language (UML) Complete systems created using just UML and tools (way of the future?) Many diagram types, but we will only use simple class diagrams, mostly equivalent to ER (we ignore important semantic differences between ER and UML) I am biased, but I think the UML diagrams look much simpler and are easer to understand!
Employee fname: String minit: String lname: Char bdate: Date address: String sex: Char salary: Integer
Manages startDate: Date
Department name: String
Location name: String
Project name: String
0..1 supervisor
supervisee*
employs4..* works for0.. managed by 1 manages0.. 1 controlled by *controls
0..*
0..
1
0..
The database we will use in the first lab is adapted from [E&N Figure 5.5, 5.6]. It is shown as a UML class diagram in [E&N Figure 3.16]. Here is an adapted (and corrected!) version to match our lab material.
The boxes represent classes. They represent a kind of thing that can exist in our scenario. Each class has many objects , its instances.
the top compartment contains the class name
The boxes represent classes. They represent a kind of thing that can exist in our scenario. Each class has many objects , its instances.
the top compartment contains the class name the middle compartment contains the attributes (warning - same word, different context)
