GPI

Abstract

1. Introduction

This is a web application for attendance management system that uses GPS to track the location of users. The system calculates the distance between the user's current location and a predefined location to determine whether the user is within the attendance radius. The application is built using the Haversine formula to calculate the distance between two points on the earth's surface.

Welcome to our GPS-based attendance management system! Our web application allows you to manage attendance using GPS location data, making it easy to track attendance for events, classes, and meetings.

2. Objective

Welcome to our GPS-based attendance management system! Our web application allows you to manage attendance using GPS location data, making it easy to track attendance for events, classes, and meetings.

This project demonstrates how React, Tailwind CSS can be applied to a real-world Full Stack Web Development problem.

3. Key Features / Modules

• Attendance marking using GPS location
• Customizable attendance radius for each location
• Real-time attendance tracking and reporting
• User authentication and authorization
• Dashboard to monitor attendance records

4. Technology Stack

• Front-end: ReactJS, TailwindCSS
• Back-end: Flask, RestAPI
• Cloud: GCP

5. System Requirements

General requirements for this technology stack — check the README for exact versions.

• See the project README for exact requirements
• Git (to clone the repository)

6. Installation & Setup

git clone https://github.com/AKACHI-4/GPI.git
cd GPI

Full setup instructions are in the project README.

7. Future Enhancements

Suggested extensions you can add to make this your own project.

• Add role-based access control
• Deploy on a VPS or cPanel hosting with a custom domain
• Add automated tests and a CI pipeline

8. Viva / Review Questions

Common questions examiners ask for projects in this domain.

1. Explain the frontend, backend and database layers of this application.
2. How is user authentication and authorisation implemented?
3. Describe the main database tables / collections and their relationships.
4. Which REST APIs or routes are exposed and what do they return?
5. How would you deploy this application to production?

9. Source Code & License

This project is developed by AKACHI-4 and published on GitHub under the Mozilla Public License 2.0. Please follow the license terms and credit the original author when you use or modify this code.