can i start?

Hello everyone. My name is Tan. Now, my team and I will present to

you about our database project. The topic is WEATHER FORECASTING
SYSTEMS.

This is the outline of the representation.

Now, we are going to the first part, it is INTRODUCTION about my team

and the project. Our team has four members and Bảo Phúc is our
leader, Long , Phúc Dương and me. About the project, this is a software
application with graphical user interface, so it allows users to search
data from an outside source and save data to the database, it also has
some queries to filter data.

The second part is DATABASE AND QUERIES DESIGN. I am going to talk

about the content of each table in our project. The first table is
"LOCATION", it contains some information of cities like name, region,
timezone, country, locationID, elevation, longitude, latitude.
"WEATHER" table contains the information about the weather in a
certain location, it is temperature; day and night weather; date, and
user ID. And, the last one is "USER" table, contains some private
information of the users like phone number, emails, activities and
profile image.

In next slide, it is about SQL diagram and Phúc Leader will explain
clearly to you about this.
The next one is our ER Diagram. We have 3 relationships.
1. The first one between “weather” and “location” are 1 to many
relations because 1 location has many weather records but 1
weather record only belongs to 1 location.

2. The second relationship between the user table and location table
is also a 1 to many relations because 1 user has only 1 location but
1 location has many users.

3. The last relationship is between the "User" table and the

"weather" table. 1 user can find many weather records, 1 weather
record found by many users, so it is many – to – many relation.

We subdivide each part of the diagram to show clearly the keys and
attributes of each table.
In the location table, the primary key is locationID, and the other is the
attribute.
In the weather table, locationID and date is the primary keys, and the
other is the attribute.
In the last table, userID is the primary key, email and phone are
multiple attributes and profile_image is the composite attribute. The
rest of the table is the attributes.

Phúc Dương will continue the representation.

Because in my tasks, Phuc Leader and Long help me complete the task on
time, so I think both of you deserve 5% from me.