$597.00 Fixed
1. General Requirements
Technology Stack:
The platform must be developed exclusively in plain Java using Vaadin. Frameworks such as Spring Boot or similar should not be used. External libraries or third-party APIs are to be avoided as much as possible—with the exception of the security API integration detailed below. All features and functionality must be implemented natively to maintain full control over the system. Only browser-native elements (e.g., CSS/HTML scrollbars) may utilize non-Java approaches.
Modern Design:
The platform should adhere to modern UI/UX principles, offering responsive layouts and optimal performance.
Progressive Web App (PWA):
Full PWA support is required, including offline capabilities, installability, and device responsiveness.
Scalability:
The architecture must be designed to efficiently handle a high number of users and roles.
Security:
Robust security measures must be implemented, including encrypted communication, secure authentication mechanisms (e.g., OAuth2, JWT), and fine-grained, role-based access control.
Extension: Integration of a third-party security API to enhance threat detection, vulnerability scanning, and automated incident response, following strict encryption and security protocols.
2. Role Management
Support for up to 8 Roles:
The platform should support a clear role hierarchy and dynamic, role-based access control.
Dashboard Structures:
Superadmin Dashboard:
Provides full control over the platform, allowing the management of Subadmins, Vendors, Managers, and Users. Features include dynamic permission assignments and access to platform-wide analytics and logs.
Subadmin Dashboard:
Offers limited control under the Superadmin’s jurisdiction. Subadmins can manage Sub-Subadmins, Managers, and Employees within their assigned scope and have access to restricted analytics and user management features.
Vendor Dashboard:
Focused on franchise-specific operations management. Vendors can create and manage Users (such as Franchise Owners, Managers, and Employees) and have access to vendor-specific reporting and insights.
User Profiles:
Each role has a tailored dashboard with customizable functionality and restricted access based on assigned permissions.
3. Role-Specific User Creation
Superadmin:
Can create Subadmins, Vendors, Managers, and Users.
Subadmin:
Can create Sub-Subadmins, Managers, and Employees within their designated scope.
Vendor:
Can create Franchise Owners, Managers, and Employees.
4. Core Features
Role-Based Access Control:
Granular permissions that are tailored to each specific role.
Dashboards:
Intuitive, role-specific dashboards for all user types.
User Management:
Full CRUD (Create, Read, Update, Delete) operations for all roles along with dynamic permission assignments.
Activity Logging:
Comprehensive audit trails that log all user actions on the platform.
Responsive Design:
The application must be optimized for both desktop and mobile devices.
Integrated Multi-Vendor Payment System:
Allows users to upload funds via a multi-vendor PayPal integration.
Supports payments between users within the platform.
New Feature – POS System Integration:
Objective: Extend the platform to support an integrated Point-of-Sale (POS) system for physical retail operations.
Functionalities Include:
Support for barcode scanners and receipt printers.
Real-time inventory management synchronized with the central database.
Integration with the existing payment system (e.g., multi-vendor PayPal) as well as connectivity with additional payment providers.
An API interface for communication between POS hardware and the backend, ensuring real-time transaction capture and analysis.
Integration into the existing role-based access control system, enabling store managers and other authorized personnel to manage and monitor POS-specific operations.
5. Technical Requirements
Backend:
Must be built using Vaadin with plain Java components and a modular design.
Third-party frameworks like Spring Boot must be avoided.
Extension – Third-Party Security API Integration:
The system shall integrate with an external security API to provide advanced security functionalities, such as real-time threat detection, vulnerability scanning, and automated incident response.
This integration must be modular to allow for future changes or enhancements of the security provider.
The API must offer interfaces for monitoring and managing security events and should seamlessly integrate with existing authentication and authorization mechanisms (e.g., OAuth2, JWT).
Strict encryption standards and security protocols must be enforced to ensure data and transaction protection.
Frontend:
Must be exclusively developed using Vaadin to ensure seamless backend integration.
No external UI frameworks are permitted (aside from using CSS/HTML for native browser elements).
Database:
The platform should support relational databases such as PostgreSQL or MySQL.
PWA Optimization:
The platform must be fully offline-capable and installable as a native-like application.
6. Additional Requirements: Standard Multi-Role SaaS Platform Template (Optional Milestone)
Dual-Project Approach:
Two separate projects will be created, sharing the same underlying multi-role SaaS platform structure.
Template Platform (Phase 1):
User registration and login functionalities.
Listing functionalities for content or items.
Superadmin capabilities to send email newsletters to all users, and vendor-specific newsletter functionality to target their own user base.
Superadmin ability to create and manage Subadmins, Vendors, Managers, and Users with dynamic permission assignments.
Vendors can create and manage Managers, Franchise Owners, and Employees with their permissions reflected in their dashboards.
Integrated multi-vendor PayPal payment system for uploading funds and facilitating internal transactions.
This template will serve as the foundational platform for further project-specific customizations (e.g., ordering systems, chat functionalities, etc.).
7. Team Requirements
A team of at least 6 developers is required due to the complexity and tight timeline:
2 Backend Developers:
Responsible for role management, security implementations (including the third-party security API), and core system logic.
2 Frontend Developers:
Tasked with ensuring a modern UI/UX using Vaadin and optimizing the PWA functionalities.
1 QA Engineer:
8. Deadline
The project must be delivered within a short timeframe, with strict milestones to ensure timely completion.
- Proposal: 0
- 55 days
