Based off the scenario provided below create an ERD. The Scenario – Treasure Hun

Question

Based off the scenario provided below create an ERD.

The Scenario – Treasure Hunters, an augmented reality online game.
In order to play the game, each player creates their account. They must choose a unique username,
provide their name (first and last names), gender (female, male, other or prefer not to disclose), date of
birth, email and postal address (street number, street name, suburb, city and postcode) and up to three
phone numbers. The date and time of account creation and the player’s total points will also be associated
with their account.
The game revolves around players embarking on quests and hunting for treasure. Multiple players can go
on the same quest and find the same treasure. There are hundreds of quests, new quests are added every
week and some of the more advanced quests can contain up to five mini quests. Each quest needs to be
identifiable using a unique id, and they also have a name. Players initiate quests by finding objects in the
real world, which act as beacons, and each quest is assigned a beacon. Once the player finds a beacon
they will be presented with a story, which provides some background on the quest, and a list of the treasure
they must hunt down in order to finish the quest. The database needs to keep track of each player’s
progress (active, complete, inactive) on each quest.
There are different types of treasure (common, uncommon, rare, ultra-rare and elite). The players are
directed to a webpage where they can obtain various clues to find the treasure (we only wish to store the
web address in our database however, not the clues themselves). Each treasure has one webpage. When
a player finds the treasure, they are awarded points. Each piece of treasure rewards a different amount of
points. When a player unlocks the list of treasures for a quest, they can see a description for each piece.
Players can use their points to purchase badges from virtual stores. All stores have a name, and they are
only open at certain times of the day, so their opening and closing times need to be recorded.
In order to purchase badges from the stores, players can use their points. There are a lot of different
badges that players can purchase. To help players decide what to purchase they will be able to read the
badge names and descriptions. The price of the badges varies depending on demand, and is re-calculated
when a player reaches a store. This means that the price itself is not stored in the database. However,
when a player purchases a badge from a store, the store name, date and time of purchase and the cost of
the purchase need to be recorded, so that they can see a detailed list of their purchases at any time.

I have created the ERD (shown below), however I think it may be incorrect. Any help/tips would be appreciated. The ERD must be in the format shown below.

The diagram needs to show:

• the entity types
• the binary relationship types
• the complex relationship type
• the multiplicity of relationship types
• the attributes (and if applicable their domains) of entity types
• the attributes (and if applicable their domains) of relationship types, and
• the primary key of each entity type

Purchase> Players Badges Userame(PK) Name Badge(ID) Name FirstName Description LastName PhoneNo.[1..3] DOB Email Gender [M, F, O, ND] Address PurchaseDate PurchaseTime Cost StreetNo. StreetName Suburb Stores PostCode TotalPoints SignUpDate SignUpTime StorelD[PK) Name OpenTime CloseTime Treasure TreasurelD(PK! Type Common, Uncommon, Rare, Ultra Rare, Elite] WebpageLink PointsAwarded Description Find 1..n Beacons BeaconlD[PK Quests QuestIDPK! Name Contain> 1..n BeaconID Story TreasurelD Progress[Active, Inactive, Complete] MiniQuests[0..5]

Explanation / Answer

Following are the suggested updates to the diagram created by you:-

1) Purchases should be a relation ( diamond shaped box) with attributes as Purchase Date,Purchase Time and Cost.

2) The multiplicity of Player ------- Purchases association should be 1 rather than 0..n to reflect the fact that 1 Player can purchase 0..n badges.

3) The multiplicity of Player ----- Find relationship will be 1..n instead of 0..n

4) Similarly multiplicity of Find-----Beacon relationship will be 1..n . This will indicate that 1 or more players can find 1 or more beacons.

5) There should be a new relationship between Player ---1..n---------- <Player Quest> ------1---- Quest

The Player Quest relationship will have the attribute "Progress" which can have values {Active, Inactive, Complete}

The Progress attribute should be part of the relationship and not of the Quest entity where it is shown currently.

6) The interconnection between Beacon and Quest should be changed as follows:-

Beacon ---1----<assignedto>------1----Quest

Beacon should also have a story attribute to capture the story associated with the beacon.

7) The interconnection between Quest and Treasure should be as follows:-

Quest --1--------<leadsto>--------1..n-----Treasure

8) Each quest can contain 0..5 miniquests. This can be represented using a self - association as follows:

Quest --1--------------------------------|

| miniquest

|-0..5---------------------------------- |

Related Questions

Navigate

• Browse (All)
• Browse B
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.