0% found this document useful (0 votes)
12 views

Databases Coursework - 1

Uploaded by

Dominic Chuchu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views

Databases Coursework - 1

Uploaded by

Dominic Chuchu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Databases Coursework

The coursework meets the following module learning outcome:

• Practise business database design.

In this coursework you are tasked with creating a database system for the smooth and
efficient operation of a business of your choosing. Hence, you are required to specify
what type of business you will be building your databases system for, along with the
different collections of data that may be required to be stored in your database to
achieve its purpose.

This coursework worth 30% of the whole module.

Note: Please include your program in your submission file name.


e.g if I am a MSc Computing student and my idea is about a University Database, my
submission could be named as:

UniversityDB_Computing.pdf

COURSEWORK ONE

In this section, you are expected to describe an overview of your idea of the DBMS
you want to design and develop, what are the business questions based on what you
will cover in your system, and the purpose of having a DBMS you have proposed. You
will need a good logical relational database management system representation (ERD)
based on your proposed idea. This includes Formal Data Modelling with detailed
features of your system.

Your submission must be a single report (PDF) and should contain:

1. Business system summary based on the chosen topic.


a. Describe what is your business idea in details.

2. An overview of the business environment and your work objectives.


a. In this section, you are expected to explain why your business idea
needs a Relational database management system
b. and what are your work objectives.

3. Explain how your design the database structure to meet the objectives
defined in point 2, and how it will support the business as a working DBMS
4. An ERD (logical schema) of your proposed idea using an appropriate tool (It is
required that you ERD contains at least 7-8 Entities in it).
a. Indicate key attribute for each entity set
b. Indicate cardinality for each relationship
c. Indicate participation for each entity related to each relationship

Example for expected ERD form as follow:

5. A diagram (physical data model) clearly shows:


a. Each table
b. Attributes
c. Constraints including data types and Keys

In the report, if you have used ideas from anywhere other than the lecture notes and
tutorial examples (e.g., from a book, the Internet, or a fellow student) then include a
reference showing where the code or ideas came from and label your code carefully
to show which parts are your and which parts are borrowed.
Marking Scheme
Criteria Excellent Satisfactory Not Not
Satisfactory Attempted
Idea: The idea The idea Idea is simple No idea
the suitability of requires a would require and could be provided or
the idea for a DBMS and a DBMS to managed idea
has been manage without a unsuitable.
DBMS well although the DBMS.
specified. idea is not
fully specified.

Purpose of The DBMS The DBMS The DBMS Purpose of the


DBMS: purpose is purpose is purpose is not DBMS not
clearly clearly defined clearly given, or
how well
defined and although does defined. purpose ill
defined the represents a not clearly defined.
purpose of the good use of represent a
DBMS is. a DBMS. good use for a
DBMS.

Justification: Appropriately The The No justification


Of how the justified that justification justification provided or is
database meets are clearly provided are provided are unsuitable for
suitable for suitable for the not clearly the proposed
the project the DBMS DBMS defined suitable for the system.
objectives and defined. although could DBMS
that also focus be more defined.
on the suitability precise.
of the database
for the business
Entity ERD ERD provided ERD provided No ERD
Relationship provided is is correct has some provided or
Diagram: correct and although is not omissions and ERD is grossly
fully fully complete. incorrect misleading.
The quality of complete for features.
the physical the problem
data model at hand.
provided.
Physical Data Data model Data model Data model No data model
Model: is correct provided is has some provided, or
and fully correct omissions and data model is
The quality of complete for although not incorrect grossly
the physical the problem fully complete. features. misleading.
at hand.
data model
provided.
Submission: Correct files Correct files Correct files Incorrect files
To provide a submitted submitted only submitted but submitted.
submission that only with no but some with unwanted
issues. issues with files provided
meets the files provided. and possibly
requirements issues in files
given. provided.

Academic Misconduct
All submissions will be processed through a code plagiarism tool. If signs of
misconduct are found, all students involved will be contacted to discuss further steps.
Please see here for information on academic integrity at the university
https://portal.roehampton.ac.uk/information/Pages/Academic-Integrity.aspx Our
guiding principle is: Academic integrity and honesty are fundamental to the academic
work you produce at the University of Roehampton. You are expected to complete
coursework which is your own and which is referenced appropriately. The university
has in place measures to detect academic dishonesty in all its forms. If you are found
to be cheating or attempting to gain an unfair advantage over other students in any
way, this is considered academic misconduct and you will be penalised accordingly.

You might also like