All work

/01 · Full-stack / Education · 2026

Student Management System

One academic system. Three different perspectives.

MY ROLE

Full-stack development · Internship project

STATUS

Implemented core workflows · Active development

STUDENT MANAGEMENT SYSTEMARCHITECTURE STUDY / 01
Connected
by design.ACADEMIC WORKFLOWS / 2026
AdminInstructorStudent
NestJS APIJWT + ROLE GUARDS
PostgreSQLDRIZZLE ORM
REACT / NESTJS / POSTGRESQLIMPLEMENTATION DIAGRAM
Architecture visualization drawn from the implementation.

The relationships are the system.

Academic records are deeply connected. An enrollment belongs to a student and a course offering; attendance and grades depend on that enrollment. Each person needs access to a different part of the same information.

I worked across the React frontend, NestJS API, and PostgreSQL schema during my internship at Auspify Technologies. The system separates administration, teaching, and student workflows while keeping permission checks in the API.

How the pieces fit.

  1. 01ReactRole-specific workspaces
  2. 02NestJSJWT guards · Feature modules
  3. 03PostgreSQLTyped schema with Drizzle
ReactTypeScriptNestJSPostgreSQLDrizzle ORMVitest

Role-specific access

JWT authentication and role guards protect endpoints for administrators, instructors, and students. Pending registrations have an administrator approval workflow.

Connected academic records

Departments, semesters, courses, and course offerings form the basis for enrollments, attendance, and grades.

Student self-service

Dedicated endpoints expose the signed-in student’s profile, courses, attendance, and grades without requiring a client-supplied student identity.

Assignments & assessment

Modules cover assignments, submissions, quizzes, and grading alongside the core academic records.

01

Authorization belongs behind the interface.

A hidden navigation item is not an access-control boundary. Student routes derive identity from the verified JWT, while administrative routes declare the required role.

02

Protect relationships in the database.

The enrollment schema prevents duplicate student–course-offering pairs with a unique constraint. Restricted deletes protect related records from being removed accidentally.

03

A shared repository, separate responsibilities.

npm workspaces keep frontend and backend changes together. NestJS feature modules organize the API around academic responsibilities rather than one large controller.

What’s there today.

The repository contains the academic modules, role-specific frontend workspaces, migrations, and automated tests. It remains an evolving internship project; this case study does not claim a completed production rollout.

NEXT PROJECT / 02

Safaga GeoAtlas