[1] UFO Sightings around the World

This database is created to catalog and provide statistics on UFO sighting information around the world. It keeps track of each reported incident with lots of information such as witnesses, UFO details, aliens’ encounter, satellite and radar detection, abductions, and analysis on the incidents. User can perform searching for information based on time, location, UFOs’ details, abduction cases, type of witnesses, satellite-detection cases, types of evidence, and analyzed cases.

This is a constraint database using MLPQ/PReSTO tool with the full power of linear constraints.

Business rules UFOs can be detected by people or satellite UFOs might have alien(s) inside Alien(s) might or might not abduct people People can report the incident with description, number of UFOs, and whether

there had been any landing Each incident might or might not have evidences, which could be either

electromagnetic or physical or both Some people analyze the incident to verify and conclude the realness of it.

--------------------------------------------------------------------[2] Specie Migration Tracking System (Web Accessible constraint Database)

Animals that live in habitats that are difficult to survive in year round, must evolve a way to cope with the difficult time of year. A strategy used by many mammals and other species is hibernation. Migration is another option for animals that can move across long distances. They survive by leaving the area for part of the year or part of their life, and move to habitats that are more hospitable. By developing this system, we plan to learn about the different routes that the species in general follow for migration, their breeding, wintering and summering regions and the different types of migration that specie does. This in turn can help us to learn more about the style and reason of migration.

There are lots of different kinds of migration. These terms are used to describe attributes of migration such as timing, direction, the reason for migration, and how many of the species migrate. More than one term can be used to describe one species migration pattern. Some common types of migration are: Seasonal migration, Latitudinal migration, Altitudinal migration, Reproductive migration, Nomadic migration, Removal migration, Complete migration, Partial migration, Irruptive migration.

System Description:

With this system we can track the migration patterns of species. By incorporating the database information of MLPQ software, with the web interface, we have tried to make the system user-friendly. We can generate a model to track the specie movement on the

map by identifying the breeding, summering and wintering regions and the major migration flyways on the map. Due to time limitation we will use the MLPQ library file for the map information.

By noting the different types of migration, we came up with the following entities to develop the database part of this system:

Type_of_migration (ID, Name)Description: ID- Numeric - Unique type of migration ID

Name- String - Name of migration

Specie (ID, Genname, Kingdom, Phylum, Class, Order, Family, Genus, Specie)Description: ID--Numeric- Specie IDGenname- String - The generic name of the specie(Kingdom, Phylum, Class, Order, Family, Genus, Specie) – String-Biological information of the specie

Rf/Map (ID, x, y)

Description:ID- Numeric- RecordID X, y- Region coordinates on map

Migration (ID, SpecieID, TypeofMigrationID, OriginHabitatID, DestHabitatID)

Description:ID- Numeric- specific record ID SpecieID- Numeric- Specie ID TypeofMigrationID- numeric- type of specie ID OriginHabitatID- numeric- region ID of the original habitat of specie DestHabitatID-numeric- region ID of the destination habitat

Breeding (specieID, x, y)Description: SpecieID- numeric- the specie ID

X, y- numeric- the region coordinates on map

Summering (specieID, x, y)Description: SpecieID- numeric- the specie ID

X, y- numeric- the region coordinates on map Flyway(ID, x, y)

Description: ID- Numeric – the flyway ID X,y- numeric- the region coordinates on map

Flywayname (ID, Name)Description:ID-numeric-Flyway ID

Name-string- the flyway name--------------------------------------------------------------------[3] My Airfare Tracking Center

Americans love traveling! Due to the time and the distance constraints, taking flights is the best choice for a trip. Airfare, however, could be very pricy if we do not book and purchase the ticket in the right time. For instance, comparing the air fair in July to April, we have to spend almost double amount of the money taking flights from San Jose to New York City. Hence, picking up a right flight in the right time should be critical to every single traveler. Air-Fair Tracking Center gives people the opportunity to do a smart research for air fair before going on a trip. An individual is able to see the prices within six month referring all the airlines in the database by simply entering the departure dates and the destinations. He or she then can plan the domestic trip to nation wide economically.

Note: The system is designed to Allow a person to track his trip information. List all flight schedules with the airline in the database. User can find different airfare based on different date. Allow a person to compare the price of the airfare, airplane type and on

every airline in a period.

DATABASE

The following are the entities and attributes of the problem statement:

Airport (airport_id, airport_name, x, y)

