Onedrop

Abstract

1. Introduction

Onedrop is a web based blood bank management system, where user can search blood anonymously, however for requesting blood or for registering into a camp a user need to be authenticated. The main idea is to connect all the blood banks and needy people on a single platform to help each other by saving lives and time.

A user can register on onedrop and request blood as well as register into a camp either as a donor or volunteer. For registering into a camp as a volunteer, the user can select a role of a volunteer as per their interest. For each successful request or transaction the user will receive a email which would be the proof for the same. The main goal was to learn Spring boot and Angular. This project was made to show what we have learned.

2. Objective

Onedrop is a web based blood bank management system.

This project demonstrates how HTML, Angular, Java can be applied to a real-world Full Stack Web Development problem.

3. Key Features / Modules

• Different dashboard for different user. user and admin
• Jwt Interceptor in Angular
• Role base rounting in Angular
• Error handler Interceptor in Angular
• Jwt Implementation in Spring boot
• Spring Security
• Sending email in spring boot

4. Technology Stack

5. System Requirements

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

• A modern web browser
• VS Code or any code editor
• JDK 11 or later
• Maven / Gradle
• IntelliJ IDEA, Eclipse or Android Studio
• Node.js (LTS) and npm
• Git (to clone the repository)

6. Installation & Setup

git clone https://github.com/aps08/onedrop.git
cd onedrop

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 aps08 and published on GitHub under the MIT License. Please follow the license terms and credit the original author when you use or modify this code.