Authentication and role boundaries
Spring Security and role-specific controllers support different journeys after sign-in, keeping student, company, professor and committee interactions organized around their responsibilities.
Java / application engineeringPublic source
Traineeship Management
Connecting placement, supervision and evaluation through role-based application workflows.
The context
A university application built with Java 17, Spring Boot and MySQL. Different workflows support students, companies, professors and a traineeship committee.
View repository ↗Java / application engineering↗
Placement → logbook → evaluationROLE-AWARE
AuthRole-based access
MatchPlacement strategies
TestControllers & services
How it connects
The workflow.
- 01Authentication
- 02Role-based workflow
- 03Matching & placement
- 04Logbook & evaluation
A functional overview of the application’s traineeship lifecycle.
Engineering details
Inside the work.
Matching and assignment strategies
Service-layer search and supervisor-assignment strategies handle placement-related business rules. Factories keep strategy selection separate from the calling workflow.
Logbooks and evaluations
Students maintain logbooks and view evaluations, while company and professor workflows support supervision and assessment. MySQL-backed persistence connects these records to traineeships.
Behavior-focused tests
JUnit 5 and Mockito tests cover authentication controllers, role-specific controllers, services, position-search strategies and supervisor-assignment strategies.
What I took from it.
- Role-based applications require thinking through entire user journeys.
- Separating strategy selection from workflow code makes business rules easier to test.
- Controller and service tests provide useful coverage for both web behavior and domain decisions.
See for yourself
Source & documentation.
Next projectFood Hazard Detection↗