Airport includes all different domestic airports in the United States. Each airport is assigned a unique id number, name, and corresponding coordinate in this database system. Airport id is the primary key. airport_id: Assigned specific id number of an airport. airport_name: The name of an airport. x: The x-axis of a location within the world map corresponding to an airport. y: The y-axis of a location within the world map corresponding to an airport.

Ticket (ticket_no, flight_no, pid, route_no, issue_date, price_index_no, itinerary_no) Each ticket will have a unique ticket number to be identified.

ticket_no: The assigned number of an issued ticket from an airline by the system. flight_no: A flight number indicates a specific flight schedule in the system. pid: The assigned id of a passenger by the system. route_no: A unique flight track number for each flight trip. issue_date: The date that the ticket has been issued. price_index_no: An assigned index number from price_index_no entity. itinerary_no: An assigned number from itinerary table.

Passenger (pid, lname, fname, date_of_birth) Each traveler has an assigned id number, and his or her name while using the

system. pid: The assigned id of a passenger by the system. lname: The last name of a passenger. fname: The fist name of a passenger date_of_birth: The birthday of the passenger.

Itinerary (Itinerary_no, flight_no, ticket_no, flight_date) Each passenger is required to have a plan including the information about the travel date.

Itinerary_no: An assigned unique number for itinerary. flight_no: A flight number indicates a specific flight schedule in the system. ticket_no: The assigned number of an issued ticket from an airline by the system. flight_date: The flight date of a trip.

Airline(airline_id, name, airplane_id)

Each airline has an assigned airline id number by the system, name, owned airplanes, and rated quality of the service.

airline_id: The assigned id of an airline by the system. name: The name of an airline. airplane_id: The assigned id of an airplane by its airline.quality.

Airfare(route_no, price_index_no, price, fare_effective_date, seat_index_no,

currency_id) Airfare represents the sale of all issued ticket sold by the airlines in the database.

route_no: The assigned unique number for every route. price_index_no: An assigned index number from the price_index_table. price: The price of each issued ticket. fare_effective_date: A effective date that the price will be fixed. seat_index_no: An assigned index number from the price_index_table. currency_id: Different translations have different currency ids.

Airplane(airplane_id, airline_id, airplane_type, capacity)

Each airplane has an assigned id by the system; it also includes the airplane type and capacity.

airplane_id: The assigned id of an airplane by its airline. airline_id: The assigned id of an airline by the system. airplane_type: The type of the airplane. (747/757/767) capacity: The number of the seats in each airplane.

.Flight (fligh t_ no , airplane_id, departure_id, arrival_id, departure_date_no,

arrival_date_no, route_no)

The detail of a flight. The flight schedule includes the flight number, airplane id and the schedule of the flght.

flight_no: A flight number indicates a specific flight schedule in the system. airplane_id: The assigned id of an airplane by its airline. departure_id: The airport id where a flight depart. arrival_id: The airport id where a flight arrive. departure_date_no: The departure date and time issued on the ticket. arrival_date_no: The arrival date and time issued on the ticket. route_no: The number of a flight route.

route (route_no, departure_id, arrival_id, dis) The customary flight track during a flight trip.

route_no: The number of a flight route. departure_id: The airport id where a flight depart. The airport id where a flight arrive.

SeatIndex(seat_index_no, flight_no, flight_date, first_seat_type, business_seat_type,

economy_seat_type) SeatIndex is an entity which shows the number of available seats for each airline in the database.

Seat_index_no: The assigned id of a traveler’s plan by the system. flight_no: An airplane’s assigned number by its airline. Flight_date: An airline’s assigned id number by the system. first_seat: The possible remaining first class seat in a flight. business_seat: The possible remaining business class seat in a flight. economy_seat: The possible remaining economic class seat in a flight.

PriceIndex(price_index_no, flight_no, flight_date, first_price, business_price,

economy_price) PriceIndex is an entity which shows the price lists from airlines referring to a plan.

price_index_no: An assigned index number to identify the different price. flight_no: An airplane’s assigned number by its airline. flight_date: The date of an fight departure. first_price: The estimated first class price in a flight corresponding to a date. business_price: The estimated business class price in a flight corresponding to a

date. economiy_price: The estimated economic class price in a flight corresponding to

a date.

Currency

(route_no, departure_id, arrival_id, currency_id, d_currency, a_currency) Currency is a currency converter for U.S dollars to a variety of currency in the world.

route_no: A route number assigned by the system. departure_id: The airport id where a flight depart. arrival_id: The airport id where a flight arrive. currency_id : A currency id that was assigned to every different route. d_currency: the departure airport currency. a_currency: the arrival airport currency.

DistanceConverter( mile, km)

