database UML代写：ICTSAD501 Model Data Objects

数据库代写代考 DB Database SQL

ICTSAD501 Model Data Objects:

Assignment

 

Friendly Fight Club’s Fight Night

 

Friendly Fight Club

Your final project for ICTSAD501 Model Data Objects is to design a database for the Friendly Fight Club’s Fight Night event.  The FFC was founded to bring together mixed martial arts enthusiasts to make friends and have fun while keeping fit.

Fight Night

Fight Night is a monthly event hosted by the Friendly Fight Club. The friendly fights come in three categories; light weight, heavy weight and free-for-all. Light weight and heavy weight fights are most common and only involve fellow club members. Members who are less than 60kg can participate in light weight matches while others can compete in heavy weight class. Free-for-all has no weight restrictions and welcomes to everyone including non-members. The database needs to help us keep track of member status as well as contact information.

Due to several complaints about member freeloading, the club also want to keep a record of who brought their own gear (head gear, sparring gloves, shin guards, gum shields etc.). It may be handy to have some basic item rating system as not all brands are created equal. FFC always asks their members to wear high quality protective gear as they significantly reduce the risk of injury to the user and opponent alike. A list of items and a rating of 1 – 5 will be good.

All fights can be held as either single or tag-team matches. A match can have two or three rounds depending on the outcome of the second round. The system needs to record all matches and who participated the Fight Night. This also involves recording the winner of each round. On completion of the fight event, you need to record the 1st prize winner and runner-up for each category.

Restrictions on the Design

In order to achieve the desired level of flexibility in data collection, the design will be expected to accommodate the following features:

  • Only the member information and members-only fights should be recorded.
  • It is up to you as the designer to decide how many classes should be used.
  • Your design should be optimised to reduce the storage of redundant information.

 

Submission Requirements

To complete the assignment, you must submit each of the following:

  1. A Conceptual UML design of the database showing the attributes of each class and highlighting ALL associations between classes including their multiplicities.
    1. The UML diagram can be drawn up in UMLet, DBDesignerFork, Visio or some other UML design tool but not using the Management Studio Diagram tool.
    2. Multiplicities must be included and can be represented using number or crow’s feet notation.
    3. Save the UML as an image to be included in your final word document (make sure it is still readable)

 

  1. Written Logical Schemas for your design showing:
    1. Each of the required Table Schemas
    2. Any Primary and Candidate Keys using notation PK(xx) and CK(yy)
    3. Any Foreign Keys using notation FK(attr1) -> Table2(attr1)

 

Your designs should be combined into a final word document that includes dot points to justify some of your decisions.  For example, why you may have chosen a particular class and/or relationship over another (eg a 1:many relationship instead of inheritance, or vertical vs horizontal inheritance in the logical design etc). There is a maximum of 2500 words so dot point justifications are acceptable.

Related Posts