INV. IEnterprise ApplicationBackend Engineering2024

WISLA Platform

A complete enterprise web application for university–company partnership: a Spring Boot backend with role-based access control, state machines for every workflow, and three different organisations under one roof.

WISLA Platform — Enterprise Application

Grade

19/20

Organisations

3 roles

Backend

Spring Boot

Store

MySQL · JPA

The fact sheet

WISLA is a full software system, architected and shipped end to end. The backend is Spring Boot with Spring Security at the gate: companies, faculties and students each hold a role, and every screen asks who is looking before it renders. Academic email verification opens the door; explicit state machines drive internships, applications and partnership agreements from draft to done; JPA over MySQL keeps the whole archive consistent. A CV snapshot freezes each application in time, so what the faculty reviewed is exactly what the company receives. Verified with a grade of 19/20.

Field notes — problems, decisions

01

One system, three identities

Companies, faculties and students share one platform, but nothing about their day looks the same.

Role-based access control with per-role views — authorization is resolved against the authenticated principal on every request.

02

Workflows with real states

Internships, applications and partnership agreements pass through approval chains; a record must never be in two places.

Explicit state machines for every flow — status is a resolved fact, not a guess, and transitions are the only way to move.

03

The door has to check IDs

Only real academic addresses should pass through the gate of the university system.

Academic email verification before the first login, enforced server-side at registration.

Next accession — INV. IIPalais Amghass →