A distance converter refers to the changing between mile and kilometer. mile: The distance between two airports in miles. km: The distance between two airports in kilometer.

Addition (x, y, z) The function to sum two numbers.

x: y: z:sum

CONSTRAINT DATABASE

NorthAmerica (i, x, y)SouthAmerica (i, x, y)GreenLand (i, x, y)EuropAsia (i, x, y)Africa (i, x, y)Australia (i, x, y)Japan (i, x, y)Taiwan (i, x, y)Route (id, x, y)TimeZone (id, x, y)

--------------------------------------------------------------------[4] VIVA! Bravo Las Vegas Travel Agency

The Bravo Agency uses a web tool called, VIVA, (Vacation Info for Vegas Area), to exclusively search and make reservation on various airlines, rental cars, shows/tours and hotels to offer Las Vegas vacation packages to customers. There are three kinds of users; VIP customers, regular customers and guests.

VIP and regular customers have to register at VIVA. Once they register, they can log in to access to all the features of VIVA. They can search for various hotels, airline, rental cars and theater shows at Las Vegas through VIVA. They can make or cancel reservation. Customers have to pay with credit card when they make reservation. The reservation can be cancelled if airline, hotels, rental cars and theater companies allow it.

VIP customers get first access to new vacation packages before regular customers can. If new vacation package become available, then, VIP customers can get them and reserve them with $50 discount of total cost. Regular customers can become VIP customers pay one-time fee of $100 VIP member set-up fee.

Guests search the vacation packages, but they cannot make reservation unless they register to become regular/VIP customers.

Here are key functions of VIVA1. Make reservation for customers for airline, rental cars, shows/tours and hotels.2. Perform capacity check for airline, rental cars, shows/tours and hotels.3. Cancel reservation4. Create invoice for customers5. Search for available airplane, rental car, hotel, shows/tours within certain price range6. Search for available airplane, rental car, hotel, shows/tours within certain dates7. Search through customer’s travel history to suggest a vacation similar to previous one8. Show airport,hotel and travel routes. (This has been implemented for web browser)

Constraint Model For VIVA (We have total 12 entities with constraints)

1. Hotel constraint: See entity HotelRoomRate2. Rental car constraint: See entity RentalCarRate3. Airplane constraint: see entity Flight4. Tour constraint: see entity TourTicketRate5. Member type constraint: see entity Payment6. Length of Trip constraint: see entity Itinerary7. Map constrains: see entities Airport, Airportmap, Hotel, Hotelmap,

TravelRoute, RouteMap

For example, in the airplane ticket reservationFlight(name, FlightID, basePrice, AirportID, departureAirport, T):-name = "Delta", FlightID = "100", basePrice - T = 100,departureAirport = "SJC",AirportID = "LAS",T>=0, T<=10.

For example, in the hotel room reservationHotelRoomRate(hotelID, roomType, basePrice):-hotelID = "1119",basePrice - 25roomType = 100,roomType <=2.

For example, in the rental car reservationRentalCarRate(carID, baseprice, carType, T):-carID = "904",baseprice = 90, carType = "economy",T>=0, T<=10.

List of all entities and attributes associates with it. Flight(name, FlightID, basePrice, AirportID, departureAirport, T)AirplaneTicket(customerID, customerName, FlightID)Airport(name, city, state, airportID, telephoneNumber,x,y)Airportmap(airportID, x, y)Hotel(hotelID, name, address, telephoneNumber, x,y)Hotelmap(name, x, y)TravelRoute(itineraryID ,x, y)RouteMap(id, x, y)HotelRoomRate(hotelID, roomType, basePrice)HotelRoom(hotelroomID, hotelID, roomNumber, roomType, price, customerID)RentalCarRate(carID, baseprice, carType, T)RentalCar(carModel, carID, telephoneNumber)EconomyCar(carID, price, customerID)StandardCar(carID, price, customerID)Convertible(carID, price, customerID)TourTicketRate(tourID, baseprice, DiscountType, customerID)TouristAttraction(attrationName, tourID, telephoneNumber, basePrice)TravelAgent(name, address, userID, telephoneNumber)Customer(name, address, userID, telephoneNumber, birthDate, discountType, viptype, T)Guest(name, address, userID)Reservation(customerID, itineraryID)Itinerary(itineraryID, flightID, hotelroomID,rentalCarID,tourID, customerID, flightprice, hotelprice, rentalCarprice, tourprice, totalcost, triplength)DepartureCity(name, stateName, x, y)DestinationCity(name, stateName, x, y)Payment(cardNumber, expirationDate, amount, address, customerID, viptype)--------------------------------------------------------------------[5] Trip Planner

