ICT702 Introduction to the Relational Database

Major Assignment

Major Assignment (Individual Assignment) Database

Design and Implementation

Purpose and Learning Outcomes

Purpose
The purpose of the assignment is to provide students with the opportunity to apply knowledge
and skills developed during the semester with reference to:

1. Interpretation of business rules from a case study.

2. Conceptual data modelling through the creation of an Entity Relationship (ER) model.

3. Application of DDL and DML components of SQL to:

a. creates and populates a relational database; and

b. query the created relational database.

Timelines and Expectation

The percentage value of this Assignment is 40% of the course mark.

Due: the due date is on Sunday 5/5/2024 23:59 week 9, Refer to the course outline.
Minimum Time Expectation: 35 hours.
Students are required to complete the assignment individually.
Students are expected to submit the required report and details (see below) to the submission
box in their Moodle shell.

ICT702-Major Assignment Compiled by: Mohamad Naji 23/04/2024

 Assignment Requirements

Overview
Students are expected to develop and provide their own case study and then interpret that to
create an ER Model of the system.
They are then expected to provide a physical implementation of the ER model in the form of
the DDL to create the required tables, attributes, and relationships.
Students are then required to provide the DML to insert sufficient information into the database
to answer a set of queries.
They should also provide proof of the running DDL and DML queries by providing images of
the output obtained.

It is a requirement of this assignment that students use Xampp for the database components.
The submission must be presented in the format of a professional report. Further information is
given in the Detailed Requirements and Marking Criteria sections of this document.

Case Study Requirements

1. Scenario choice: your chosen scenario must include at least Ten to Fifteen entities
that are related to each other. This really can be anything you choose, but you are advised to
choose something you have knowledge of, to make the exercise easier. An example could be a
hobby that you have – perhaps you enjoy a sport, and you wish to develop a database that
models some form of performance related to the teams and games played in this sport. Another
example could be a part-time job you may have, and you may wish to develop a database to
assist some aspect of that business. Another example could be some area of science, perhaps an
engineering-type application that models a power station or a factory or an experiment of some
kind. Because this “brief” is very open-ended, you are recommended to check your chosen
scenario with the teaching staff to make sure it is suitable. A final consideration when thinking
of your scenario is the list of SQL queries that you will need to execute within your database to
prove the creation of tables and insertion of data. For instance, you will need to include certain
search and statistical functions, so your scenario will need to be sophisticated enough to make
these queries possible. PLEASE NOTE: each student is required to develop a UNIQUE
scenario – it will not be permitted for two students to use the same scenario.

ICT702-Major Assignment Compiled by: Mohamad Naji 23/04/2024

 2. Your ER Diagram must include Ten to Fifteen entities. There is no upper bound on
how many entities you choose, but you are advised to include no more than Eighteen. Design
your ER Diagram with all entity names, attribute names, primary and foreign keys,
relationships, cardinality, and participation indicated. You will need to normalise all your
entities, to resolve any many-to-many relationships.
Observe the following restrictions when creating your scenario:

