Asset Management Web Aplication Development

To develop a web application with objective To create a secure and user-friendly web platform that allows users to store their asset information, nominee details, and submit life declarations at specified intervals to ensure that necessary services are provided to users during their lifetime and allow for the systematic closure of services after their demise. The platform will consist of two portals: User Portal and Admin Portal. Major Functionalities required are automatic image capturing on blink of eye, compiling individual files in to pdf, integration of payment gateway for auto debit for reoccurring payments. integration of SMS, email etc.Technical Requirements:
20) Technology Stack:
20.1) Frontend: React.js
20.2) Backend: Laravel (PHP framework)
20.3) Data Base: PostgreSQL
20.4) API Development: HTTP, REST, and JSON protocols
20.5) Hosting: VPS Hosting
21) API Integration:
21.1) Integration with third-party services for WhatsApp message / SMS, email notifications, and payment gateways (e.g., Stripe, Razorpay).
22) Compliance:
22.1) End-to-End encryption (AES-256) for sensitive data at rest and in transit.
22.2) Role-Based Access Control (RBAC) and Multi-Factor Authentication (MFA) to prevent unauthorized access.
22.3) Adherence to GDPR, PCI DSS, and ISO 27001 standards for handling user and financial data.
22.4) Maintain detailed logs for user activities, document uploads, and login attempts for security audits.
22.5) Implement automated daily backups with a secure disaster recovery plan.
22.6) API security measures include OAuth 2.0, token expiration, and IP whitelisting for admin access.
________________________________________
Additional Functional Requirements:
23) The website should ensure 99.9% uptime, with backup and disaster recovery plans.
24) The platform should be scalable to accommodate growing numbers of users, assets, and documents.
25) Fast page load times (under 3 seconds) for all pages and operations.
26) The website must maintain detailed logs of user activities (e.g., document uploads, login attempts) for auditing and security purposes.
27) Data security is the highest priority as the website will capture the financial details of users.
28) Website must be responsive and compatible with desktops, laptops, mobile phones, and tablets.
29) Consistent color scheme, fonts, and themes across the website, including popups and tabular formats.
30) User-friendly navigation and accessibility options (e.g., screen readers, keyboard, navigation).
31) All images and media used must be licensed or royalty-free to avoid copyright issue.
32) Check for all the possible user reaction against every logic.
Handover Requirements
33) Finalize & share website architecture before initiating development.
34) Weekly meetings for tracking project progress.
35) Phase wise Code walkthrough after completion.
36) Handover of application code, documents, and other configurations.
Deliverables at the defined timelines
1. Source code
a) Frontend code (React JS)
b) Backend Code (Microservices Architecture based REST API)
c) Database (DDL/DML scripts)
d) Deployment scripts
2. Code Quality check reports including Frontend and Backend (SonarQube etc.).
3. Documents
a) API specification
b) LLD (Low level document)
c) Deployment document


Other Standards and Guidelines-
1. Microservices based architecture for backend APIs.
2. Proper logging should be implemented for transaction tracing.
3. Security - Cross-Site Scripting (XSS), token based / api key based authentication.
4. Modules access should be based on Roles (RBAC).
5. Code coverage should be more than 80%.
6. Validations on the server side and client side must be in place.
7. Web pages must be web responsive.
8. REST endpoints must meet the standards HTTP codes and SLA.
9. The database should be normalized.
10. ORM must be implemented