Trip Planner gives a simulation for designing and developing a real-time trip planning system which would help you enjoy your vacation right from the start of reserving it all at one place.

The project aims at designing a database, which can help in planning a comfortable trip in the state California. This database contains information

for reserving flights, hotels and rental-cars. It also contains information about various vacation packages offered, attractions in a particular city and any discount offered to the customer. The temporal nature of the MLPQ allows us to see the statistics of the reservation in particular period of time and the status of the flight at particular instance of time.

This database records the information about the cities, airports, customer information, flight schedules, and hotels in a particular city. The database contains few tables showing the various constraints. This database will include all the entity and attributes furnished as below.

This figure shows the California map with cities and flight. Entity Name (Attribute-list)

CaliforniaMap (id, x, y)Shows the map of california with x,y coordinates in space.

Airport (id, airportname, x, y)Airport is the location of airport in a particular city in California in the space time diagram with x,y being the coordinates represented in the map of california.

Customer (cusid, cusname,resid, address,age,milestravelled)This table keeps information about the customer. Each customer has cusid, which uniquely identifies a customerCusname is name of the customerResid is the reservation id of the customer used as a foreign key reference to reservation tableAddress represents the address of the customerAge is the age of the customer

Reservation (reservationid, type, day, month, year, time, status)This table includes information about reservationreservationid is the id tagged to each reservation at a particular instance of time.Type is the reservationtype indicating if it’s a flight/hotel/trip reservation.Day,month,year,time indicates the parameters when the reservation is madeStatus is the booked/cancelled status of the reservation.

Flight (flightid, start-city, destination-city, day, time, seatavail, fare)This table is used to keep information about flight schedule. Based on the day a person wants to leave it will show the schedules of flights and there rates.Flightid is the unique key identifier of a particular flight at a particular route at a particular instance of timeStart-city is the city from which flight will startDestination-city is the destination of the flight.Day are the days on which a particular flight is availableTime is the time at which the flight startsSeatavail shows the availability of seat in a particular flightFare shows the flight rate per reservation.

Hotel (hotelid,name, city, type, rate, roomavail)This table contains information of the hotels in a particular city. The attribute include hotelid which is the unique key identifier of a particular hotel in a particular location, name of the hotel, city in which its located type of hotel shows that whether it’s a 5 star hotel ,7 star hotel or 3 star hotel rates shows the rate associated with the hotel.room availability shows the availability of room in a particular hotel

Payment (cusid,reservationid,type,amount)This table keeps the information about the payment made for the reservations. Cusid and reservationid jointly forms the primary key of the table.Type shows if the payment is going to be made by cash/check/creditcardAmount shows the total amount for reservation.

City (name, x, y)This table contains information about the cities, which would be there in a particular route.The attributes show the name of the city x, y will represent a point where city is located in the State.

Attraction (city, county, x, y)This table is used to store information about major attractions in a particular city. The attributes include the name of the city Name of the county in where the attraction is located.x, y shows its physical location.

trippackage (tpid, city, hotel, totalrate, days) This table keeps the information about the vacation packages. The attributes include the tpid which is the trip packagae id, city which is the location included in the package, name of the hotel which is included in the package,total rate is the total amount for the whole package, days show how many days are included in the package.

Rental Car (name,time-period,class,pickup-location)This table confirms selection of choice of cars, commute period.name is the company name which rents the cartime-period is the period of time the car is rentedclass is the type of vehicle pickup-location is the place from where the vehicle has to be picked up.

Constraint tables:

Aeroplane (id, x, y, t)Shows the trajectory of the aeroplane in the map of california at a particular instance of time t.

Flight-bonus (milestravelled,bonusmiles)This table contains information about bonus miles.This table is used to make decision about the bonus miles offered to the customer, which depends on the miles traveled by the customer.This table presents bonus miles as a linear function of miles travelede.g if miles is greater then 2000 then bonus=.15x where x is the miles traveled.

Cancellation (cancellationid, reservationid, deduction, time, systime)This table stores information about the cancellations.

The attribute reservationid shows the reservation id and cancellationid as the cancellation id.deduction shows the penalized charges of cancellation from the total amount of reservation.Systime is the time at which reservation is cancelled.

Age-discount (age, discount)This table includes the age of the customer and based on the age certain discount is offered to the customer .This table shows discount as a linear function of age.e.g if the age of customer is less than 12 or more than 65 then some discount will be given to him .

