Here are the key entities and relationships based on the information provided:
Entities:
- Department
- Employee
- Supervisor
- Project
Relationships:
- Department has one supervisor (1:1)
- Department has many employees (1:M)
- Employee works in one or more departments (M:N)
- Project has many employees assigned (1:M)
- Employee works on one or more projects (M:N)
The important attributes that uniquely identify each entity are also specified, such as employee number, department code, project number. This provides the foundation for modeling the database schema to represent these real world entities and relationships.
The Relational Data Model and Relational Database Constraints Ch5 (Navathe 4t...Raj vardhan
The Relational Data Model and Relational Database Constraints
Ch5 (Navathe 4th edition)/ Ch7 (Navathe 3rd edition)
Example of STUDENT Relation(figure 5.1)
ESOFT Metro Campus - Diploma in Software Engineering - (Module IV) Database Concepts
(Template - Virtusa Corporate)
Contents:
Introduction to Databases
Data
Information
Database
Database System
Database Applications
Evolution of Databases
Traditional Files Based Systems
Limitations in Traditional Files
The Database Approach
Advantages of Database Approach
Disadvantages of Database Approach
Database Management Systems
DBMS Functions
Database Architecture
ANSI-SPARC 3 Level Architecture
The Relational Data Model
What is a Relation?
Primary Key
Cardinality and Degree
Relationships
Foreign Key
Data Integrity
Data Dictionary
Database Design
Requirements Collection and analysis
Conceptual Design
Logical Design
Physical Design
Entity Relationship Model
A mini-world example
Entities
Relationships
ERD Notations
Cardinality
Optional Participation
Entities and Relationships
Attributes
Entity Relationship Diagram
Entities
ERD Showing Weak Entities
Super Type / Sub Type Relationships
Mapping ERD to Relational
Map Regular Entities
Map Weak Entities
Map Binary Relationships
Map Associated Entities
Map Unary Relationships
Map Ternary Relationships
Map Supertype/Subtype Relationships
Normalization
Advantages of Normalization
Disadvantages of Normalization
Normal Forms
Functional Dependency
Purchase Order Relation in 0NF
Purchase Order Relation in 1NF
Purchase Order Relations in 2NF
Purchase Order Relations in 3NF
Normalized Relations
BCNF – Boyce Codd Normal Form
Structured Query Language
What We Can Do with SQL ?
SQL Commands
SQL CREATE DATABASE
SQL CREATE TABLE
SQL DROP
SQL Constraints
SQL NOT NULL
SQL PRIMARY KEY
SQL CHECK
SQL FOREIGN KEY
SQL ALTER TABLE
SQL INSERT INTO
SQL INSERT INTO SELECT
SQL SELECT
SQL SELECT DISTINCT
SQL WHERE
SQL AND & OR
SQL ORDER BY
SQL UPDATE
SQL DELETE
SQL LIKE
SQL IN
SQL BETWEEN
SQL INNER JOIN
SQL LEFT JOIN
SQL RIGHT JOIN
SQL UNION
SQL AS
SQL Aggregate Functions
SQL Scalar functions
SQL GROUP BY
SQL HAVING
Database Administration
SQL Database Administration
Entity type
Entity sets
Attributes and keys
Relationship model
Mapping Constraints
The ER Model
Cardinality Constraints
Generalization, Specialization and Aggregation
ER Diagram & Database design with the ER Model
Introduction
Relational Model
Concepts
Characteristics
● Data Modeling and Data Models.
● Business Rules (Translating Business Rules into Data Model Components).
● Emerging Data Models: Big Data and NoSQL.
● Degrees of Data Abstraction (External, Conceptual, Internal and Physical model).
The Relational Data Model and Relational Database Constraints Ch5 (Navathe 4t...Raj vardhan
The Relational Data Model and Relational Database Constraints
Ch5 (Navathe 4th edition)/ Ch7 (Navathe 3rd edition)
Example of STUDENT Relation(figure 5.1)
ESOFT Metro Campus - Diploma in Software Engineering - (Module IV) Database Concepts
(Template - Virtusa Corporate)
Contents:
Introduction to Databases
Data
Information
Database
Database System
Database Applications
Evolution of Databases
Traditional Files Based Systems
Limitations in Traditional Files
The Database Approach
Advantages of Database Approach
Disadvantages of Database Approach
Database Management Systems
DBMS Functions
Database Architecture
ANSI-SPARC 3 Level Architecture
The Relational Data Model
What is a Relation?
Primary Key
Cardinality and Degree
Relationships
Foreign Key
Data Integrity
Data Dictionary
Database Design
Requirements Collection and analysis
Conceptual Design
Logical Design
Physical Design
Entity Relationship Model
A mini-world example
Entities
Relationships
ERD Notations
Cardinality
Optional Participation
Entities and Relationships
Attributes
Entity Relationship Diagram
Entities
ERD Showing Weak Entities
Super Type / Sub Type Relationships
Mapping ERD to Relational
Map Regular Entities
Map Weak Entities
Map Binary Relationships
Map Associated Entities
Map Unary Relationships
Map Ternary Relationships
Map Supertype/Subtype Relationships
Normalization
Advantages of Normalization
Disadvantages of Normalization
Normal Forms
Functional Dependency
Purchase Order Relation in 0NF
Purchase Order Relation in 1NF
Purchase Order Relations in 2NF
Purchase Order Relations in 3NF
Normalized Relations
BCNF – Boyce Codd Normal Form
Structured Query Language
What We Can Do with SQL ?
SQL Commands
SQL CREATE DATABASE
SQL CREATE TABLE
SQL DROP
SQL Constraints
SQL NOT NULL
SQL PRIMARY KEY
SQL CHECK
SQL FOREIGN KEY
SQL ALTER TABLE
SQL INSERT INTO
SQL INSERT INTO SELECT
SQL SELECT
SQL SELECT DISTINCT
SQL WHERE
SQL AND & OR
SQL ORDER BY
SQL UPDATE
SQL DELETE
SQL LIKE
SQL IN
SQL BETWEEN
SQL INNER JOIN
SQL LEFT JOIN
SQL RIGHT JOIN
SQL UNION
SQL AS
SQL Aggregate Functions
SQL Scalar functions
SQL GROUP BY
SQL HAVING
Database Administration
SQL Database Administration
Entity type
Entity sets
Attributes and keys
Relationship model
Mapping Constraints
The ER Model
Cardinality Constraints
Generalization, Specialization and Aggregation
ER Diagram & Database design with the ER Model
Introduction
Relational Model
Concepts
Characteristics
● Data Modeling and Data Models.
● Business Rules (Translating Business Rules into Data Model Components).
● Emerging Data Models: Big Data and NoSQL.
● Degrees of Data Abstraction (External, Conceptual, Internal and Physical model).
Software Engineering - Introduction and Motivation (Marcello Thiry)Marcello Thiry
Software Engineering Undergraduate Course Presentations
Introduction and Motivation
University of Vale do Itajaí
Univali
Incremental Tecnologia
English version
2024.06.01 Introducing a competency framework for languag learning materials ...Sandy Millin
http://sandymillin.wordpress.com/iateflwebinar2024
Published classroom materials form the basis of syllabuses, drive teacher professional development, and have a potentially huge influence on learners, teachers and education systems. All teachers also create their own materials, whether a few sentences on a blackboard, a highly-structured fully-realised online course, or anything in between. Despite this, the knowledge and skills needed to create effective language learning materials are rarely part of teacher training, and are mostly learnt by trial and error.
Knowledge and skills frameworks, generally called competency frameworks, for ELT teachers, trainers and managers have existed for a few years now. However, until I created one for my MA dissertation, there wasn’t one drawing together what we need to know and do to be able to effectively produce language learning materials.
This webinar will introduce you to my framework, highlighting the key competencies I identified from my research. It will also show how anybody involved in language teaching (any language, not just English!), teacher training, managing schools or developing language learning materials can benefit from using the framework.
Model Attribute Check Company Auto PropertyCeline George
In Odoo, the multi-company feature allows you to manage multiple companies within a single Odoo database instance. Each company can have its own configurations while still sharing common resources such as products, customers, and suppliers.
The Art Pastor's Guide to Sabbath | Steve ThomasonSteve Thomason
What is the purpose of the Sabbath Law in the Torah. It is interesting to compare how the context of the law shifts from Exodus to Deuteronomy. Who gets to rest, and why?
The Indian economy is classified into different sectors to simplify the analysis and understanding of economic activities. For Class 10, it's essential to grasp the sectors of the Indian economy, understand their characteristics, and recognize their importance. This guide will provide detailed notes on the Sectors of the Indian Economy Class 10, using specific long-tail keywords to enhance comprehension.
For more information, visit-www.vavaclasses.com
Synthetic Fiber Construction in lab .pptxPavel ( NSTU)
Synthetic fiber production is a fascinating and complex field that blends chemistry, engineering, and environmental science. By understanding these aspects, students can gain a comprehensive view of synthetic fiber production, its impact on society and the environment, and the potential for future innovations. Synthetic fibers play a crucial role in modern society, impacting various aspects of daily life, industry, and the environment. ynthetic fibers are integral to modern life, offering a range of benefits from cost-effectiveness and versatility to innovative applications and performance characteristics. While they pose environmental challenges, ongoing research and development aim to create more sustainable and eco-friendly alternatives. Understanding the importance of synthetic fibers helps in appreciating their role in the economy, industry, and daily life, while also emphasizing the need for sustainable practices and innovation.
This is a presentation by Dada Robert in a Your Skill Boost masterclass organised by the Excellence Foundation for South Sudan (EFSS) on Saturday, the 25th and Sunday, the 26th of May 2024.
He discussed the concept of quality improvement, emphasizing its applicability to various aspects of life, including personal, project, and program improvements. He defined quality as doing the right thing at the right time in the right way to achieve the best possible results and discussed the concept of the "gap" between what we know and what we do, and how this gap represents the areas we need to improve. He explained the scientific approach to quality improvement, which involves systematic performance analysis, testing and learning, and implementing change ideas. He also highlighted the importance of client focus and a team approach to quality improvement.
The French Revolution, which began in 1789, was a period of radical social and political upheaval in France. It marked the decline of absolute monarchies, the rise of secular and democratic republics, and the eventual rise of Napoleon Bonaparte. This revolutionary period is crucial in understanding the transition from feudalism to modernity in Europe.
For more information, visit-www.vavaclasses.com
The Roman Empire A Historical Colossus.pdfkaushalkr1407
The Roman Empire, a vast and enduring power, stands as one of history's most remarkable civilizations, leaving an indelible imprint on the world. It emerged from the Roman Republic, transitioning into an imperial powerhouse under the leadership of Augustus Caesar in 27 BCE. This transformation marked the beginning of an era defined by unprecedented territorial expansion, architectural marvels, and profound cultural influence.
The empire's roots lie in the city of Rome, founded, according to legend, by Romulus in 753 BCE. Over centuries, Rome evolved from a small settlement to a formidable republic, characterized by a complex political system with elected officials and checks on power. However, internal strife, class conflicts, and military ambitions paved the way for the end of the Republic. Julius Caesar’s dictatorship and subsequent assassination in 44 BCE created a power vacuum, leading to a civil war. Octavian, later Augustus, emerged victorious, heralding the Roman Empire’s birth.
Under Augustus, the empire experienced the Pax Romana, a 200-year period of relative peace and stability. Augustus reformed the military, established efficient administrative systems, and initiated grand construction projects. The empire's borders expanded, encompassing territories from Britain to Egypt and from Spain to the Euphrates. Roman legions, renowned for their discipline and engineering prowess, secured and maintained these vast territories, building roads, fortifications, and cities that facilitated control and integration.
The Roman Empire’s society was hierarchical, with a rigid class system. At the top were the patricians, wealthy elites who held significant political power. Below them were the plebeians, free citizens with limited political influence, and the vast numbers of slaves who formed the backbone of the economy. The family unit was central, governed by the paterfamilias, the male head who held absolute authority.
Culturally, the Romans were eclectic, absorbing and adapting elements from the civilizations they encountered, particularly the Greeks. Roman art, literature, and philosophy reflected this synthesis, creating a rich cultural tapestry. Latin, the Roman language, became the lingua franca of the Western world, influencing numerous modern languages.
Roman architecture and engineering achievements were monumental. They perfected the arch, vault, and dome, constructing enduring structures like the Colosseum, Pantheon, and aqueducts. These engineering marvels not only showcased Roman ingenuity but also served practical purposes, from public entertainment to water supply.
2. Learning outcome
1
¨ Define database
¨ Describe component of database table.
¤ Record (Tuple)
¤ Attribute (Field)
¤ Domain
¤ Degree
¤ Cardinality
¨ Describe characteristic of relation scheme.
¤ Relation Name
¤ Attribute Name
¤ Domain
3. Learning outcomes
2
¨ Describe the relation instance
¨ Identify relation keys:
¤ Primary Key
¤ Candidate Key
¤ Foreign Key
¨ Explain Relational Model Relationship
¤ One to Many
¤ Many to Many
¤ Self Referencing
¨ Create connections between tables.
¨ Apply Integrity rules to several tables in a given database.
4. Database
3
¨ Definition
¤ Database is a shared, integrated computer structure that houses
the collection of:
n End User Data : users’ data
n Metadata: description about data (description about table, attributes
etc.)
¨ Data
¤ Raw facts about, unprocessed facts.
¤ e.g.: Aminah, 0102539937
¨ Description
¤ Store metadata- data about data
¤ Know as System Catalog / data dictionary
¤ e.g.: Name : VARCHAR(10)
5. Database
4
¨ Example of database encounter in daily life:
¤ Airline reservation
¤ Purchasing from supermarket
¤ Using local library
7. Relational Database Model
6
¨ First proposed by Dr. E.F. Codd of IBM Research in 1970
¨ Represent database as a collection of relation.
¨ Informally, each relation looks like a table of values.
¨ Represent database as a collections of relations.
¨ Relational database matches data by using common
characteristics found within the data set.
¨ The resulting groups of data are organized and are much
easier for people to understand.
8. Relational Database Model
7
¨ Basic Structure
¤ Implemented through Relational DBMS (RDBMS)
¤ RDBMS manage the complexity of physical implementation.
¤ Users see database as a collection of tables in which data are
stored.
¤ Tables are also known as Relation.
¤ Tables contains Attributes.
¤ Attributes are a set of characteristics of the table.
¤ Tables are related to each other through some shared attributes.
¤ The relationship type is shown in Relational Schema.
11. Entity
10
¨ Things or object in real world with independent
existence.
¨ An entity may be object with:
¤ physical existence : person, car, house, employed, etc.
¤ conceptual existence : job, course, event.
12. Attribute
11
¨ Attribute (Field)
¤ Each entity has certain characteristics known as
attributes.
¤ Named column of relation.
¤ Example : an EMPLOYEE entity maybe describe by
employee's name, age, address, salary and job.
¤ Used to hold information about the objects to be
represented in database.
13. Simple & Composite Attributes
12
¨ Simple Attributes
¤ Attribute that cannot be further divided
¤ Simple (Atomic) attributes.
n Age, City, Postal Code
¨ Composite Attributes
¤ Comprise of more than one attributes.
n Can be divided into smaller subparts, which represent more
basic attributes with independent meaning.
n Address consist of streetNumber, postalCode, city
14. Single valued & Multivalued Attributes
13
¨ Single Valued Attributes
¤ Can only have one value for the particular entity.
¤ Eg: A student can have only one IC number
¨ Multivalued Attributes
¤ Attributes that can have many values.
¤ Eg: A student can have many certificate such as
PMR, SPM, MLVK, etc.
15. Stored & Derived Attributes
14
¨ Stored Attributes
¤ The date_of_birth is the stored attribute.
¨ Derived attributes
¤ Can be computed from other attributes
¤ Example: age is derived from date_of_birth.
¤ Age is called derived attribute,
16. Null values
15
¨ In some cases, particular entity may not have an
applicable value for an attribute.
¨ Two cases:
1. The attribute value is missing.
n E.g.: Height attribute is NULL.
2. It is not known whether the attribute value exist.
n College degree – some people may have it and some not.
¨ Therefore, NULL value has to be created
17. Domain
16
¨ Set of possible values for an attribute.
¨ Each simple attribute of entity is associated with
value set (domain of values)
¨ It specify the sets value that may be assigned to
that attribute for each individual entity.
¨ Example given an attribute named GENDER, the
domains are MALE and FEMALE.
¨ Formally written as: GENDER = {MALE, FEMALE}
18. Degree
17
¨ Degree
¤ The degree of relation is the number of attributes it
contains.
¤ For example, Student has four attributes, or degree
four.
20. Cardinality
19
¨ Cardinality
¤ The number of tuples(rows) its contains.
¤ If Branch relation have 5 number of tuples, the
cardinality of Branch relation is 5.
¤ Change as the number of tuples is added or deleted.
22. Relational Scheme
22
¨ Named relation defined by a set of attribute and
domain name pairs.
¨ Common convention:
¤ RelationName (attribute_1, attribute_2,…..,
attribute_n)
¨ Example:
¤ Branch (branchNo, street, city, postcode)
23. Characteristics of Relation Scheme
23
¨ What is Relation Schema?
¤ A named of a relation defined by a set of attributes
and domain name pairs.
¨ Relation name
¤ Relation name is distinct from all other relation names in
relational schema.
¤ Cannot have two Student relation in the database.
24. Characteristics of relation scheme
24
¨ Attribute name
¤ Each attribute has a distinct name.
¤ Order of attributes has no significance.
¤ Order of tuples has no significance, theoretically.
¨ Domains
¤ Values of an attribute are all from the same domain.
26. Relational Database schema
26
¨ A sets of relation schema.
¨ The example shows the database schema for COMPANY =
{EMPLOYEE, DEPARTMENT, DEPENDENT, PROJECT}
Relation
Schema
DB
Schema
27. Relational Database schema
27
¨ The relation schema normally represented as
follows:
¨ The primary key is underlined.
EMPLOYEE { SSN, FNAME, LNAME, MINIT, BDATE, ADDRESS, SEX,
SALARY, SUPERSSN,DNO }
DEPARTMENT { DNUM, DNAME, MGRSSN, MGRSTTDATE }
28. Relation instance
28
¨ A tuple at a specific moment of time
¨ Eg: Branch (BranchNo, Street, City, PostalCode )
¨ The relation instance for branch is:
¤ (B005, 55 Jln Dobi, Johor Bahru, 80100)
¤ (B006, 55 Jalan Perai, Johor Bahru, 80000)
¨ The relation instance change when tuple is updated,
deleted or inserted.
30. Relation Keys
30
¨ Refers to the important attribute in an entity.
¨ Determine the uniqueness of an row in given table.
¨ Identifiers for each rows.
¨ An attribute or more than one attributes can be
declared as keys depending on situations.
¨ Types of keys:
¤ Primary Key
¤ Candidate Key
¤ Alternate Key
¤ Foreign key
31. Primary Key
31
¨ Is an attributes that uniquely identify each rows.
¨ Each table must have primary key.
¨ Cannot be NULL value to maintain Entity Integrity.
¨ Primary key is the one that officially declared as the
row identifier inside a specific table.
¨ Candidate keys for table Student:
¨ Eg: studentID for Table Students
32. Candidate key
32
¨ A candidate key is a single field or the least combination of
fields that uniquely identifies each record in the table.
¨ There can be more than one candidate keys in a relation.
¨ Criteria for the candidate keys:
¤ It must contain unique values
¤ It must not contain null values
¤ It contains the minimum number of fields to ensure uniqueness
¤ It must uniquely identify each record in the table
34. Candidate key
34
¨ However, the instance of relation cannot be used to
proved attributes or combination of attributes is a
candidate key.
¨ What happen if another person has name James
McCloud as the first and last name?
¨ Identifying the candidate keys require that we know
“the real world” meaning of the attribute involved.
35. Alternate key
¨ An alternate key is any candidate key that is not
primary key.
¨ Alternate keys are sometimes referred as
secondary keys.
36. Foreign Key
35
¨ Attribute is an attributes whose value match the primary
key values in related tables.
¨ Creates a relationship between relations
37. Example
36
¨ Branch (branchNo, street, city, postCode)
¨ Staff (staffNo, fName, lName, position, sex, DOB, salary,
branchNo)
¨ FK à branchNo references Branch (branchNo)
39. Group discussion
38
DriverID dFName dLName
D456 Jane Watt
D666 Karen Black
D957 Steven Smith
D344 Tom Jones
ClientID FName cEmail cAddress
C3034 Anne Way 111 Storie Road
C089 Mark Fields 120 Lady Jane
C019 Anne Brown 13 Renfrew Road
C039 Karen Ways 34 High Street
DriverID ClientID pickupDate
D456 C3034 2/1/10
D456 C089 2/1/10
D666 C3034 2/1/10
D344 C039 2/1/10
For each table, find:
1. Two candidate keys
2. Primary Key
3. Foreign Key
40. Integrity rules
39
¨ To have a good design, a database must have
integrity rules.
¨ Constraint or restriction that apply to all instances of
the database.
¨ Integrity rules consists of:
¤ Entity Integrity
¤ Referential Integrity
41. Entity integrity
40
¨ Requirement
¤ All Primary Key entries are unique, and no part of a primary
key may be NULL.
¨ Purpose
¤ Guarantee that each entity will have a unique identity and
ensures that for each key value can properly refer primary
key values.
¨ Examples:
¤ INVOICE, no invoice can have a duplicate number, nor can it
be NULL.
¤ All invoices are UNIQUELY identified by their invoice
number.
42. Referential integrity
41
¨ Requirement
¤ A Foreign Key may have either a NULL entry, as long as it is not a part
of its table’s primary key or an entry that matches the primary key
value in a table to which is related. (Every non-null foreign key value
must reference an existing primary key value)
¨ Purpose
¤ Makes it possible for an attribute NOT to have a corresponding value,
but will be impossible to have an invalid entry.
¤ The enforcement of the referential integrity rules makes it impossible to
delete a row in one table whose primary keys has mandatory matching
foreign key values on another table.
¨ Examples:
¤ A customer might not (yet) have an assigned customer sales
representative (CSR) number, but it will be impossible to have an invalid
CSR number.
43. Example
42
¤ Branch and Staff Relation.
¤ It is not possible to create staff record with branchNo
B025, unless there is already record for branch B025
in Branch relation.
¤ However, we should be able to create new staff
record with NULL branch number to allow the situation
where a new member staff has joined the company but
has not yet assigned to a particular Branch.
45. Relational Model Relationship
44
¨ An association between entities.
¨ Entities that participate in the relationship are
called participants.
¨ Specifies how many instances of an entity relate to
one instance of another entity.
¨ Types:
¤ One to Many (1:M) Relationship
¤ Many to Many (M:N) Relationship
¤ Self Referencing Relationship
46. One to many (1:M)
45
¨ Table A may have many linked records in Table B
¨ But each record in Table B may have only one
corresponding record in Table A.
47. One to many (1:M)
46
¨ Example:
¤ A database in company keep track the information
about the employee and their dependent. Each
employee can have one or more dependent and each
dependent belongs to one employee only.
48. Many to many (m:N)
47
¨ Table A may have many linked records in Table B
¨ Table B may have only many record corresponding
record in Table A.
¨ M: N relationship is not a good choice in database.
¨ Normally when we have M:N relationship, we have
to separate into 1:M relationship.
49. Many to many (m:N)
48
¨ Example:
¤ A course can be taken by many students and the
students can take as many courses as they want.
51. Group discussion
50
A company has several departments. Each department
has a supervisor and at least one employee. Employees
must be assigned to at least one department. Projects will
be given to the employee and it will be done in a group.
At least one employee is assigned to one project or more.
The important data files are the names of the
departments, projects, supervisors and employees, as well
as the supervisor and employee number, department
code and unique project number.
¨ Identify the entity.
¨ Identify the relationship.