CSCE Capstone
Student Site for Individual and Collaborative Activites
Team 4 – ServeSmart
Team Members:
Description:
Many restaurant point-of-sale (POS) systems are inefficient and confusing. We aim to amend this by designing a portable and minimalistic POS software built for tablets, and designed to handle tasks, tables, pending orders, and payment. We intend to implement this with a React Native app so that it can be easily deployed on all target devices.
Our platform will have numerous benefits for establishments that use it. Firstly, servers will be able to complete their tasks quicker and decrease turnaround time. This will increase customer satisfaction and gratuity. The sales data from each working shift will be stored and organized to allow management to analyze their metrics and make calculated business approaches. The end goal is to maximize efficiency and profit for the workforce and management teams in the foodservice industry.
Schedule
| Tasks | Description | Dates |
| First Sprint meeting | Meet together and determine the architecture of our program. Decide how to store, handle, and transfer data between client and server. Assign roles to each team member. | 11/19/2020 |
| Begin work on Sprint 1 | Each member works on their specific tasks for sprint 1. Front end members initialize the Native framework and back end members set up Firebase. |
1/13/2020- 1/20/2020 |
| Sprint 2 meeting | Begin enhancing and building upon database API’s and the user interface. Start to create a logical flow with basic communication through the application’s components. | 1/20/2020 |
| Begin work on Sprint 2 | Each member does their assigned sprint tasks and reflects their progress through the Trello task board. Tasks can be added or removed as necessary. |
1/21/2020- 2/5/2020 |
| Preliminary Testing | Test client server communications. Ensure data is being properly sent through the application. Search for bugs and help each other with road blocks. | 2/6/2020 |
| Sprint 3 meeting | Take results from testing and re-plan the future structure and direction of the app. Argue for implementing new features and removing unnecessary ones. | 2/7/2020 |
| Sprint 3 | Each member does their assigned sprint tasks and reflects their progress through the Trello task board. |
2/8/2020- 2/22/2020 |
| Sprint 4 meeting | Discuss how to connect all different components and continue with working and creating each necessary component. | 2/23/2020 |
| Sprint 4 | Each member continues their respective work and works to the best of their ability, asking and offering help when necessary |
2/24/2020- 3/5/2020 |
| Sprint 5 Metting | Meet and figure out how each team-member is progressing in their development and come up with strategies to help improve development |
3/6/2020 |
| Sprint 5 | Continuing the good development practice of updating trill and committing code after every session to ensure visibility to all team-members |
3/7/2020-3/21/2020 |
| Sprint 6 Meeting |
Lay-out what is necessary to finish for the app’s functionality
|
3/21/2020 |
| Sprint 6 | Start work on the final features needed for our app | 3/22/2020-4/3/2020 |
| Sprint 7 Meeting | Meet and discuss the process of the final features and the realistic outcome our developers can achieve | 4/3/2020 |
| Sprint 7 | Finish remaining features | 4/4/2020-4/15/2020 |
| Clean-up Sprint | Implement final touches on styling and organization. | 4/16/2020-4/20-2020 |
| Testing & Debugging | Run extensive end-to-end tests to ensure functionality. Reach out to restaurants and receive feedback on our app | 4/21/2020-5/1/2020 |
| Documentation | Document our work with a report and a user-manual for the system. | 5/1/2020-Finish |
Contact:
Reddington Walters – rrwalter@email.uark.edu