💠

Project Title

VEDU

A Liquid-UI Based Real-Time Collaborative Virtual Classroom Platform for 2026 Pedagogy.

02. Introduction & Objectives

Introduction

Vedu solves the "Zoom Fatigue" problem of limited time meet and specialized classroom management. It bridges the gap between static LMS and chaotic video calls.

Objectives

Latency Control: Keep WebRTC sub-300ms.
Role-Based UX: Distinct dashboards for Teachers (Moderation) and Students (Learning).
Persistence: Automatic attendance and recording to Supabase Storage.

03. System Requirement Specification (SRS)

Software Stack

Backend: Java 17, Spring Boot 3.2.x
Database: PostgreSQL via Supabase
Media Server: LiveKit / OpenVidu v3
Frontend: JavaScript (ES6), HTML5/CSS3

Hardware Baseline

Min Server: 4GB RAM, 2vCPU (For signaling)
Client Bandwidth: 2.5 Mbps (720p Video)
SSL: Required for WebRTC WSS

04. Process Logic

The system utilizes a Service-Oriented Architecture (SOA).

Connection Handshake

1. Client signs in via Supabase Auth.
2. Client hits Spring Boot `/api/meetings/token` with Room Name.
3. Spring Boot verifies roles and requests Token from LiveKit.
4. Client uses JWT to open a WebSocket (WSS) to the Media Server.

05. Development Timeline (Gantt Chart)

A 12-week iterative development cycle (SDLC - Agile).

Phase	Weeks	Deliverable
Requirement Analysis	1-2	SRS Document
Backend Dev (Spring/Auth)	3-5	REST APIs & Supabase Integration
RTC Integration (LiveKit)	6-8	Signaling & Media Streams
Liquid UI Deployment	9-10	Responsive Dashboards
Testing & Optimization	11-12	Final Deployment & Manuals

06. Data Dictionary

Attribute	Data Type	Description
user_id	UUID	Primary Key from Auth.users
user_type	TEXT	Used for Storing Usertype
full_name	VARCHAR(100)	Displayed on Video Label
room_token	TEXT	Temporary LiveKit Session Token
access_token	TEXT	Temporary user Session Token
is_teacher	BOOLEAN	Role check for classroom controls

07. Data Flow Diagram (DFD)

Level 0 DFD: Illustrates how the Participant data flows from the UI through the Spring Gateway to the Media Engine.

Flow: User -> Login API -> Room Token API -> Media Stream Engine

07. Data Flow Diagram (DFD)

Level 1 DFD: Illustrates how the Participant data flows from the UI through the Spring Gateway to the Media Engine.

Flow: User -> Login API -> Room Token API -> Media Stream Engine

08. Entity Relationship Diagram (ERD)

Schema Logic: One Teacher manages many Courses. One Course has many Sessions. Sessions generate multiple Attendance records.

Entities: Users, Courses, Meetings, Attendance, Recordings

10. Expected Report Generation

The system provides automated reporting for educational auditing:

Classroom Audit: Log of join/leave times for students.
Participation Score: Tracking hand-raise frequency per student.
Session Analytics: Aggregated attendance percentage for the semester.

11 & 12. Future Scope & Bibliography

Future Scope

1. AI Summaries: Integration of Gemini API to summarize lecture transcripts.
2. Mobile App: Native iOS/Android apps using LiveKit Mobile SDK.
3. Whiteboard: Real-time SVG canvas for collaborative math work.

References

• LiveKit.io Documentation (2025/26)
• Spring Boot 3.2 Framework Guides
• Supabase Realtime & Auth Documentation