Read carefully through the situations described and develop an ERD that would fully address each portion of this situation. You should be able to create the entities, attributes, and relationships with proper cardinalities from reading this scenario. Be sure to include all primary keys (pk) and foreign keys (fk) as well as appropriate data types.

Diagramming Cases

1. Nerd gaming owns a large volume of board games. Each board game is described by a UPC number, name, type, and dimensions;
   1. Dimensions are height, weight, width so that we know how to properly shelf them.
2. A game is developed by a game developer, but the game developer can be unknown in the case of an anonymous developer or a custom game
   1. The developer must have a developer id, name, address, and phone number. We also would like to track a company name, but it is not always a company so that can be null.
3. Only data about the given developers that are in our shop are kept in our database.
4. At any point in time, our games can be on our shelves, at convention, in our storage facility, or on loan for testing.
   1. If the game is on the shelf, we will need to know the shelf number, the row, and the space number (this helps us know where the game is at).
   2. If the game is on convention, we need to know the convention name, the city and state, as well as the organizer in charge.
   3. If it is in our storage facility, we need the facility number, address, temperature, and lock code (the doors are locked so that security is in place).
   4. Finally, if the game is on loan for testing, we need the loan individuals name, their purpose, and the timeline they wish to loan.
5. Keep in mind that a game may end up going through several of these scenarios before it leaves our company. We will need to track this.