Table of Contents
- Overview
- Role
- Problem
- Goal
- Solution
- Technical Implementation
- Challenges and Learnings
- Final Thoughts
Overview
Information System for Study Program Services is a web-based academic administration platform built for the Faculty of Science and Technology at Universitas Islam Negeri Jakarta. The system centralizes and digitizes academic workflows — from research proposal seminar registration to thesis defense grading — serving students, lecturers, and faculty administrators through a role-based access system.
Role
Software Engineer
Problem
Academic administration at the faculty was heavily manual and paper-based:
- Students submitted seminar and thesis registration forms physically, causing delays and lost documents.
- Lecturers had no centralized place to manage supervision logs or input grades.
- Faculty staff manually handled official letter requests (e.g., department head signature letters, assignment letters) with no tracking system.
- There was no unified view for administrators to monitor progress across all study programs.
Goal
- Build a unified, role-based web portal for all academic service activities within the faculty.
- Digitize registration, approval, revision, and rejection workflows for academic milestones.
- Enable lecturers to record supervision sessions and submit grades electronically.
- Provide administrators with a dashboard view of student progress and faculty statistics.
- Support official letter requests with digital signature capability.
Solution
User Roles
The system supports four distinct roles with different access permissions:
- Student: Register for Research Proposal Seminar, Results Seminar, and Thesis Defense; upload required documents; track approval status; log thesis supervision sessions.
- Lecturer: View assigned students; input and submit grades for all academic milestones; download grading documents; manage supervision logs.
- Study Program Staff: Approve, reject, or request revisions on all student submissions; manage grading periods; generate official grading documents; request assignment letters.
- Faculty Administration: Full access across all study programs; user management; department head signature letter handling; faculty-wide statistics.
Core Modules
| Module | Description |
|---|---|
| Research Proposal Seminar Registration | Students submit documents; staff approve, reject, or request revisions |
| Results Seminar Registration | Same workflow as Proposal Seminar; includes scheduling |
| Thesis Defense Registration | Thesis defense registration with document uploads |
| Grading | Lecturers input scores; staff generate official grading reports (DOCX) |
| Supervision Monitoring | Log and track thesis advisory sessions per student |
| Letter Requests | Department head signature letters and assignment letters with file upload/download |
| User Management | Admin manages accounts, roles, and email verification |
| Lecturer Statistics | Dashboard showing per-lecturer student load and supervision data |
Technical Implementation
Stack
- Backend: Laravel (PHP) with MVC architecture
- Frontend: Blade templates with AdminLTE 3 and Bootstrap 4
- Database: MySQL with 20+ tables covering all academic entities
- Authentication: Laravel Auth with email verification and role-based middleware
- Notifications: Laravel Notifications via email for approval/rejection/grading events
- File Handling: Secure encrypted file IDs for document downloads; PDF viewing in-browser
- Document Generation: Server-side DOCX generation for official grading reports (Proposal Seminar, Results Seminar, Thesis Defense)
- Activity Logging: Custom activity log table for audit trails
Role-Based Access Control
A custom middleware layer enforces route-level access per user role, ensuring each user only sees and interacts with data relevant to their responsibilities.
Database Design
The database is structured around the core academic entities — users, study programs, registrations, grades, supervision sessions, and letter requests — with a normalized schema that supports multi-role, multi-program access patterns.
Challenges and Learnings
- Multi-role Complexity: Designing a clean permission model where each role sees exactly the right data required careful middleware layering and policy classes.
- Workflow State Management: Handling approve/reject/revise status transitions consistently across three different academic milestones required a unified approach to avoid code duplication.
- Secure File Access: Files are accessed via encrypted IDs rather than direct paths to prevent unauthorized document access.
- Email Notifications: Integrating real-time email notifications for every workflow event (acceptance, rejection, grade submission) required careful queue and throttle configuration.
Final Thoughts
- Digitization Has Immediate Impact: Replacing paper-based processes with a tracked digital workflow dramatically reduced administrative back-and-forth.
- Role Separation Is Critical: Strict role-based access prevented data leakage across study programs and ensured accountability.
- Modular Design Pays Off: Structuring each academic service (Proposal Seminar, Results Seminar, Thesis Defense) as an independent module made it straightforward to extend the system with new service types.