Scribd
Upload
85 views4 pages

NFL E/R Design Problem

The document describes designing an entity-relationship diagram to model objects and relationships in the NFL, including teams, players, games, managers, and contracts. The diagram models teams with names and cities, people as players or managers with SSNs and names, and games with home/visiting teams, dates, and scores. Players have attributes like weight, height, position, and birthdate and can be contracted to teams with salaries. Teams have 24-99 players and 1-3 managers, who can work for up to 4 teams with salaries. The diagram shows these entities and relationships with cardinalities.

Uploaded by

jamespetrou
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
85 views4 pages

NFL E/R Design Problem

The document describes designing an entity-relationship diagram to model objects and relationships in the NFL, including teams, players, games, managers, and contracts. The diagram models teams with names and cities, people as players or managers with SSNs and names, and games with home/visiting teams, dates, and scores. Players have attributes like weight, height, position, and birthdate and can be contracted to teams with salaries. Teams have 24-99 players and 1-3 managers, who can work for up to 4 teams with salaries. The diagram shows these entities and relationships with cardinalities.

Uploaded by

jamespetrou
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 4

NFL E/R Design Problem

Design an Entity-Relationship Diagram that models the following objects and


relationships in the world of football (NFL): teams, players, games,
managers and contracts. Each (NFL-) team has a unique team name, and a
city it plays in. Each person being part of the NFL-world has a unique ssn
and a name. Additionally, for players their weight, height, position and
birth dates are of importance. Players have a contract with at most one
team and receive a salary for their services, and teams have at least 24 and
at most 99 players under contract. Each team has one to three managers;
managers can work for at most 4 teams and receive a salary for each of their
employments. Players cannot be managers. A game involves a home-team
and visiting-team; additionally, the day of the game, and the score of the
game are of importance; teams play each other several times in a season
(not on the same day!). Moreover, for each game played we like to know
which players participated in the game and how many minutes they played.
 
Indicate the cardinalities for each relationship type; assign roles (role names) to
each relationship if there are ambiguities! Use sub-types, if helpful to
express constraints!
Sal empl. (0,4) ssn name
name Manager
(1,3) 
Team Person
city (24,99) 
(0,1)
Home Visit
contr Player birthd

NFL (0,*) (0,*)


Sal (0,*) weight height pos

E/R play played-in.

Problem (1,1)
score
(22,*)
min
Scoring:
1. Play relationship a Set: 3
2. Person/Player/Manager: 3 Game Date
3. Weak Game Entity: 3
4. Played-in: 2
5. Can Only Play once on a day: 1
6. Contract: 3
7. Salary, score, min attribute: 3
Team(name, city) Problem2
Player(ssn, birthd, pos,…)

Person(ssn, name)

Game(home, visit, day, score)

Played_in(home,visit, day, ssn, min)


Sal empl. (0,4) ssn name
name Manager isa
(1,3)
Team Person
isa
city (24,99) (0,1)
Home Visit
contr Player birthd

(0,*) (0,*)
Sal (0,*) weight height pos

Day play played-in.


(0,*)
score
Date (1,1)
min
(22,*)

Scoring:
Game 1. Play relationship a Set: 3
2. Person/Player/Manager: 3
3. Weak Game Entity: 3
Another different Solution! 4. Played-in: 2
5. Can Only Play once on a day: 1
6. Contract: 3
7. Salary, score, min attribute: 3

You might also like