Scribd
Upload
5 views

Assignment assistance_DBI202_thuyenPTL_Spring24

The document outlines a project assignment for students to design a relational database based on a chosen business. It includes multiple labs focusing on problem presentation, system description, entity attributes, functional dependencies, ER modeling, SQL queries, and data constraints. The final submission requires a comprehensive project report and SQL file detailing the implementation and outcomes of the project.

Uploaded by

hieulnqe180109
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views

Assignment assistance_DBI202_thuyenPTL_Spring24

The document outlines a project assignment for students to design a relational database based on a chosen business. It includes multiple labs focusing on problem presentation, system description, entity attributes, functional dependencies, ER modeling, SQL queries, and data constraints. The final submission requires a comprehensive project report and SQL file detailing the implementation and outcomes of the project.

Uploaded by

hieulnqe180109
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Students choose a business, which can be based on data and information from a certain

(small) website. Students must ensure the following contents:

Lab1

I. Presentation of the problem  The problem to be solved

II. Description of the system's business each business

Lab2

III. With each entity

- Define a set of attributes

- Determine the set of functional dependencies

- Determine the primary key of the relation

Lab3

Using relational algebra expression to answer queries of project (Each group will have 6
queries)

Lab4

IV. Draw the model ER model of the above system

Draw the correct symbol

V. Draw the Relational Model (moving from ER model) and normalize data to 3NF.

VI. Data requirements specification (data dictionary)

Example:

Data Element Description Composition or Data Type Length Values

delivery where and to whom a meal is to patron name


instruction be delivered, if it isn't being
picked up in the cafeteria +patron phone number

+meal date
+delivery location

+delivery time window

delivery building and room to which an alphanumeric 50 hyphens and


location ordered meal is to be delivered commas
permitted

delivery time beginning time of a 15-minute time hh:mm local time; hh =


window range on the meal date during 0-23 inclusive;
which an ordered meal is to be mm = 00, 15,
delivered; 30, or 45

Lab5

VII. List of data constraint

VII. Physical settings

1.Create a table with constraints, insert data. Install Index if available.

2. Queries with corresponding SQL answers

3. Create table view

Query request: Instructors will send query requests appropriate to the project (8 -10 requests
for each group)

Assignment

VII. Physical settings (cont)

4.Triggers for setting complex constraints

5 .Procedures and Functions to solve business

6 . save File srcipt.sql with group_name

VIII.Conclusion
- Comment on the group's project if implemented

- How much has the team implemented in the entire project?

- What the group achieves, what it does not achieve

- If the implementation continues, what will the group do?

Submit the entire project text file (.doc or .pdf) and .sql file

==============================THE END============================

Tips: Example for I.

Sample 1:

Introduction of an Online Hotel Management System doesn’t have to sit and manage the entire activities on
paper. And at the same time, the Owner of the Hotel will feel comfortable keeping a check on the hotel easily
from anywhere around the world.
It provides room booking, staff management, and bill generation features. The system will be simple and
attractive which will make the customer comfortable to use and choose their ideal room. The system allows the
Owner to check the Progress of the hotel from interactive Graphs and he will be notified of each new change
made in the System.
The system allows the manager to keep track of available rooms in the system and even maintain staff details like
their hours worked and salary. Customers can view and book an available room online and the system will
automatically generate the bill according to the number of days the type of room is booked.
....

You can demonstrate the functions of what the end users of your system do in it

Sample 2:

Requirements of the Company (oversimplified for illustrative purposes)


 The company is organized into DEPARTMENTs. Each department has a name, number and an employee who
manages the department. We keep track of the start date of the department manager.
 Each department controls a number of PROJECTs. Each project has a name, number and is located at a single
location.
 We store each EMPLOYEE’s social security number, address, salary, sex, and birthdate. Each employee works
for one department but may work on several projects. We keep track of the number of hours per week that an
employee currently works on each project. We also keep track of the direct supervisor of each employee.
 Each employee may have a number of DEPENDENTs. For each dependent, we keep track of their name, sex,
birthdate, and relationship to employee.
…………….

You can demonstrate the functions of what the end users of your system do in it

How to design your relational database, step by step


Step 1: Define your purpose and objectives
Before beginning your database design journey, understand why you’re making it.
Step 2: Analyze data requirements
Before you design your database, you’ll need to identify what kind of data is most important to that
work.
You can do this by closely examining existing processes and by interviewing team members—both
management and end users. Some questions to ask as you conduct your research:
How are your team members currently using data? Talk to team members—both management and end
users—to identify their current data use patterns and case studies, as well as any gaps in the current
system. You can ask questions like, “What types of data are you currently using?” which will give you
insight into the type of relational database model that would be the best fit.
Step 3: Create a list of entities and a list of attributes
The next steps are to extract a list of entities and a list of attributes from the research you’ve compiled.
In the context of relational databases, an entity is an object, person, place, event, or idea—like
“clients,” “products,” “projects,” or “sales reps.” These entities will eventually turn into your tables
later on in the design process.
For example, if you were developing a talent database for a big record label, your entities list might
look something like this:
Artist, Agent, Venue, Gigs
Next, create a separate list containing the relevant attributes for each of the entities you’ve identified.
Attributes are the defining characteristics of those entities, like “name,” “quantity,” “address,” “phone
number,” or “genre.” These attributes will become the fields for your tables.
Think of entities as nouns, and attributes as the adjectives that describe those nouns. Again, for the
talent database example, your attributes list might look something like this:
Artist Name
Agent Name
Agent Phone Number
Agent Email Address
Venue Name
Venue Address
Gig Dates
If multiple attributes have different names but actually represent the same concept, consolidate them
into one. For example, if you have both “Product No.” and “Product Number” on your list, you should
remove one of them.
If multiple attributes have similar names but actually represent different concepts, rename the attributes
to be more specific. For example, you could rename two different “Name” attributes into the more
specific “Artist Name” and “Venue Name.”
After refining your lists, it’s a good idea to review them with the team members you interviewed to
confirm that you’ve accounted for every necessary type of data.
Step 4: Model the tables and fields
Your list of entities will become separate tables in your base, and the list of attributes will become the
fields for these tables.
Each table’s primary field should meet the following criteria:
- It must contain unique identifiers. This will prevent you from creating duplicate records and
redundancy within a table.
- It cannot contain null values. A null value is the absence of a value, and as such, you cannot use a null
value to identify a record.
- It should not be a value that will need to be modified often.
A poorly designed database makes it difficult to access the information you need and can jeopardize the
accuracy of your data. If you take the time to define your goals, research how your organization collects data,
and identify what you want to store, you can create a structured database that anyone in your org can navigate
and use.

You might also like