User Registration Form - Copy this React, Tailwind Component to your project

Public Expense Management System The Expense Management System is designed to help organizations track and manage their expenses efficiently. The system is developed using a Monolithic architecture to ensure scalability, flexibility, and maintainability. The application is divided into multiple services, each responsible for a specific aspect of expense management. Monolithic architecture The system is divided into the following modules: 1. User Module 2. Expense Module 3. Category Module 4. Report Module 5. Notification Module Entities and Their Relationships 1. User Module • User o UserID (Primary Key) o Name o Email o Role (Admin, User) o Password (hashed) Relationships: • Each user can have multiple expenses. • Users can have different roles affecting their permissions within the system. 2. Expense Module • Expense o ExpenseID (Primary Key) o UserID (Foreign Key) o Amount o Date o CategoryID (Foreign Key) o Description Relationships: • Each expense is linked to a user. • Each expense falls under a specific category. Public 3. Category Module • Category o CategoryID (Primary Key) o Name o Description Relationships: • Categories are used to classify expenses. • Categories are predefined and can be managed by admin users. 4. Report Module • Report o ReportID (Primary Key) o UserID (Foreign Key) o Period (Month, Year) o TotalAmount o GeneratedDate Relationships: • Reports are generated for users based on their expenses. 5. Notification Module • Notification o NotificationID (Primary Key) o UserID (Foreign Key) o Message o Date o Status (Read, Unread) Relationships: • Notifications are sent to users for various events (e.g., expense submission, report generation). Workflow 1. User Registration and Authentication: o Users register via the User Service. o Authentication and Authorization Service handles login and token generation. 2. Expense Management: o Users submit expenses through the Expense Service. o Each expense is categorized using the Category Service. 3. Reporting: o Users can generate reports of their expenses using the Report Service. Public o Reports summarize expenses over a specified period. 4. Notifications: o Users receive notifications for various events via the Notification Service. o Events include expense submissions and report generations. 5. Admin Capabilities: o Admin users can manage categories and oversee user activities. Note: Make sure your project is having implementation of following concepts: 1. Angular/ react as frontend technology 2. Spring rest Backend tecnology 3. Spring Data JPA 4. Swagger 5. Mockito, Junit 6. Jacoco for code coverage 7. Java 8 features 8. Exception Handling, Validation and Logs 9. Push code to git