Final Project – ER Diagram,

Normalization, SQL Statements, Data

Marts, Backups
(Group work, 4 students per group maximum)

Due Date:
Please refer to the Instructional Plan for all assessment deadlines.

Description:
The objective of this Project is to provide students with hands-on experience in database design,
normalization, SQL statement creation (procedures, functions) , data mart construction, and backup
procedures using MySQL Workbench.

Task:
• Students will work in groups of 4 to develop a comprehensive database solution for a company.
Check the options below. The assignment is divided into five main tasks: creating an ER Diagram,
performing normalization, writing SQL statements (procedures and functions), developing data
marts, and implementing backup procedures. Final project will be presented in class. Regular
and mandatory Scrum meetings will be held in class with the goal of evaluate students’
engagement, collaboration and progress over the weeks. Important: although this is a group
project, each student will be evaluated individually based on their collaboration, support, and
engagement during the process of development of the project in each task and topic. Check the
rubric for more information.

Scenarios to use to create your Project, all groups should have different scenarios:
o Bike rental database
o Fitness App
o School Grade System
o Hiking Application
o Pharmacy
o Amusement Park Tickets sale
o Music School Registration
o Car Ride Application
1) ER Diagram
• Description: Design an Entity-Relationship (ER) diagram for the scenario of your choice.
• Requirements: Identify and define all entities (at least 5, maximum 8). Determine the attributes
for each entity. Define primary keys for each entity. Establish relationships between entities,
including cardinality and participation constraints.
• Deliverables: ER Diagram in MySQL Workbench (.mwb format and screenshot in your report).

2) Normalization
• Description: Normalize the database to ensure it is free from redundancy and update anomalies.
• Requirements: Convert the ER diagram into excel tables. Ensure all tables are in at least 3rd
Normal Form (3NF).
• Deliverables: Document the normalization process in an Excel file, showing the progression
from 1NF to 3NF.

3) SQL Statements
• Description: Write SQL statements to manipulate and query your database.
• Requirements:
o Create tables (DDL) with appropriate data types and constraints. This step can be done
using the automatic script generate by MySQL Workbench based on the updated ER
diagram.
o Populate all tables (DML) (at least 10 rows in each table).
o Each student is supposed to create and present a procedure or a user function. In order
to create them you have to define 5 goals for your database that you will solve with the
use of procedure or user functions. (e.g. 1st Goal: a function that calculates the total
amount for a given order by summing the product prices multiplied by their quantities).
• Deliverables: SQL script file containing all DML (CREATE tables) and DDL statements (INSERT
statements), including the procedures and user functions.

4) Data Marts

• Description: Develop data marts to support business analytics for your database.
• Requirements: Identify the key metrics and dimensions for analysis for your specific scenario
(e.g., sales by region, customer purchase patterns).
• Design a star schema for the data marts.
• Create the data mart tables and populate them with data from the main database.
• Deliverables:
o ER Diagram of the data marts (make sure to add to your report).
o SQL script for creating and populating the data mart tables using the data from the
original database.
 5) Backups
• Description: Implement a backup to ensure data integrity and availability to all participants in
the group. There should be consistency among the ER presented for your database, the
normalization, and the actual database. No need to create a backup for your Data Marts, only to
your database.
• Requirements:
o Use MySQL Workbench to perform a full backup of the database.
• Deliverables:
o SQL script from MySQL Workbench to performing the backup.

In class evaluations: Scrum Meetings and Final presentation:

• Timeline of the Scrum meetings and deliveries:
Each part of the project will be divided within the group. However, every student is expected to
participate in the process to make sure there is alignment and discussion in each state of the
project.
o Student #1: ER Model diagram
o Student #2: Normalization and DDL scripts
o Student #3: DML scripts & Backup
o Student #4: Data Mart (Model and Scripts)
o All students: Procedure or User function (5 in total, one by each participant of the
group).
• Each part of the project should match with the previous part presented. For example, you can’t
present a database that does not match with the ER Model and Normalization steps.

Week 12: Project Released. Define your database scenario/topic.

Scrum meetings: All students must be present during the meetings and presentations to
get evaluated and get marks for the overall project.
Week 13:
• 1st Scrum meeting: Delivery of the ER diagram and discuss with your professor your 5 goals that
must be achieved by using procedures or user functions (e.g. 1st Goal: a function that calculates
the total amount for a given order by summing the product prices multiplied by their
quantities).
• 2nd Scrum meeting: Delivery of the Normalization
Week 14
• 3rd Scrum meeting: DDL, DML, Backup and Data Mart.
Week 15:
• Final presentation (15 minutes) : Present your topic to class. Execute and explain the
Procedures, Functions and Backup steps.
Submission Guidelines and Presentation:
Group Report: A comprehensive report detailing each task, including ER diagrams, normalization steps,
SQL scripts, data marts, and backup procedures.
Code and Files: All SQL scripts, MySQL Workbench files (ER diagram), and other relevant documents
should be submitted in a zip file.
Presentation: 15 minutes per group. Slides
• Number of files: 2
• Files: “LastName_FirstName_GroupReport.pdf”
“LastName_FirstName_ModelNormalizationCodeFiles.zip”
• Citation Style: APA2 (required)
• PDF file title Page: (10% penalty if you do not include) College Name, Program Code, Course Code,
Course Section, Assignment Title, Student Name, Date
• Font Style:
• Body Size: 11pt
• Font Style: Calibri
• Line Spacing: 1.08pt (Microsoft Default)

Success Criteria:
• This assessment's overall weight can be found on the Instructional Plan (IP) and reflected within
the eConestoga grade book. Any student that discovers a conflict existing between the IP and
grade book shall notify their course faculty member.
• For specific evaluation standards, students shall consult the associated assessment rubric found
in the Rubrics section of eConestoga.
• Failure to submit an assessment by the specified end date, to the correct dropbox, will result in
a grade of zero (0).
• No opportunity will be provided to make up for an unsubmitted deliverable.
• It is the student’s responsibility to ensure that their work has been submitted through
eConestoga, on time, to the correct course and in the correct folder.
• Be aware that Conestoga College’s Academic Offense policy will be enforced.

Resources:
The Writing Services center provides writing support through https://lib.conestogac.on.ca/writing-
services
o Downloadable PDF instructions on making an appointment with Conestoga College’s Writing Services
are located here: https://lib.conestogac.on.ca/ld.php?content_id=35144762
1 Page count does not include cover page, table of content, large format images, 2 For details on APA style referencing you are to visit https://apa.conestogac.on.ca/
reference page(s)
or bibliography