Professional Documents
Culture Documents
iTBL 5 - G#3
iTBL 5 - G#3
iTBL 5-B
Given the following data requirements of a CONFERENCE database, draw the initial ER design.
For each conference we want to keep the start date, end date, period, location, name and code that
consists of the name initials plus the year.
Researchers are attending conferences. We want to keep track of the researcher’s info (name and
specialization), affiliation and address. Assume that researchers’ names are unique.
Each paper should have a title, abstract, conference and researcher(s), who authored the paper.
Assume that the titles of papers may not be unique. Also, some conference attendees (potential
researchers) may not have papers yet.
Initial Design:
Department of Computer Science
1411263 Intro. to Database Management Systems
Fall 2021-2022
end-date
start_date
period
name
CONFERENCE
name_initials
location Code
year
address
conferences
RESEARCHERS
name
affiliation info
specialization
Department of Computer Science
1411263 Intro. to Database Management Systems
Fall 2021-2022
conference abstract
title
PAPER
Reserchers
Department of Computer Science
1411263 Intro. to Database Management Systems
Fall 2021-2022
Final Design:
For the cardinality and participation constraints, if not mentioned in the description above, make an
assumption, write it below, and design accordingly.
- We assume that confrences must be attended by researchers and that researchers must
attend confrences.
- Paper is a weak entity, we assume title as partial key and writes as the identifying
relationship.
- Not all researches must write papers but papers must be written by a researcher.
- We assume papers must be published in a conference and that a confrenece must have
papers published in it.
Department of Computer Science
1411263 Intro. to Database Management Systems
Fall 2021-2022