How ayeshamashiat/pams_backend works
Project type and purpose
• This is a full-stack web application named “Postgraduate Academic Management System (PAMS).”
• Purpose: Support postgraduate thesis and academic workflows (authentication, user roles, supervisor assignment, proposal submission, thesis progress, notifications).
File structure
Top-level:
• backend/ — Node.js/Express monolith
– controllers/ (HTTP-route handlers by domain)
– routes/ (Express routers)
– models/ (Mongoose schemas)
– middleware/ (auth, file upload)
– services/ (business logic, e.g. progressService)
– utils/ (email, notifications, initial admin seeding)
– uploads/ (file store for proposals, reports)
– server.js (app entry)
– package.json (dependencies, scripts)
• README.md (project description, stack, setup)
Patterns & conventions:
• MVC-style separation (models/controllers/services)
• RESTful API endpoints by domain (student, faculty, thesis, etc.)
• JWT-based auth and role middleware
• File-storage for PDF uploads
• Nodemailer for email notifications
Key insights from README
• Frontend: React + Next.js (hosted separately)
• Backend: Node.js, Express, MongoDB (Mongoose)
• Auth: JWT, bcrypt
• Email notifications via Nodemailer
• Roles: Admin, Student, Faculty, PGC