Unlock document.
This document is partially blurred.
Unlock all pages and 1 million more documents.
Get Access
DESIGNING
DATABASES
LEARNING OUTCOMES
1. Identify the relational database model’s basic components.
The relational database model stores information in the form of
logically-related two-dimensional tables.
Entities
Attributes
Entity identiers
Constraints
Primary keys
Foreign keys
2. Explain the importance of documenting entity relationship diagrams.
An entity is a person, place, thing, transaction, or event about which
information is stored. A customer is an entity, as is a merchandise item.
Entities are not necessarily tangible, such as an appointment to see the doctor
is an entity. Attributes are characteristics or properties of an entity. For
example, a CUSTOMER entity can be described by have attributes such as a
Customer Number, First Name, Last Name, Street, City, State, Zip Code, Phone
Number, Credit Card No, and Credit Card Exp.
3. Explain the need for an entity-relationship diagram in a database
management system.
An entity-relationship diagram (ERD) is a technique for documenting the
entities and relationships between entities in a database environment.
The Chen model uses rectangles to represent entities, diamonds for
relationships, and lines with arrows to show the type of relationship between
entities.
CORE MATERIAL
The core chapter material is covered in detail in the PowerPoint slides. Each slide
contains detailed teaching notes including exercises, class activities, questions,
and examples. Please review the PowerPoint slides for detailed notes on how to
teach and enhance the core chapter material.
Designing Databases Page 1 of 8
C
APPENDIX
APPLY YOUR KNOWLEDGE
Instructor Note: There are few right or wrong answers in the business world.
There are really only e2cient and ine2cient, and e3ective and ine3ective business
decisions. If there were always right answers businesses would never fail. These
questions were created to challenge your students to apply the materials they
have learned to real business situations. For this reason, the authors cannot
provide you with one version of a correct answer. When grading your students’
answers, be sure to focus on their justication or support for their specic answers.
A good way to grade these questions is to compare your student’s answers against
each other.
1. SportTech Events
Project Purpose: Get students comfortable identifying entities, attributes
and relationships.
Solution:
Make sure students know that POTENTIAL_SPONSOR is an associative
entity. This can be confusing, since a SPONSOR can be a
POTENTIAL_SPONSOR as well. That creates a many-to-many relationship if
POTENTIAL_SPONSOR is not an associative entity.
Suggested ERD:
Sugg
ested Normalization:
Designing Databases Page 2 of 8
2. Course and Student Schedules
Project Purpose: Get students comfortable identifying entities, attributes
and relationships.
Solution:
Make sure that students identify the many-to-many relationship between
STUDENT and SECTION. They will have to create an associative entity
called ENROLL to normalize this.
Suggested ERD:
Designing Databases Page 3 of 8
Suggested Normalization:
3. Foothills Athletics
Designing Databases Page 4 of 8
Project Purpose: Get students comfortable identifying entities, attributes
and relationships.
Solution:
The main business functions to be addressed include the tracking of: 1)
members; 2) memberships; 3) personnel, including those who teach
tness classes as well as those who perform administrative functions; 4)
facilities (rooms) and exercise equipment; and 5) equipment mainte-
nance.
Make sure students identify the many-to-many relationship between
MEMBER and CLASS. They will have to create an associative entity called
ENROLL to normalize this.
Suggested ERD:
Suggested Normalization:
Designing Databases Page 5 of 8
Designing Databases Page 6 of 8
4. Slopeside Ski Rentals
Project Purpose: Get students comfortable identifying entities, attributes
and relationships.
Recommended Solution:
The main business functions to be addressed include the tracking of: 1)
customers, both corporate and individual; 2) wine orders placed by
customers; 3) wine products available for sale; 4) grape harvest
information, including details on variety, quantity, and vineyard source;
and 5) employees of the vineyard.
There are several many-to-many relationships in this exercise.
Suggested ERD:
Suggested Normalization:
Designing Databases Page 7 of 8
Designing Databases Page 8 of 8
