Question
Offered Price $24.00

Database System Assignment 1

Question # 00018572
Subject: Computer Science
Due on: 06/29/2014
Posted On: 06/27/2014 11:09 AM
Expert tutors with experiences and qualities
Posted By
maqj
Best Tutors for school students, college students
Questions:
1146
Tutorials:
1060
Feedback Score:

Purchase it
Report this Question as Inappropriate
Question

Read the attached set of user requirements and create an Entity Relationship diagram using UML notation. To receive full credit for this assignment, your diagram must be well organized and include:

  • Each main entity type, labeled with an appropriate name and a designated primary key
  • Attributes of each entity type
  • All relationships between entities, each labeled with an appropriate name
  • Multiplicity constraints clearly identified for each relationship
  • All assumptions made when interpreting the requirements

You may use any software with drawing capabilities (e.g., Microsoft Word, LucidChart, or Visio) to complete this assignment

Below are the criteria that will be used to evaluate the performance of your work on Assignment 1 (Entity Relationship Model). Level 4 indicates that all requirements have been met and that you have demonstrated a strong understanding of the Entity Relationship Model. Level 1 indicates that many requirements are missing or incomplete and that you lack a general understanding of the major concepts. Directly below each requirement and the evaluation criteria is the point value awarded for the performance level. For each requirement, the criteria that most closely matches your work product will be the performance level (and points) awarded. The maximum score for this assignment is 90 points. Late submission of assignments will be assessed a penalty of 10% per day. Assignments more than two days late will not be accepted and will receive 0 points.


Requirement

Level 4

Level 3

Level 2

Level 1

Entities

Every entity is labeled with an appropriate name and a primary key. There are no missing and/or extra entities that are not stated in the requirements.

Every entity is accurately labeled and has a primary key defined. However, there are 1-2 missing and/or extra entities relative to the requirements.

There are several missing and/or extra entities relative to the requirements. Several entities lack a primary key or have been labeled inappropriately.

Most entities, their labels, and primary keys listed in the diagram do not correspond to the requirements.

18 Points

18

16

14

12

Relationships

Every relationship is named. There are no missing or extra relationships that do not fit either the requirements or assumptions made.

There are several missing and/or extra relationships. Several relationships are poorly labeled.

There are many missing and/or extra relationships. Many relationships are poorly labeled.

Most relationships are missing or there are an unusual number of extra relationships.

18 Points

18

16

14

12

Multiplicity (Cardinality and Participation)

Multiplicity is provided for every relationship, on both sides of the relationship.

There is more than one multiplicity that is either missing or wrong. This includes cardinalities that are labeled backwards.

There are many multiplicities that are wrong or missing.

Most multiplicities are missing or do not match requirements.

18 Points

18

16

14

12

Assumptions

All assumptions are clearly stated and implemented. No assumptions conflict with requirements.

Assumptions have been made about the requirements, but not explicitly stated.

Assumptions are stated, but not implemented in the design.

Unnecessary assumptions are made that do not fit the requirements or implementation.

18 Points

18

16

14

12

Clarity of Presentation

The diagram uses UML notation, is easy to read, and the designer’s intent is made clear.

The diagram uses UML notation but is difficult to read due to the poor organization of entities.

UML notation is not correctly used and the diagram is difficult to read.

The diagram is unreadable or illegible.

18 Points

18

16

14

12

Total Points

90

80

70

60

Tutorials for this Question
Available for
$24.00

Database System Assignment 1

Tutorial # 00018023
Posted On: 06/27/2014 11:09 AM
Posted By:
Best Tutors for school students, college students maqj
Expert tutors with experiences and qualities
Questions:
1146
Tutorials:
1060
Feedback Score:
Report this Tutorial as Inappropriate
Tutorial Preview ……
Attachments
BICYCLE_SHARING_SCHEME.docx (46.12 KB)
Preview: Size4TerminalID, xxxxxxxxxxxxxxx Storage xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Dropoff_time&loc, rental xxxxxxxxxxxxxxxxxxxxxxxxxx CostIdentify Relationships: xx this xxxxx xxx aim xx to identify xxxxxxxxxxxxxx that is, xxx connections xxxxxxx xxxxx of xxxxxxxx There are xxxxxxxxx four relationships xx this xxxx xxx users xxxx a membership x member borrows x bicycle xxxxxxx xxxxxxx sponsers xxxxxxxxx and bicycles xxxxxx Transaction records xxx details xx xxxxxxx and xxxxxxxx Multiplicity constraints:One-to-One xxxxxxxxxxxxx In 1-1 xxxxxxxxxxxxx each xxx xx 1 xxxxx links to xxx and only xxx row xx xxxxx table xx Bicycle Sharing xxxxxx there is xxxxxxxxxx relationship xxxxxxx.....
Purchase this Tutorial @ $24.00 *
* - Additional Paypal / Transaction Handling Fee (3.9% of Tutorial price + $0.30) applicable
Loading...