Database Systems Final Project
The goal for the final project will be to build an application that uses a SQL Server database. Grading will reflect mainly the
quality of the database component of your application, and less that of your interface. The application can be a desktop, mobile,
or a web application. You are free to choose the topic of the application, however, you should not reuse code from a project in
another class unless you speak with me about this first and we agree to the terms. I can help you come up with one if you like.
For the project you will be paired up based on your seating arrangement in class. In other words, each round table will consist of
a group. The side tables will be grouped as well. This is a general rule; however, some of you are interested in working together
and possibly in a smaller group. This is fine but I will need your groups worked out by Wednesday 4/11/2018.
The project will be developed in 3 phases that will be graded separately. Requirements for the phases are listed below.
% of project grade Due Date
Phase I: 25% 4/22/2018 by 11:59 pm
For this project, you are free to choose the topic of the application. For the final deliverable, you will be encouraged
to prepare materials that you can post online to highlight your application as part of your portfolio for job and
internship interviews (e.g., a video demo of the application in use).
The requirements for Phase I:
You are to design an ER diagram for your database. Your database must contain at least 5 tables with various
relation types (i.e., 1-to-1, 1-to-many, many-to-many). Your ER diagram must represent the 5 tables and how
they are related. You may have fewer than 5 but you will need to justify this design. For each table you should
expect a single View. You do not need to put this into your ER diagram but will need to implement.
Your application should be able to answer complex queries, including queries that compute some aggregate or
need to combine the information associated with different entity types and relationships.
All communication with the tables are to be conducted via Stored Procedures (i.e., CRUD operations). You are to
list the names and parameters of each of the procedures you will be creating with a short description of what
the procedure is to do and data that you expect to return. Remember, a Stored Procedure is simply a method.
Part of your grade will be based on the difficulty of the database portion of the project.
Your group will submit a single document with the following:
1. What is the goal of your application? Why did you choose this topic?
2. What are the expectations of the application? What will you complete as well as what is out of scope?
3. What challenges will you face in completing this application and what is your plan to deal with them?
4. Who will use this application and why? Describe at least 2 types of users.
5. Include a detailed ER diagram (do NOT hand-draw, use PowerPoint, Word, etc.) for your database with
an explanation of each entity and relationship.
6. List each stored procedure you are planning to create. Include the parameters you are planning to use
and what the stored procedure is expecting to return. NOTE: This does not need to be set in stone – you
will most likely change this list over the next 3 weeks.
Grading Criteria:
DO NOT BE LATE WITH YOUR SUBMISSION! LATE ASSIGNMENT TURN-INS WILL NOT BE GRADED!
Document organization, clarity of the language, formatting style.
Quality of the ER diagram and the accompanying explanation for entities and relationships
Phase II: 35% 4/29/2018 @11:59 pm
The requirements for Phase II:
You will turn in a zip file with the following:
All information included in Phase I’s document with any updates addressed / fixed from my feedback
SQL script. that creates your database, tables, stored procedures, etc. Included in this you need to
include the inserts – SO THAT – If I run your script. I will have a complete starting database. This list
might change by your final turn-in; however, you should be close to full competition. Remember, your
topic doesn’t need to solve everything – just enough to show you are well into a fully built system.
A prototype of your application and instructions on how to use your system. You need to decide on
what technology you will use for the front-end of your system. You can create a website, mobile app, or
desktop application. If you develop a desktop application, you can use Java or .NET. I can provide you
with some sample code to get you started. A mobile or web app can be created using a web service or
you can connect directly to your database – still using Stored Procedures.
Grading Criteria:
Document organization, clarity of the language, formatting style.
Addressed feedback
Your progress
Quality of your SQL statements for manipulating and querying the data / style. / formatting
Quality of the specification
Phase III: 40% Presentation on: In class on 5/9/2018 and Turn-in by: @11:59 pm
Phase III comes in parts:
1. You are to put together a 5 – 10 minute PowerPoint presentation. You should cover the following:
What did you use to record your demo
What the project is and why you picked it
What technology stack did you use
Any “out-of-the-normal” queries you added
Any problems that may have come up during the project and how did you solve them
Etc.
2. Your final project:
a. SQL Script. that creates the full database and populates it with data. Format it like the AP script.
b. An updated and final ER diagram of your system
c. All project code for your system
d. An instruction document explaining how to use the system
3. Each person in the group is to fill out the Canvas Peer Evaluation. List each member of the group (including
yourself) with a brief critique of the member. Included in this should be your opinion of their participation
using the letter grade standard. What I am looking for is an honest picture of each member’s contribution
to the project. This should be a warning to all – do not slack on this project. Keep in mind some of you will
do more than others do – that is okay. Members should help complete the project – not exclude themselves
from doing work.
Grading Criteria:
Quality of the content and organization of the presentation
Quality of PP and delivery
Peer evaluations
Overall impression