Scribd
Upload
6 views2 pages

Tutorial 3 Conceptual Modelling

The document outlines a tutorial for designing an entity-relationship model for the Varsity International Network of Oenology's database application, which manages member and wine information. It details the requirements for identifying entity sets, relationship sets, attributes, keys, and participation constraints, as well as the translation of the entity-relationship diagram into a relational schema with SQL DDL code. Additionally, it references various database system literature for further reading.

Uploaded by

Runjia Chen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views2 pages

Tutorial 3 Conceptual Modelling

The document outlines a tutorial for designing an entity-relationship model for the Varsity International Network of Oenology's database application, which manages member and wine information. It details the requirements for identifying entity sets, relationship sets, attributes, keys, and participation constraints, as well as the translation of the entity-relationship diagram into a relational schema with SQL DDL code. Additionally, it references various database system literature for further reading.

Uploaded by

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

Tutorial: Entity-relationship Modelling

The Varsity International Network of Oenology wishes to computerise the management of the information
about its members as well as to record the information they gather about various wines. Your company, Apasaja
Private Limited, is commissioned by the Varsity International Network of Oenology to design and implement
the relational schema of the database application. The organisation is big enough so that there could be several
members with the same name. A card with a unique number is issued to identify each drinker. The contact
address of each member is also recorded for the mailing of announcements and calls for meetings.
At most once a week, VINO organises a tasting session. At each session, the attending members taste several
bottles. Each member records for each bottle his or her evaluation of the quality (very good, good, average,
mediocre, bad, very bad) of each wine that she or he tastes. The evaluation may dier for the same wine from
one drinker to another. Actual quality and therefore evaluation also varies from one to another bottle of a given
wine. Every bottle that is opened during the tasting session is nished during that session.
Each wine is identied by its name (Parade D'Amour), appellation (Bordeaux) and vintage (1990). Other
information of interest about the wine is the degree of alcohol (11.5), where and by whom it has been bottled
(Mis en Bouteille par Amblard-Larolphie Negociant-Eleveur a Saint Andrede Cubzac (Gironde) - France), the
certication of its appellation if available (Appellation Bordeaux Controlée), and the country it comes from
(produce of France).
Generally, there are or have been several bottles of the same wine in the cellar. For each wine, the bottles in
the wine cellar of VINO are numbered. For instance, the cellar has 20 bottles numbered 1 to 20 of a Semillon
from 1996 named Rumbalara. For documentation purposes VINO may also want to record wines for which it
does not own bottles. The bottles are either available in the cellar or they have been tasted and emptied.
We rst want to design an entity-relationship schema that most correctly and most completely captures the
constraints expressed in the above description of the VINO application.

1. Entity-relationship design.

(a) Identify the entity sets. Justify your choice by quoting the sentences in the text that support it.

(b) Identify the relationship sets and the entity sets that they associate. Justify your choice by quoting
the sentences in the text that support it.

(c) For each entity set and relationship set identify its attributes. Justify your choice by quoting the
sentences in the text that support it.

(d) For each entity set, identify its keys.

(e) For each entity set and each relationship set in which it participates, indicate the minimum and
maximum participation constraints.

(f ) Draw the corresponding entity-relationship diagram with the key and participation constraints. Indi-
cate in English the constraints that cannot be captured, if any.

2. Logical design and SQL DDL code.


(a) Translate your entity-relationship diagram into a relational schema. Give the SQL DDL statements
to create the schema. Declare the necessary integrity constraints. Indicate in English the constraints
that cannot be captured, if any.

References
[1] P. Atzeni, S. Ceri, S. Paraboschi, and R. Torlone. Database Systems - Concepts, Languages and Architectures.
http://dbbook.dia.uniroma3.it. Visited on 29 December 2021.

[2] S. Bressan and B. Catania. Introduction to Database Systems. McGraw-Hill Education, 2006.

[3] H. Garcia-Molina, J.D. Ullman, and J. Widom. Database Systems: The Complete Book. Pearson interna-
tional edition. Pearson Prentice Hall, 2009.

[4] R. Ramakrishnan and J. Gehrke. Database Management Systems. McGraw-Hill, 2002.

Page 2

You might also like