Database

For our MVP, we decided that the application needed to a sign-in page and Google Map View. For the sign-in page, the user is intended to use their TU email with their name and a password to sign into the app. For the Google Map View, the user needs to be able to view different locations around campus, which will be marked with Google Maps markers. To integrate these features into the app, there needs to be a database, which for the MVP, stores the information that is needed by the Google Maps API and sign-in page.

We used Expo's integration with SQLite to integrate the app with a local database in Expo's FileSystem.

The entities location and person were implemented from our entity relationship diagram here. Both of the entities were implemented in JavaScript classes with an SQLite web database as the main class attribute, which references the local database. The entities included methods for creating, dropping, inserting, and querying the tables.

---

Location

Description:

This class means high-level methods for interacting with the table that represents location entities from our entity relationship diagram.

Attributes:

• DB: SQLite.WebSQLDatabase

  • This is a reference to the local database on Expo's FileSystem.

Methods:

• constructor:

• createLocationTable:

• dropLocationTable

• insertLocationIntoLocationTable:

• async queryAllAttributes:

---

Person

Description:

This class means high-level methods for interacting with the table that represents person entities from our entity relationship diagram.

Attributes:

• DB: SQLite.WebSQLDatabase

  • This is a reference to the local database on Expo's FileSystem.

Methods:

• constructor:

• createPersonTable:

• dropPersonTable

• insertPersonIntoPersonTable:

• async queryAllAttributes: