Purpose:To gain exposure to relational database by creating a
logical design (documentation of planning, design) and a physical design
(implementation into MS Access) of an approved topic for a database
application.

Description:Work in a group of fourstudents to design a
database application. Your database needs to have at least THREE binary (1:M or
M:N) relationships, but not too many since there will be critical time pressure
to complete the project.

The goal is not to develop a
complete system, but rather to develop a prototype that illustrates the major
features of the system. The parts that are done should be complete and
impressive.

The major requirements of the
project will be a careful and complete Entity Relationship model, the relational
database schema/tables with sample data, a set of interesting SQL
queries, forms for data entry, and reports(with Microsoft
Access).

·Hard copy of the report must be submitted at
the beginning of the class. NO ONLINE SUBMISSION for this milestone is
required.

·Each group must work together to come up with the ERD,
data dictionary and normalization process. However,each individual membermust be responsible for creating at least ONE query
and ONE report. Please make sure to indicate the authorship of each query and
DB report in your logical design.

Create a Relational Database
Logical Design and write a design report that includes:

•
Group Report
Part:

·Cover page showing the name of the DB application and
names of all group members indicating a contact person

·A paragraph or two describing the purpose and
functionalities of this database application

·ERD (Entity Relationship Diagram): must include >=
THREE binary (1:M or M:N) relationships

·DB schema generated from the ERD: you will end up with
THREE or more tables depending on how many relationships you have and whether
you have M:N relationships.

·Data Dictionary (For each table, describe what kind of
information the table is trying to hold, definition for each attribute
including meaning of each attribute, data type, constraints, whether it is a PK
or FK, etc.)

·Normalization: Justification as to how duplication was
avoided

·Show each table with a sample data set (at least THREE
records)

•
Individual Part (must
indicate authorship) including the designof

·At least ONE query expressed in English (Questions
with specific criteria)

·At least ONE report (Output & Summaries)

Questions to get started:

•
What is the
purpose of your database?

•
What are the
unique categories/tables/entities in your DB – what are the things you want to
represent?

•
What are the
relationships between entities?

•
What
fields/attributes does each table have?

•
What are your
primary keys, secondary keys, and foreign keys?

•
What kind of
question do you want to ask to your DB?

•
How do you want
to present the information to the users?