Scribd
Upload
190 views5 pages

To Data Modeling: Section 3 Assessment

The document discusses building an entity-relationship data model for managing classroom assignments. It describes two entities - CLASSROOM and COURSE - along with their attributes. CLASSROOM attributes include ID, campus building, room number, capacity, and style. COURSE attributes include ID, name, department, number. However, COURSE has a multi-valued attribute for learning objectives, as there can be multiple objectives per course. The task is to draw the two entities and their attributes using entity-relationship notation, including designating the multi-valued attribute for COURSE.

Uploaded by

rina mahure
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
190 views5 pages

To Data Modeling: Section 3 Assessment

The document discusses building an entity-relationship data model for managing classroom assignments. It describes two entities - CLASSROOM and COURSE - along with their attributes. CLASSROOM attributes include ID, campus building, room number, capacity, and style. COURSE attributes include ID, name, department, number. However, COURSE has a multi-valued attribute for learning objectives, as there can be multiple objectives per course. The task is to draw the two entities and their attributes using entity-relationship notation, including designating the multi-valued attribute for COURSE.

Uploaded by

rina mahure
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/ 5

Introduction

to Data
Modeling
Section 3 Assessment
The Scenario (1)
You work as a business analyst for a university, and you
are asked to begin building an entity-relationship data
model to help manage classroom assignments for
courses.

The first two “objects” that you decide to work on are


CLASSROOM and COURSE. From your experience with
data modeling, you know that both of these objects
should be represented as entities.

But then what?


The Scenario (2)
You meet with several business users and start
collecting requirements for the attributes that need to be
part of your data model. You come up with the following
lists:
For CLASSROOM: For COURSE:
•  A classroom ID •  A course ID
•  The campus building •  The course name
•  The room number •  The department
•  The capacity of the room •  The course number
•  The classroom style (e.g., •  One or more standard
theater-style; work tables; course learning
rows of desks; etc.) objectives
The Scenario (3)
You begin to work on your data model for these two
entities and their respective attributes.

You do find one complication as you proceed, though.


Whereas each CLASSROOM has only one possible
classroom style (theater-style, work tables, etc.) you
discover that for any given COURSE, there actually could
be – and usually are – more than one learning objective.
Your assignment
Draw the two entities CLASSROOM and COURSE and
their respective attributes using “classic” entity-
relationship notation.

For now, you aren’t going to worry about the


“cardinality” of the relationship between the two; just
focus on designating a relationship, but you do decide to
use “dual naming” for the relationship.

One of the two entities will have a multi-valued attribute


(MVA). Designate which one and use the correct
“classic” entity-relationship notation for an MVA.

You might also like