1 / 16

FAMU CMRP Database

FAMU CMRP Database. By: Jabare Mitchell Tyshun Jones Gassie Orr. Purpose of the Database. The purpose of the database is to allow the developers and users to pull out particular sets of information through queries within our application…. To retrieve data.

march
Télécharger la présentation

FAMU CMRP Database

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FAMU CMRPDatabase By: Jabare Mitchell Tyshun JonesGassie Orr

  2. Purpose of the Database • The purpose of the database is to allow the developers and users to pull out particular sets of information through queries within our application…. To retrieve data. • (Essentially this version is a draft version due to the fact secure shell is not the software we will be using to implement our app.)

  3. The Makeup of Our Database • Modeled after our ER diagram • Database contains 16 different tables each with its own set of attributes depending on what they are.

  4. Sixteen Tables • Stud • admin • E_coordinator • Safety official • Parking services • Classes • Class section • Class roll • Location • Events • Alerts • Lot • Building • Room • Users • Instructor The Table highlighted in red will be the ones discussed in detail

  5. Admin • ADMIN_ID • ADMIN_USERNAME • ADMIN_NAME • ADMIN_PASSWORD • NOT NULL CHAR(2) • VARCHAR2(25) • VARCHAR2(50) • VARCHAR2(20) The not null highlighted above shows that Admin_ID is the primary key for this table.

  6. Classes • CLASS_ID CHAR(6) • CLASS_NAME • CLASS_PREREQ • CLASS_CREDITS • NOT NULL CHAR(6) • VARCHAR2(35) • CHAR(7) • NUMBER(1)

  7. Alerts • ALERT_ID • ALERT_DESCR • ALERT_TIME • ALERT_DATE • ALERT_TYPE • ALERT_USERNAME • NOT NULL CHAR(5) • VARCHAR2(150) • DATE • DATE • VARCHAR2(25) • VARCHAR2(25)

  8. Location • LOC_ID • LOC_NAME • COORD_LAT • COORD_LONG • NOT NULL CHAR(5) • VARCHAR2(40) • NUMBER(8,6) • NUMBER(8,6)

  9. Building • BUILD_ID • BUILD_ROOMS • LOC_ID • NOT NULL CHAR(4) • NUMBER(3) • CHAR(5) The Loc_ID attribute is a foreign key coming from the Location table. The Build_ID is still the Primary key

  10. The Purpose of the Sample Queries • The sample queries will give us an Idea on how to find information and also how to design our GUI so that we can ask the same questions in an efficient manner. • Lets us know our database is accurate. We will use the same tables for example purposes .

  11. Admin Queries • Figure out all of the Admin’s Names • Count how many admin’s there are • Search for an admin by there username

  12. Classes Queries • Find a class by its name • Find a class by its ID • Find a classes pre-reqs

  13. Location Queries • Get the coordinates to a building • Find a location by its Loc_ID • Count how many locations there are

  14. Alerts Queries • View alert descriptions • View the time an alert occurred by using its Alert_ID

  15. Building Queries • Find a building using from its name or loc_id

  16. Questions?

More Related