Functional Requirements (FR) - (A functional requirement is simply a description of what the system must do)

These are the specific features the system must perform.

• User Management: Create accounts with Email, Username, Password, Nickname, and Profile Picture.
• Role-Based Access: 01 Admin can create chats and manage users; multiple Users can self-subscribe/unsubscribe.
• Chat Lifecycle: System must notify subscribed users when a chat starts, display join/leave timestamps, and handle "Bye" commands.Persistence:
• Save chat logs to a .txt file and store the file link in a database

Non-Functional Requirements (NFR)

These define how the system should behave under the hood.

• Concurrency: Support multiple users simultaneously using Threads.
• Distributed Nature: Use RMI for communication between client and server.
• Data Integrity: Use Hibernate for all CRUD operations to ensure consistent database states.

<--- Admin can only create one chat a time --->

---

USE CASE Diagram (defines the boundaries of your system and who does what)

Admin CLI

Client CLI

---

Chat Logs