cardiscount (age, insuranceamount)This table includes information about insurance.This table presents insurance-amount as the linear function of age.The attributes includes the age of the customer.Insurance-amount is the amount of insurance the customer has to pay. The insurance depends on age If the age of person is less than 25 you have to pay more insurance.

Hoteldiscount (hotelid, discount, month)This table gives information about discount associated with some of the hotel discountsThe attributes include the hotelid for which the discount applies to, discount shows percentage discount associated with the package and the month its offered.

--------------------------------------------------------------------[6] Demographic Survey of Cable Subscribers

The main purpose of this project is to conduct a demographic survey of the various cable subscribers in Bay Area and their subscription trends. This will help infer a preference for the channels in particular and cable service providers in general.

It was found that certain cable service providers operate in only limited areas. The services and options offered also vary from region to region. There were also certain interesting findings about preferences for channels and the types of channels viewed in different areas.

The initial design included only cable services. But, the revised design encompassed also Broadband high speed Internet services that are increasingly being bundled with cable TV services.

TABLE SCHEMA

The revised schema is as follows – (in italics is the revised set of tables)

1. Subscriber (subscriberId, name, address, city, state, zip, areaId)

This table contains information regarding the individual subscribers. The subscribers belong to an “area” based on the location of their residence.

2. Provider (providerId, name, address, city, state, zip)This table contains information regarding the cable service provider.

3. Channel (channelId, name, type)This table contains data about a particular cable channel. The “type” field contains information like – “Digital”, “HD”, “Pay-per-view”, “Regular”

4. Feature (featureId, name, type)This table contains data about optional features that can be added on to Internet services. These include additional storage space, web accelerator service, dynamic connections (free dial-up), static IP address allocation, etc.

5. Plan (planId, providerId, name, cost, type)This table contains information regarding the service plans that the cable service provider offers. A service plan is composed of various channels and/or ISP features. A bundled offering is made available to the subscribers. The “type” field is used to specify if the plan is a channel-based TV plan or a feature-based ISP plan.

6. Area (areaId, name, x, y)The entire space is divided into Areas for administration and service. This table is a list of areas that the cities have been divided into, as determined by the cable service providers. Each area offers a certain number of services. Not all services may be offered in all the areas.

7. PlanArea (planId, areaId)This associates the area with the services that the cable providers offer in that area. It is possible that certain services are unavailable in certain areas.

8. PlanComponent (planId, componentId)This table lists all the components (like channels and/or ISP features that have been bundled together and are being offered as a single plan.

9. Subscription (subscriberId, planId, expirationDate)This table relates the subscriber to the plan he has requested for and the provider of that plan. A subscriber may have multiple plans from different providers. This table also tracks the expiration of the subscription and the special offers that the subscriber may have obtained.

10. PaymentHistory (subscriberId, paymentDate, amountPaid, paymentMethod)This is a table used for accounting purposes. Here, the details about the payments made, the mode of payment and the date the payment was received are noted. The table keeps track of the amount due, which may be carried across payment periods.

11. ServicePerson(personId, name, areaId, providerId, assignmentDate)This table holds the list of all the service persons for a particular area. The service person is associated with the provider he is working for and his services are available only in specified areas. The service person starts offering his services in the area specified starting from the assignmentDate.

--------------------------------------------------------------------[7] Inventory Control Database

Inventory control seems to be one of the most important parts for on-growing businesses. As one business is growing, inventory is eventually growing as well and can get complicated from some cases. Any businesses that have a good control model of inventory can save themselves a lot of money. Inventory applies to many areas, from as little as company’s office supplies to as big as company’s products and customer purchase orders. Also, internal expenses are also very important. For our project #2, we consider to design an inventory database for restaurant that will keep track of item’s quantity, ingredients, amount sold, and more.

In this design, we will limit ourselves to designing database for restaurant item inventory control only and will not consider other interventions such as timesheet or money control. This database allows us to do all kinds of queries to find needed information.

2. Constraint Database Model

2.1 Database Schema and DescriptionAcronymmm := Main Menuit := Itemingr := ingredientpo := purchase order

1). Table: main_menu (mm_id, mm_name)This table is used to store main categories of food such as appetizer, entrée,

dessert, drink, etc...

2). Table: item_menu (it_id, mm_id, item_name, item_price)This table is used to store all saleable item names and prices. Item names are

such as pizza, hot dog, coke, etc…

3). Table: item_description (id, mm_id, it_id, description)This table is used to store description of items since description of certain item

can be changed throughout their life time.

4). Table: ingr_inventory (ing_id, ing_code, parent_id, ing_name, ing_description, yield, conv_id)

This table is used to store all ingredients that are used to make items

5). Table: item_data (id, mm_id, it_id, it_amount, order_num)This table is used to store what items were sold and how many were sold for each

order number

6). ingr_parent_inventory (parent_id, parent_name, location_id)

This table is used to stored main categories of ingredients and its location

7). inventory_department (department_id, department_code, department_name)This table is used to store department information based on main categories of

ingredients

8). inventory_location (location_id, location_name)This table is used to store location where main categories of ingredients are

located

9). inventory_order (order_id, parent_id, vendor_id, invoice_id, order_date, order_qty, order_status)

This table is used to store on-going and history of ordering information

10). inventory_purchase (invoice_id, qty, cost, conv_id)This table is used to store purchased information

11). inventory_receive (invoice_id, qty, cost, conv_id)This table is used to store quantity receiving information

12). vendor_data (id, parent_id, vendor_id, cost, yield, waste, update_date, supply_to_date, first_supply_date, last_supply_date)

This table is used to store information on vendor and its history

13). unit_conversion (conv_id, big_unit, small_unit, bigtosmall_factor)This table is used to store conversion unit

14). vendor (vendor_id, vendor_code, vendor_name, phone, address, city, state, country)This table is used to store vendor information

15). vendor (emp_id, emp_name, ssn, phone, address, city, state, country)This table is used to store employee information

16). time_to_order (vendor_id, order_qty, month, consume)This table is used to determine when to re-order base on how much to order and

the estimated rate of consumption during current period.

17). inventory_remain(vendor_id, order_qty, qty_stock, qty_sold, qty_remain)This table is used to determine how much quantity remains

18). inventory_watcher(vendor_id, order_qty, month)This table is used to estimate how much quantity will remain after certain period

19). inventory_receive_record (recv_id, invoice_id, recv_date, emp_id)This table is used to store receiving information such date and who receive it.

20). ingr_parent_inventory (parent_id, vendor_id, department_id, conv_id, cost, avg_cost, yield, waste, in_stock, on_order)

This table is used to stored main categories of ingredient’s information

--------------------------------------------------------------------[8] MAJOR EARTHQUAKES OVER THE LAST 25 YEARSTeam Prime Entity is interested in creating a database that can track major earthquakes around the world for the past 25 years and show how the economy and population density of a country can affect the amount of deaths caused by an earthquake. The goal of the project is to be able to perform queries on attributes related to earthquakes such as plates, location, magnitude, deaths caused, country, and the date. The output of the queries can be used to analyze the earthquakes and provide useful information.

In our project, a major earthquake is considered to be a 4.0 or higher magnitude earthquake or where the earthquake caused more than a few fatalities. Our database will produce a map of all the continental plates, the countries being tracked, and the locations of where all the earthquakes occurred.

Real information is gathered from the following sources: www.usgs.gov, www.census.gov, and http://pwt.econ.upenn.edu.

RELATIONSOur relations are the following:

epicenter (i, x, y, t): shows the time and location of the epicenter of where an earthquake occurred. Time is in a YYYYMMDD format.

earthquake (eid, magnitude, day, month, year): defines the magnitude of the earthquake, the number of deaths caused by it, and the date it occurred.

effect (eid, cid, deaths): number of deaths caused by an individual earthquake in a country.

plate_region (i, x, y): contains the locations of all the plates around the world. plate (pid, name): names of the plates. country_region (id, x, y): describes the area of a country. country (cid, name, area): names and areas of the countries. population (cid, pop, year): the number of people living in each country for each

year. faultline (i, x, y): faults occur at the border between two plates. economy (cid, gdp, year): the gdp of each country for each year.

TYPES OF QUERIES

Some of the queries that can be performed are as follows:

What country has had the highest death toll from earthquakes?What country has had the highest magnitude earthquake?What country has had the most earthquakes in the last 25 years?

Which plate has had the most recent earthquake occur?Find the total number of deaths caused by earthquakes in the two countries that had the lowest and the highest GDP per capita.Find the total number of deaths caused by earthquakes in the two countries that had the lowest and the highest population density.What was the most active fault line?

--------------------------------------------------------------------[9] Satellite Tracking and Management System

In the information age that we live in today, there are a lot of

data transmissions that are going on that we don’t tend to think

much about.

For instance, all those satellites launched by broadcasting

companies transmitting TV signals to our TV sets at home so we

watch our favorite shows, movies, games etc.

In order to ensure that we get a good signal satellite operators

