Skip to main content

Database Design

Database designs provide the blueprints of how the data is going to be stored in a system. 

Database design is a vital component of any app, and it determines what data to be stored and how the different data elements interact. A proper database affects the overall performance of an application. We're using a Firebase Database for our app. We prefer Firebase over SQLite since this is a multi-user app and FireBase is preferred over SQLite for Multi-User Apps. 

Google Firebase is Google-backed application development software that allows developers to develop Android, IOS, and Web apps. It can be used for user authentication and to host a real-time database. The database design for our app is given below.


The root node of our Database is Users, which branches into two children i.e. Customer and Vendor.
We store all the information corresponding to the customer using the Customer's Mobile Number as the Key, and for vendor, we store all the information using the OutletName as the key. 
Under the Customer subtree, it has three children, namely, Cart, UserData, and the TransactionHistory. 

1) Cart

The Cart will store the list of items in the cart of the customer.  Every child in the cart will have four children, namely
  • Name of the Item
  • Price of the Item
  • URL of the picture 
  • Quantity of the item
We access this node when we want to display the list of items in the cart. When the user placed the order all the items in the cart are deleted. 

2) User_Data

Under this, we store all the information pertaining to the user. This child is common for both Customers and Vendors. Every child in the User Data will have four children, namely
  • Email
  • Password
  • PhoneNumber
  • Username (Name of the Customer / Outlet Name)
We access this node during Login and Registration and also for displaying the Customer Profile.

3) Transaction_History_Customer

Under this we store information regarding all the orders placed by the customer. Every child in this node will have 
  • Amount of the Transaction
  • The outlet from which they purchased
  • Transaction ID
We access this node to display the Transaction History of the Customer

4) Menu

Under this node, we store the menus of the individual outlets. Every child in this node will have 
  • Name of the item
  • Price of the item
  • URL of the item
We access this node to display the menu to the vendor and also to the customer.

5) Transaction_History_Vendor

Under this we store information regarding all the orders received by the outlet. Every child in this node will have 
  • Amount of the Transaction
  • Phone Number of the customer
  • Transaction ID
We access this node to display the Transaction History of the Vendor





Comments

Post a Comment

Popular posts from this blog

App Architecture

App architecture is a consistent plan that needs to be made before the development process starts.  App architecture offers a road map for how the various application components must be set up and connected. It defines how the UI, database and background tasks interact to make the required job possible. We have used MVC(Model View Control) architecture to build our app.  MVC is known for handling multiple views and huge volumes of data effectively. There are three  components in MVC: Model : The model contains data about the application. All the information which must be stored or displayed and access specifications are mentioned here.  model.java serves as our model class. View : View forms the UI part of the app. Views displays model data to the users and allow them to modify the data. The Layouts form the view.  Controller : The controller handles user requests and controls user navigation within the app. It processes user input. The Activities and the Fragme...
Post a Comment
Read more

App Launch Screen

The app splash screen is the brief introductory screen that appears as the app loads after the user has just opened the app. When the application is launched, Main Activity sends an intent to the Splash Activity, which displays the App Logo for 2000 milliseconds, from where the control comes back to the Main Activity.   The MainActivity consists of three options: Login: Users can log in using their Username. The user is directed to the Login Activity for authentication. The User first selects what type of user (i.e., Customer or Vendor) in the Spinner on the Login page. The Username for the customer would be their PhoneNumber, and for the Vendor, it would be their OutletName. Once the user clicks on the Login button, we verify if such an account with the given Username exists in the Database or not. If it doesn't exist, we display a Toast message saying, "No Account found". If the username is valid, then we verify the Passwo...
Post a Comment
Read more