![](https://websites.uta.edu/cseseniordesign/files/2022/08/Screen-Shot-2022-07-08-at-10.20.53-AM-1.png)
Team Name
Team Stark
Timeline
Spring 2022 – Summer 2022
Students
- Saugat Upadhaya
- Bikash Bhattarai
- Anisha Bhattarai
- Prakash Kafle
- Sumiran Thapa
Abstract
Our app is a Liquor Inventory app called LiquorUpp to help everyday stores, collect information on their liquor. The app gives the user the ability to add, remove, sort, see the history of their sales and many other features. The database used to store all this information is called FireBase. This is an online free to use database that holds many features to protect and store the data of users. A bonus feature within the app is the ability to set a notification when an item is running low.
Background
The idea of a mobile inventory phone app was a team idea. We went around stores asking questions to the workers and managers about, “How satisfied are you with your inventory software?”, We received a variety of answers but one problem that we commonly heard was if they had a portable inventory app. That is what inspired the team to make an inventory app that was capable of running on an Android phone. As society advances new ideas and innovations must flow through us to keep us ahead of the competition.
Project Requirements
- Users must log in after signing in.
- Users can create the different categories.
- Users can add a list of items by using a Barcode scanner or manually.
- Users can sort the items by name, price or by category.
- Users can search the desired items by name, price or category.
- Upon selling the items, it will show up in the history tab.
- Pie charts and graphs will be generated based upon sold items.
- Users can set the limit by which they notify users when items run low.
- Added and sold items will be shown with date and time upon the history tab.
- Users can add the picture of an item from their gallery.
System Overview
The app has many components working with one another. Login, a component that handles the safety of the app is the first step into access the inner layer. The user has the ability to create a user name and password to keep their data safe. The database (Firebase) offers features such as account verification to deny anyone who doesn’t have a login. After passing through login, you then inter the Backend component. This gives you the ability to add, edit and remove items and categories. This layers also communicates with the database layer to send and receive data of the correct user. The database layers has features to protected the data of the user by preventing sql injection and encrypting data.
![](https://websites.uta.edu/cseseniordesign/files/2022/08/297997091_806941226980887_1955856499348620192_n.png)
Results
Results text and demo videos go here
Future Work
Implement the feature that the sold item will disappear from the items tab which is showing right now.
Implementing the feature which can recover mistakenly deleted items and graphs will be adjusted accordingly.
Project Files
Project Charter (Link)
System Requirements Specification (link)
Architectural Design Specification (Link)
Detailed Design Specification (Link)
Poster (Link)
GitHub (Link)
Demo Video (Link)
References
Any references go here, properly formatted