have to know exactly how many satellites they need to cover a

certain area and their relative positioning at any given time.

As a result of explosion in number of satellites orbiting our planet

there is great need for a good satellite tracking system for

companies to keep track of their satellites at any given time.

There are two major factors that are crucial part of this sort of

tracking system. One of them being the spatial aspect and the

other is the temporal aspect of the satellite.

So we need to keep track of both of these interrelated factors.

We need to identify that what is the location of the satellite at

any given time.

The location can be calculated by using the longitude, latitude,

and amplitude values. As for the time, it has to be relative to the

global timing values.

In addition to tracking location data there is also a need to keep

track of speed at which the satellite travels and does it follows

the projected trajectory.

So that the satellite can be brought back to the projected path

plan if it goes off course.

We also keep a track of the coverage area with respect to each

satellite, specifically the continents and countries it provides

coverage to.

Furthermore, we can keep track of the temperatures, the surface

temperature as well as the internal temperature by using sensors

in the satellite.

In a particular satellite tracking system, there within is a Global

Positioning System (GPS) receiver which has sensors which are

combined with time and location tags, and can provide

previously unattainable information relevant to natural resource

impact assessment and management.

The satellite supplier’s supply different parts of the satellite and

they get their parts from the manufacturers.

When the satellite has to be launched a specific launch site

needs to be selected which is controlled by a base station from

where all the data broadcasting is done to the satellite during the

mission.

Thus, we would like to create a spatial temporal database on the

SATELLITE TRACKING & MANAGEMENT SYSTEM.

--------------------------------------------------------------------[10] MyAirportShuttle

MyAirportShuttle is a database used for tracking shuttles operated by Bay Area Shuttle Inc.

The database stores various details regards the shuttles, passengers, schedules and also reservations.

Bay Area Shuttle charges passengers based on the pick-up location or drop-off location from the airport. The charge is calculated using a constraint database.

The database allows getting the following information

1) Number of passengers traveling on a particular shuttle2) Shuttle Reservation3) Shuttle Status [Assigned, Picked-up, Dropped-off]4) Type of maintenance needed for the vehicles based on mileage5) Which driver will take which shuttle 6) Updates to reservation to make changes to travel plans

Following entities will be used for the above database:

1) Distance (fromLoc, toLoc, dist) The distance entity calculates distance determined by the pick-up and drop-off locations. FromLoc is the pick-up location id and toLoc is the drop-off location id.

2) Location (locId, x, y)

Location entity helps to place a particular pick-up or drop-off location to a city. The attribute city lists a unique city name with an id as “locId” with the coordinates x and y.

3) Shuttle (id, type, make, model)

The Shuttle entity has a particular Id called “id” and “type” of the shuttle lists the type of vehicle(van or car). The make and model describes the vehicle as per the make and year of manufacture.

4) Payment (shtid, schido, resvno, ptype)

This entity keeps track of the mode of payment for every shuttle and every schedule for a reservation.

5) Reservation (resvno, passno, schid, date)

Reservation entity holds the details of a reservation with a unique “reservationNo” and the passenger id under which the reservation is made. The reservation is made for a particular schedule on a particular day specified by date attribute..

6) Cancellation (resvno, date)

This particular entity gives details about a cancellation of a particular reservation based on the reservation number for a given date

7) ShuttleStatus (id, x, y, time, status)

The entity shuttleStatus keeps track of the exact positon of the shuttle at a particular time for a particular shuttle. The status has the values Assigned, Picked_up, Dropped-off.

8) Driver (id, fname, lname, dob, lno) The Driver entity gives the details of the driver like his first name, last name, date of birth and his license number with every tuple having a distinct “id” for driver.

9) Receipt (amount, d, constraint)

Receipt lists the charge for the travel based on distance d.

10) Maintenance (type, desc, m1, m2, constraint) The entity Maintenance is to keep track of the maintenance information of the

shuttles and constraint defines the maintenance type needed for the shuttles based on the mileage of the vehicle.

11) DriverAssignment (did, schid, date)The DriverAssignment entity gives the details as to which driver is assigned to which shuttle with their “id’s” on daily basis.

12) Route (rno, x, y)This entity lists the different routes and the various locations, given by the x and y coordinates, on each route.

13) Mileage (shuttleid, premileage, currmileage)The mileage entity keeps track of the mileage of every vehicle. Premileage is the mileage beginning of the week and the currmileage gives the present mileage.

