The user will just swipe up, right, left to start off with investing or joining a company in some way
2. Company Data:
The frontend triggers displayCompanies in the backend, requesting company data.
Retrieves the company data from the database and it acts as the information hub, it will also filter out the companies that do not pertain to what industries the user is interested in
3. User Profile Precision:
Users request their profile information from the frontend.
The backend fetches the user profile data, we will use JWT in order to ensure that the user's information is safe.
Users engage with the application, and the frontend conveys actions to the backend.
We need to execute all of user-driven actions like the swiping. It performs operations like storing application and investment data. Depending on the nature of the action (Apply/Invest), it takes charge of updating company data or approving membership requests within the database.
Classes Involved:
ApplicationService Class: Manages application-related stuff, safely sends the user's information and application to the company.
InvestmentService Class: Manages investment-related stuff, so that thee could be a meeting set up and contact so that users can invest in private companies
NotificationService Class: Handles notifications for application and investment statuses, maybe sending to user e-mail
GarbageManagement Class: Error management as well as cleaning out the data, so that there can't just be garbage users signing up and sending garbage requests
5. Notification Management:
The backend handles notifications for application and investment statuses.
tBackend serves as a meticulous manager. For applications, it updates company data in the database and promptly notifies the frontend. In investments, the backend takes charge of approving membership requests, effectuating data updates, and communicating these critical updates to the frontend with finesse.
Classes Involved:
NotificationService Class: Handles notifications for application and investment statuses.
Backend Workflow and UML diagram for Linkr App
1. Initiating User Engagement:
2. Company Data:
displayCompaniesin the backend, requesting company data.3. User Profile Precision:
UserProfile Class: Represents user-specific information.4. User-Driven Actions:
ApplicationService Class: Manages application-related stuff, safely sends the user's information and application to the company.InvestmentService Class: Manages investment-related stuff, so that thee could be a meeting set up and contact so that users can invest in private companiesNotificationService Class: Handles notifications for application and investment statuses, maybe sending to user e-mailGarbageManagement Class: Error management as well as cleaning out the data, so that there can't just be garbage users signing up and sending garbage requests5. Notification Management:
NotificationService Class: Handles notifications for application and investment statuses.