Professional Documents
Culture Documents
Bestari Swimming desires to create a database that will be used to design a custom-built scholarship
application management system. As a database designer, you are assigned to design a data model for
the scholarship application management system.
• The candidate must be under 35 years of age on 1 July 2022 and a college/university student.
• The candidate’s record contains candidate ID, candidate’s last name, and so on.
2. Use a table (see below), identify the entity relationship from the entity identified [2marks]
above, you can make assumptions whenever possible (list only meaningful
associations).
4. Use a table, list down all possible attributes according to the entities above. [1 mark]
Entity Name Attributes Type PK/FK
6. Identify any components that can be transformed into Enhanced ERD (EERD).
8. Transform your ERD into logical design (tables with data), you can use Microsoft [ 2marks]
Access or screen shot from MySQL. Fill in minimum 5 rows of sample data in all
tables that you have designed.
9. Screenshot your group discussion (about 1-2 pages) and attach the screenshots in
the Appendix.
Note: The ERD should include entities, attributes, relationships, connectivity and cardinalities.
There are many ways to design the ERD, as long as it is logical and relevant.
IMPORTANT NOTES:
1. This is a group assignment. Any individual submission will not be entertained.
2. You must follow exactly the instructions specified in this assignment.
3. The assignment constitutes of 15% of the total evaluation in this course.
4. We expect high quality assignment and each of them to be different. Plagiarizers will be
seriously penalized (both original creator and copier). We will consider highly similar
work to be plagiarism.
5. The report must attach with given assignment cover sheets. The sheet must be filled up
properly and signed.
6. The due date of this assignment is on 23rd November 2022 (Wednesday), 2.00 PM
through your group’s eLeap. Late work will be deducted by 2 marks each day, down to
zero mark.
7. The submission format should be in PDF/zip form. Each group only need to send one copy
(use representative). Please name your file Matric1_Matric2_Matric3_Matric4.pdf/zip.
8. Safe guide your work in a reliable storage and make duplicate copies. Excuses like lost file,
no internet access, computer damage and leaked works of whatever, will not be
entertained.
ERD/EERD Rubrics
5 4 3 2 1 0
Notation Diagram uses Diagram uses Diagram uses an Diagram uses an Diagram does not
appropriate an appropriate appropriate crow’s appropriate crow’s use crow’s foot ER
crow’s foot ER crow’s foot ER foot ER notation. foot ER notation. notation or uses a
notation. The notation. The The notation is The notation is notation incorrectly
notation is notation is used correctly for used correctly for for less than 25%
used correctly used correctly 50% elements of the 25% elements of elements.
for all for 75% diagram. the diagram.
elements of elements of the
the diagram. diagram.
Entity Diagram captures Diagram captures Diagram captures Diagram captures
all entity sets (including most entity sets less than 3 of the none of the entity
EERD components) (including some entity sets and no sets nor necessary
necessary for a components of EERD) necessary EERD EERD components for a
database that necessary for a component for a database that
would satisfy the database that database that would satisfy the
initial problem would satisfy the would satisfy the initial problem
statement. initial problem initial problem statement.
statement. statement.
Keys Diagram Diagram Diagram captures Diagram captures Diagram captures Diagram captures
captures all captures 75% 50% attributes, 25% attributes, less than 25% none of the primary
attributes, attributes, primary keys and primary keys and attributes, primary and foreign keys
primary keys primary keys foreign necessary foreign necessary keys and foreign necessary for a
and foreign and foreign for a database that for a database that necessary for a database that
necessary for necessary for a would satisfy the would satisfy the database that would satisfy the
a database database that initial problem initial problem would satisfy the initial problem
that would would satisfy statement. statement. initial problem statement.
satisfy the the initial statement.
initial problem
problem statement.
statement.
Constraints & Diagram Diagram Diagram captures Diagram captures Diagram captures Diagram captures
Cardinality captures all captures 50% of the 25% of the only cardinality or none of the
cardinality 75%cardinality cardinality and cardinality and participation cardinality and
and and participation participation constraints participation
participation participation constraints constraints necessary for a constraints
constraints constraints necessary for a necessary for a database that necessary for a
necessary for necessary for a database that database that would satisfy the database that
a database that database that would satisfy the would satisfy the initial problem would satisfy the
would satisfy the would satisfy the initial problem initial problem statement. initial problem
initial problem initial problem statement. statement. statement.
statement. statement.
Relationship All relationship are More than 50% Less than 50% No relationship name
named. relationship are named. relationship are in the diagram.
named.