14) Schedule (scheduleid, shuttleid, starttime, startlocation, endlocation)This entity keeps track of the schedule of all the shuttle. This entity has keys for all the other important entities such as reservation, shuttlestatus, passenger, driver assignment etc. Starttime, Startlocation gives the time and location where the shuttle starts from and the endlocation gives the ending location of the shuttle.

15) Passenger (pid, fname, lname, locid, ph)This entity has the information of the passengers. Each passenger has a unique id and then the first name, last name and the location where they are picked up or dropped of and their contact phone.

16) Update(resvno,pickuptime,schid)The update entity makes updates to the reservation relation. You can update the pickuptime and the schedule for a particular reservation number.

--------------------------------------------------------------------[11] Computing Service Center

The current computing system management at UC Davis has the following concerns:

- Students waste time waiting in line at certain computer labs while there are other labs on campus which are available to them.

- Students have limited knowledge on what applications are provided on machines at different computer labs.

- Students have trouble locating the closest computer lab.- Students need information on their printing quotas to avoid overcharges.- Students need to find out if a room has been reserved at a specific time.

For this project, we will design a constraint database that manages the computer lab information. The application that uses this database will inform the students with the availability, resources, and locations of the computer labs. The students can check for the open hours of the labs and find out when the lab is being reserved. They will be able to access this information either by going online or through an automated phone system. Also, the students can make the decision on which printer to print their documents (if the printer in the current lab is jammed, out of paper, only black and white, etc.). This database will keep track of the location of the computer labs, numbers of computers in each lab, what applications are available at different labs, lab permission, and print page quotas for each student.

Relations that will be used in this database:

Lab(labID, adminID, x, y, capacity, RLevel, scheduleType)This entity keeps track of number of available computers in a lab, the lab location, its restriction level, and the schedule type.

Computer(CID, labID, loginStatus, OS, configVal)This entity tells which computer is being occupied using log-in as a Boolean flag, it also keeps track of the operating system and configuration values for the computer.

PC(CID, labID, loginStatus, OS, processor, configVal)This entity is part of Computer entity, and has an additional information on the types of processors for the PCs.

Unix(CID, labID, loginStatus, OS, shellType, configVal)This entity is part of Computer entity, and has an additional information on the types of shells used in Unix machines.

Mac(CID, labID, loginStatus, OS, configVal)This entity is part of Computer entity.

LabAdmin(adminID, SName, skillLevel)This entity describes someone who maintains a lab.

Printer(printerID, labID, printerType, paperStatus)This entity contains the printer’s ID, its paper status, and the type of printers.

Reservation(CID, SID, day, time)Example constraint: day=mon, 9am<time<10amThis entity keeps track of which has been reserved and what time it is unavailable.

Schedule(scheduleType, day, time, setBy)Example constraint: day=mon, 8am<time<6pm, setBy = adminIDThis entity determines the day and time depending on the input for schedule type.

Application(regKey, appName, configVal, adminID)This entity lists the applications offered. It specifies a configuration value for each of the applications.

Student(SName, SID, ALevel, a, b)This entity describes the student’s name, ID, current location on campus and his/her access level to computer labs.

StudentRecord(recID, SID, deptID, studentLevel)This entity gives information on which department a student belongs to. It contains the student’s ID, record ID, and studentLevel (determined by the student’s year of graduation).

PrintRecord(SID, totalPrinted, lastPrintJob)This entity provides how many pages a student has printed and keeps track of the last print job.

Quota(deptID, printQuotaAllowed, studentLevel)This entity specifies how many pages are allowed to print according to each department policy and student level.

Accessibility(ALevel, RLevel, accessName)This entity determines which lab a student can access depending on the access level of the student and the restriction level of the lab. The constraint is applied to both attributes.

PrintJob(printJobID, CID, SID, pagePrinted, timeStamp)This entity tells how many page is being printed by a student at a specific time. It also keeps track of which computer sent the print job with a timestamp.

Closeness(a, b, x, y, c, d)This entity calculates the distance b/w two point horizontally and vertically. For example, a-x=c, b-y=d

Distance(c, d, e)This entity calculates the sum of c and d. i.e. c+d=e.

** Please Note: AccessLevel has 5 levels:1 = Fresh (freshmen)2 = Other (sophomores, juniors, seniors)3 = OtherSpecial (student with special projects)4 = Grad (graduate students)5 = GradSpecial (graduate students with special projects)

** These 5 levels will convert to 2 Restriction Levels1 = grant to 1-3 access levels2 = grant to 4, 5 access levelsPeople with restriction level 2 can also go to level 1 labs, but people with restriction level 1 can’t go to level 2 labs.

--------------------------------------------------------------------