Software Requirements Specification (SRS)

Bar Management System Mobile App

1. Introduction

1.1 Purpose
This Software Requirements Specification (SRS) document defines the system requirements for the
Bar Management System mobile application. The system is designed to manage bar operations,
including sales, inventory, stock, and reporting. The application will be developed as a mobile app
with React Native for the frontend and C++ with Qt for the backend.

1.2 Scope
The Bar Management System will focus solely on bar operations (excluding restaurant management)
and will serve three main user roles: Admin, Manager, and Bartender. The system will handle
functions such as order management, inventory management, sales reporting, and user
authentication.

1.3 Definitions, Acronyms, and Abbreviations

 React Native: A framework for building mobile applications using JavaScript and React.

 C++: A powerful, high-performance programming language used for backend processing.

 Qt: A framework for building cross-platform applications with C++, used for backend logic
and networking.

 JWT (JSON Web Tokens): A method for securely transmitting information between frontend
and backend, particularly for user authentication.

 SQLite: A lightweight, self-contained database engine.

 PostgreSQL: A relational database management system (RDBMS) used for centralized data
storage.

2. Overall Description

2.1 Product Perspective

The Bar Management System is a standalone mobile application that connects to a backend service
written in C++ (Qt). The frontend (mobile app) communicates with the backend via REST APIs or
WebSocket for real-time updates. The app provides role-based access, where different users
(Admin, Manager, Bartender) will have different permissions and access levels.

2.2 User Classes and Characteristics

 Admin: Full access to all features, including user management, system configuration, and
report generation.

 Manager: Limited access to system configuration and full control over stock, orders, and
reports.

 Bartender: Can process orders, view product catalog, and register sales.

2.3 Assumptions and Dependencies

  The system assumes that the mobile device will have an internet connection for syncing data
with the backend.

 The backend is assumed to be deployed on a server that can handle a large number of
concurrent users, especially for real-time features like live sales tracking.

3. System Features

3.1 User Management

3.1.1 Description

 Admins can create, modify, and delete user accounts for Managers and Bartenders.

 Users have roles that restrict their access to certain parts of the system.

3.1.2 Functional Requirements

 Admin:

o Create, update, and delete Manager and Bartender accounts.

o Manage user roles and permissions.

 Manager:

o View user accounts but cannot modify them.

 Bartender:

o Cannot access user management features.

3.2 Authentication and Access Control

3.2.1 Description

 The system will use JWT for user authentication.

 Roles-based access control will restrict functionality based on the user’s role.

3.2.2 Functional Requirements

 Admin, Manager, and Bartender will log in with email and password.

 On successful login, a JWT token will be issued, which must be used for further requests.

3.3 Order Management

3.3.1 Description

 Bartenders will take customer orders, which are then registered in the system.

 Orders include the drinks, quantities, and the total cost.

3.3.2 Functional Requirements

 Bartender:

o Take orders by selecting drinks from the catalog.

o Input the customer’s name (optional).

 o Automatically calculate total cost.

o Print or save a receipt.

o Record the timestamp, bartender ID, and order ID.

3.4 Inventory Management

3.4.1 Description

 Managers will add and update stock items, track stock levels, and get low-stock alerts.

 Stock quantity will automatically decrease when a sale is made.

3.4.2 Functional Requirements

 Manager:

o Add stock entries (product, quantity, unit cost).

o View and update current stock levels.

o Receive alerts when stock levels fall below a predefined threshold.

 Bartender:

o Can view current stock levels but cannot modify them.

3.5 Sales and Reporting

3.5.1 Description

 The system will track sales and generate reports.

 Managers and Admins can generate reports on sales, inventory, and staff performance.

3.5.2 Functional Requirements

 Manager:

o View sales reports (daily/weekly/monthly/yearly).

o Generate stock entry and exit reports.

o Generate low-stock alerts.

 Admin:

o Access all reports.

o Generate user performance reports.

3.6 System Performance

 The system should handle at least 500 concurrent users.

 It should provide real-time updates for sales and stock levels.

 The system must support efficient handling of sales and order calculations without
performance degradation.

3.7 Database Requirements

  Database: The system will use PostgreSQL for centralized database management or SQLite
for local storage.

 Tables:

o Users: id, name, role, email, password

o Products: id, name, category, price, unit, stock_quantity

o Sales: id, product_id, quantity, price_sold, bartender_id, customer_name, date

o StockEntries: id, product_id, quantity, unit_price, date, manager_id

4. External Interface Requirements

4.1 Frontend (React Native)

 User Interface:

o The app will have a clean, user-friendly design with intuitive navigation.

o Each role (Admin, Manager, Bartender) will have different views tailored to their
tasks.

 API Communication:

o The frontend will communicate with the C++ backend via RESTful APIs or
WebSockets (for real-time updates).

4.2 Backend (C++ with Qt)

 API Layer:

o Expose REST APIs for handling user authentication, order registration, sales data,
stock management, and reports.

 Real-time Communication:

o WebSockets will be used for live updates on sales and stock levels.

 Database Layer:

o The backend will interact with a PostgreSQL or SQLite database to store user data,
sales, and inventory.

5. Non-Functional Requirements

5.1 Performance Requirements

 The backend (C++) should be able to handle at least 500 concurrent users with low latency.

 Response times for API calls should be under 1 second.

 Real-time updates (WebSocket) should be responsive, with updates appearing in less than 2
seconds.

5.2 Security Requirements

  All data transmission should be encrypted using SSL/TLS.

 User passwords should be securely hashed using algorithms like bcrypt.

 JWT tokens will be used for secure authentication.

5.3 Availability

 The system should be highly available with an uptime of at least 99.9%.

 The backend should support automatic failover and redundancy.

5.4 Scalability

 The system should be able to scale horizontally to handle increased load (more users, more
sales, etc.).

 Database queries should be optimized for scalability.

6. Appendix

6.1 Technologies Used

 Frontend: React Native

 Backend: C++ with Qt

 Database: PostgreSQL or SQLite

 Authentication: JWT

 Real-time Updates: WebSocket

 Reports and Statistics: Chart.js or Recharts (for frontend charting)