• Include a specialization hierarchy, with super types and overlapping or disjoint sub-
types.
• Include an example of both composite and surrogate primary keys.
• One (or more) of your entities must have a numeric field.
• One (or more) of your entities must contain an alphanumeric (varchar) field.
• One (or more) of your entities must contain a Date field.
• Your attribute names and primary and foreign keys should be indicated as per the
conventions given in the lecture slides (i.e. attributes as proper nouns, primary key
underlined, and foreign keys in italics.
• All many-to-many relationships should be resolved, and you may wish to include a
discussion of normalisation (Functional dependency Diagrams), also including the
normal form that each entity is in and why that is optimal.
• For each entity, you must create some example data for that entity. Include at least 5
rows of data for each entity.
• Data Dictionary needs to be provided before creating the tables and inserting the data.
• Write the SQL statements to create the table structures from your developed ERD. The
structures should contain the attributes specified in your ERD. Use data types that are
appropriate for the data that will need to be stored in each attribute. Enforce primary key
and foreign key constraints as indicated by your ERD. Write the SQL code to insert
your data into the SQL table structures.

Detailed Requirements
• This assignment is an individual assignment. It is a requirement of this assignment that
students use XAMPP or Microsoft SQL for the database components.
• Students should submit a report that follows the format of a business/professional report
and contain, at a minimum, a Title Page, Table of Contents, Executive Summary and
References (if cited) and the following content:

ICT702-Major Assignment Compiled by: Mohamad Naji 23/04/2024

 1. An ER model of the case study system. This should conform to the third normal form.
Students should be aware there are disjoint subtype entities. Students can use any
drawing package to present the ER diagram, but the diagram should use the Crows foot
notation and conform to the standards identified in (Coronel and Morris 2018). These
include that entities are shown in a rectangle with the name of the entity in grey at the
top separated from two columns below with PK, and FK identifiers, where appropriate
in the first column and attributes in the second column. Primary key attributes are to be
separated from other attributes by a line across the rectangle. All entities are to be in
upper case and attribute names are to be in capitalise. All relationships should be
labelled and identified as mandatory or optional. All connectivity, participation and
cardinalities (if there are specific limits) should be shown.

2. A screenshot of the XAMPP showing the creation of a database with the name
ICT702_yourStudentID_Individual_Assignment.

3. The DDL statements are required to implement the conceptual data model above.
Appropriate constraints must be created. Students must follow the same naming
conventions i.e. lower for keywords, uppercase names for tables and attributes with an
underscore between words and a new line for each clause. Students should use the
default schema i.e. there is no need to create one.

.
4. 4. DML statements to insert sufficient (5 rows) data into the database to correctly
display the inserted data in tables.

Submission Requirements

• Students are required to submit a Word or PDF report that includes the following:
- Case study
-Executive Summary and Introduction
-Assumption
-ERD Diagram
-Relation Schema
-Business Rules
-Cardinalities and Connectivity
-Normalisation steps (3NF) that include dependency diagrams for each entity.
-Data Dictionary

ICT702-Major Assignment Compiled by: Mohamad Naji 23/04/2024

 -DDL includes screenshots from Xampp that show the database name (student ID)
-DML includes screenshots from Xampp that show the database name (student ID)
-A Txt file that includes all the SQL code (DDL and DML Commands).

Marking Guide
Requirements Description Max Student
Marks Mark
ERD Section • This should conform to the third normal form. 50
• Must be valid supertype and subtype entities and
hierarchy included.
• Crow's foot notation and conformance to the
standards identified.
• These include that entities are shown in a
rectangle with the name of the entity in grey at the
top separated from two columns below with PK,
and FK identifiers, where appropriate in the first
column and attributes in the second column.
Primary key attributes are to be separated from
other attributes by a line across the rectangle. All
entities are to be in upper case and attribute names
are to be in capitalise case. All relationships
should be labelled and identified as Mandatory or
Optional.
• All connectivity, participation and cardinalities (if
there are specific limits) should be shown.
• All appropriate entities, attributes and
relationships identified.
• Assumption to be included at the beginning of the
report.
• Explain the relation among Entities.
• All cardinalities and participation between
Entities should be explained.
• All the relations of each entity should be
identified.
• Data Dictionary
• Tables with Data for Each Entity
• Normalisation steps

Database • A screenshot of the XAMPP or Microsoft SQL 5

creation showing the creation of a database with the name
image ICT702_yourStudentID_ Individual_Assignment.
DDL • The DDL statements required to create a physical 17.5
Statements implementation of the conceptual data model
ICT702-Major Assignment Compiled by: Mohamad Naji 23/04/2024
 above.
• Students must use XAMPP or Microsoft SQL to
create these tables, attributes, and relationships.
• Transaction and Commit statements should be
included in the DDL.
• All constraints should be included such as (PK,
FK, Null and Not Null)
DML • DML statements to insert (5 rows) data into the 17.5
Statements to database.
Insert Data • Transaction and Commit statements should be
included in the DML.
• A screenshot is provided after inserting the data.
Report • Report is well written using professional 10
Format and language.
Presentation • The report should be very well formatted.
• Reference List if required.
Total Mark 100
Course Mark 40

ICT702-Major Assignment Compiled by: Mohamad Naji 23/04/2024