MSc Database Coursework 2_2024 (1)
MSc Database Coursework 2_2024 (1)
Learning outcomes: The coursework meets the following module learning outcome:
1
Academic Misconduct:
“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.”
Further details about “Student Code of Conduct” and “Disciplinary Regulations” can be found at:
https://www.roehampton.ac.uk/corporate-information/policies/
This requires you remain in the same group for coursework1. Each of team
member may receive same mark for their submission.
Task:
In this coursework you are tasked with implementing the database you designed in
coursework 1. Hence, you are required to use DDL statement to create database along with
the different collections of data that may be required to be stored in your database to
achieve its purpose. The completion of your coursework will be graded by submission of
report and a lab assessment.
This coursework is worth 30% of the module in total. It is split into TWO parts, support file
submission worth 10% of the module and a lab SQL assessment which worth 20% of the
module.
Coursework two including two sections.
2
o Individual reflection from both members:
▪ Student-1 individual reflection (250-300 words)
▪ Student-1 individual reflection (250-300 words)
o Reflection should discuss:
▪ What you have learned from these 2 courseworks.
▪ What challenges you have met during database design and implementation.
NOTE: you can use ‘EmployeeInfo’ schema as example to prepare your SQL code.
Lab assessment will be conducted on week 12, the implemented database will be
examined in this assessment from 3 perspectives (20%):
1. All tables are created properly based on physical data model.
2. Appropriate constraints are set including data types, primary and foreign keys.
3. Meaningful sample data is populated into each table.
The understanding of SQL will be also examined in lab session in the form of (20%):
1. Tutor makes 2 questions for each group member based on the content of your
database.
a. One simple question
b. One complex question
2. You are expected to write SQL solutions to obtain the request results.
3
b. Perform SELECT operations using:
i. Special operators.
ii. Comparison/mathematical operators.
iii. Logical operators.
iv. Aggregation functions.
v. Ordering operations.
vi. Grouping operations.
vii. Joining tables (inner, outer, self, and/or left/right).
viii. Nested queries.
c. Defining database views.
4
Assessment Criteria (Grade Boundaries or Rubric):
Criteria Excellent Satisfactory Not Satisfactory Not Attempted
SQL naming All names are easy to Names follow the Names need work and Names are too
conventions how understand, consistent conventions although some are sometimes short or too
closely is the naming and follow guidelines. could be better. unsuitable. cryptic,
convention for inconsistent, or do
tables, columns, etc. not follow any
followed. convention.
Constraints: All constraints are set Most constraints are Constraints are set, Most of the
How Constrains are properly. e.g. data properly set, but some can but most of them are constraints are not
set for tables and types for column be modified to most unsuitable, need to be set. Like primary
reflect relationships values are properly appropriate settings. modified. key and foreign
between tables. set, primary key and keys are not set.
foreign key are
correctly considered
and
set.
SQL code Quality Code quality follows Code quality needs work. SQL codes used are No SQL code
structures of code, guidelines. simple queries only. provided, or SQL
use of enough code provided is
complex queries very poorly
with formatted.
understanding.
SQL correctness how All queries work Almost all of the queries Some queries do not No output provided
correct is the output correctly. work correctly, or output is work correctly, or from SQL, or
of the SQL. correct almost all the time. output is incorrect. output is incorrect.
SQL execution how Solutions executed Queries executed correctly Some query solutions No SQL solutions
smoothly does the correctly, obtain the although there are some have syntax errors provided, or most
SQL execute – are desired results. syntax errors, desired that mean they do not have syntax errors
there any bugs? results are basically execute properly. causing problems.
obtained.
Submission ability to Correct files submitted Correct files submitted only Correct files submitted Incorrect files
provide a submission only with no issues. but some issues with files but with unwanted submitted.
provided. files provided and
that meets the
possibly issues in files
requirements given. provided.
Presentation ability Correct SQL solution Correct SQL solution No correct SQL No solution is
to show the prepared to question prepared to question by solution prepared given.
independently
independently work discuss with others independently
on SQL / Sudo SQL / Search
solution prepared solution
independently online