Perform conceptual design for the following case. You must turn in an ER diagram developed in VISIO. You may include, in your ER Diagram, specifications that include additional constraints not shown on the diagram. The specifications should be written in English. If you believe that you need to make additional assumptions, clearly state them in the specifications.
The deliverable should be a file named "YourFirstName_YourLastName.vsd". You should submit the file through the moodle assignment submission link.
TIPS:
1. Do NOT begin your VISIO drawing until you have a paper-based "blue-print" sketch of the solution - this will save you lots of frustrating time with VISIO.
2. When working with VISIO, remember to start with the "normal entities" and "normal relationships". If you forget how to do certain things, check out the lab tutorial.
3. The TCI solution file might give you a convenient template for associative pattern and inheritance.
4. The 1-m relationship should always start from the 1 side.
TheNextBigThing (NBT), a gaming company, is planning to build "World of War", a new online multi-player game. You are in charge of developing the back-end database that supports this game.
The game allows gamers to play with each other online. For each gamer, the game needs to store his / her account information including user name, password, email address, first name and last name. User name of a gamer should be unique, while first name and last name do not have to be.
A gamer could create multiple characters to play in the game. Each character should have a name that is unique. The system would also needs to capture the character's current level, experience points, health points (HP), magic points (MP), strength, intelligence, and dexterity. A character could belong to one AND ONLY ONE class. There are three classes: warrior, mage, and ranger.
A character could own items. Each item has a name, an item type, item value, item status (a number between 0 and 100 with 100 representing brand new item and 0 representing completely broken item). There are three types of items: Weapon, Armor and Accessories. For weapons, the system needs to store the weapon type, weapon speed, and damage dealt per second. Weapon damage could be derived from weapon speed and damage dealt per second. For armors, the defense value and armor type needs to be captured. The accessories would have accessory type and special effects.
It is possible for many characters to possess the same item (notice that each "item" refers to items of the same name, for example, short bow. It does not mean the same individual item).
Each character also possesses a set of skills. For each skill, the system needs to record the name of the skill, the MP cost of the skill, levels required for the skill, and a description of the skill. Naturally, multiple characters could have the same skill, and one character could have many skills. Some skills are pre-requisite for other skills.
The system stores information about PvP (player vs. player) results. For each PvP match, it stores the score of each character, and a list of matching history (character X kills character Y at time Z). For this version, only 1 v. 1 match is supported, i.e., the maximum number of players in each PvP match is 2.
The system also allows characters (NOT players) to form guild with each other. The name of the guild, the time it is founded, and its current status will be recorded. The system keeps the list of characters that belong to a guild.