Hostel management system project
rooms, fees, out-passes and an ER diagram

Warden

Manages rooms and allocation, fees, approves out-passes, closes complaints, posts notices.

Student

Applies for a room, pays fees, requests out-passes, raises complaints, reads notices: only their own records.

Eight entities. Allocation is the history of who held which bed when, so a room change adds a row instead of overwriting the last one.

Relationships

• block contains room (one to many)
• room is allocated in allocation (one to many)
• student holds allocation (one to many)
• student owes fee (one to many)
• student requests outpass (one to many)
• student receives visitor (one to many)
• room has complaint (one to many)
• student raises complaint (one to many)

Mermaid source

Paste it into mermaid.live, draw.io (Arrange, Insert, Advanced, Mermaid) or any Markdown editor that draws Mermaid to get the diagram for your report.

erDiagram
  BLOCK ||--o{ ROOM : "contains"
  ROOM ||--o{ ALLOCATION : "is allocated in"
  STUDENT ||--o{ ALLOCATION : "holds"
  STUDENT ||--o{ FEE : "owes"
  STUDENT ||--o{ OUTPASS : "requests"
  STUDENT ||--o{ VISITOR : "receives"
  ROOM ||--o{ COMPLAINT : "has"
  STUDENT ||--o{ COMPLAINT : "raises"
  BLOCK {
    uuid id PK
    text name
    text gender
  }
  ROOM {
    uuid id PK
    uuid block_id FK
    text room_no
    int floor
    text type
    int capacity
  }
  STUDENT {
    uuid id PK
    text roll_no UK
    text name
    text course
    text guardian_phone
  }
  ALLOCATION {
    uuid id PK
    uuid student_id FK
    uuid room_id FK
    int bed_no
    date from_date
    date to_date
  }
  FEE {
    uuid id PK
    uuid student_id FK
    text kind
    numeric amount
    numeric paid
    date due_on
  }
  OUTPASS {
    uuid id PK
    uuid student_id FK
    timestamp leaves_at
    timestamp returns_at
    text reason
    text status
  }
  VISITOR {
    uuid id PK
    uuid student_id FK
    text name
    text relation
    timestamp in_at
    timestamp out_at
  }
  COMPLAINT {
    uuid id PK
    uuid room_id FK
    uuid student_id FK
    text category
    text status
  }

This builds on Refinar's school starting point, which already has residents with their parents, a daily register and fees with receipts. Rooms, allocation, out-passes and complaints come from the prompt. Running a real college hostel? See the hostel management system page instead.

The prompt it starts with

A hostel management system for a final-year project, in English: blocks, rooms with floor, type and capacity, and beds; students apply for a room and the warden allocates a bed, never beyond capacity; hostel and mess fees per semester with payments and dues; out-pass requests with leaving and return times that the warden approves or rejects; a visitor log; complaints about a room with a category and status; notices. Roles: warden, who does everything, and student, who sees their room, fees, out-passes and complaints only.

• A parent login that shows out-passes and fee dues.
• A QR gate pass scanned by the security guard at exit and entry.
• Mess menu and meal counts per day.
• Automatic room allocation by course and year.

• Hospital management systemPatients, doctors, appointments, prescriptions, wards and bills, with a login per role.
• Library management systemCatalogue, copies, issue and return with due dates, fines and reservations.
• Student management systemStudents, courses, attendance, marks and results, fees and a student login.
• Pharmacy management systemMedicines, batches and expiry, purchases, sales bills and stock alerts.
• E-commerce websiteStorefront, cart, checkout, orders with status, customer accounts and a stock admin.
• Event management systemEvents with ticket types, registration, QR check-in at the door and feedback.