Software Requirements Specification (SRS)Legacy format

---

### 1.1 Purpose

The purpose of this document is to provide a detailed description of the Software Requirements for the TrustLocalHub platform. It defines the functional and non-functional requirements, user roles, and system architecture.

### 1.2 Scope

TrustLocalHub is a web-based marketplace designed to connect local service providers (plumbers, electricians, cleaners, etc.) with customers. The platform facilitates service discovery, booking management, and provider verification to ensure a trustworthy ecosystem.

### 1.3 Definitions, Acronyms, and Abbreviations

• SRS: Software Requirements Specification

• JWT: JSON Web Token (for authentication)

• Admin: System administrator with oversight capabilities

• Provider: A professional offering local services

• User/Customer: An individual seeking local services

---

### 2.1 Product Perspective

TrustLocalHub is a full-stack web application consisting of a React-based frontend and a Node.js/Express backend, using a MySQL database for persistent storage.

### 2.2 User Classes and Characteristics

1. User (Customer):

• Search for local services by category, location, or name.

• View provider profiles, ratings, and pricing.

• Book services and manage booking history.

• Rate and review service providers.

2. Service Provider:

• Register and create a professional profile.

• Upload verification documents (Aadhaar, Skill Certificate, etc.).

• Manage service offerings and pricing.

• Track and manage customer bookings.

3. Administrator:

• Verify or reject service provider applications based on documents.

• Manage user and provider accounts.

• Monitor platform-wide bookings and reviews.

### 2.3 Operating Environment

• Client: Modern web browsers (Chrome, Firefox, Safari, Edge).

• Server: Node.js environment.

• Database: MySQL 8.0+.

### 2.4 Design and Implementation Constraints

• Responsive design for mobile and desktop using Tailwind CSS.

• Secure authentication using JWT and Bcrypt.

• Database schema must support relational integrity between users, providers, bookings, and reviews.

---

### 3.1 User Interfaces

• Home Page: Search bar and featured service categories.

• Dashboards: Customized views for Users, Providers, and Admins.

• Booking Portal: Interface for selecting dates and confirming service requests.

• Verification Module: Document upload interface for providers.

### 3.2 Software Interfaces

• Backend API: RESTful endpoints provided by Express.

• Database: MySQL connection via mysql2 driver.

• Storage: Local file system for storing uploaded documents (via Multer).

---

### 4.1 Authentication & Authorization

• Registration: Separate flows for Users and Providers.

• Login: JWT-based secure session management.

• Role-Based Access Control (RBAC): Ensuring users can only access their respective dashboards and actions.

### 4.2 User (Customer) Features

• Search & Filter: Find providers by speciality, location, or name.

• Provider Profiles: Detailed view of experience, pricing, and reviews.

• Booking Management: Request service, view status (Pending/Confirmed/Completed).

• Review System: Post ratings and text reviews for completed services.

### 4.3 Provider Features

• Profile Management: Update experience, address, and pricing.

• Document Upload: Submit mandatory documents for admin verification.

• Booking Tracking: View incoming requests and update booking status.

### 4.4 Admin Features

• Provider Verification: Review uploaded documents and approve/reject providers.

• User Management: Enable/disable user or provider accounts.

• System Monitoring: View all bookings and reviews across the platform.

---

### 5.1 Performance Requirements

• API response times should be under 500ms for standard queries.

• Efficient search indexing for provider discovery.

### 5.2 Safety & Security Requirements

• Passwords must be hashed using Bcrypt.

• Sensitive routes must be protected by JWT middleware.

• Input validation to prevent SQL injection and XSS.

### 5.3 Reliability & Availability

• The system should maintain high availability.

• Graceful error handling for database or network failures.

---

• Frontend: React.js, Vite, Tailwind CSS, Axios, React Router.

• Backend: Node.js, Express.js.

• Database: MySQL.

• Authentication: JWT (JsonWebToken).

• File Uploads: Multer.