Spring Boot project structure — package-by-feature, record DTOs, Flyway migrations, multi-profile config, actuator, proper test structure
84
76%
Does it follow best practices?
Impact
97%
4.04xAverage score across 5 eval scenarios
Passed
No known issues
A healthcare clinic needs a Spring Boot service for appointment booking. Build it with Spring Boot 3 and Java 17+.
Domain concepts:
Endpoints:
POST /api/doctors -- register a doctor (name, specialty required)GET /api/doctors -- list doctors, optional filter by specialtyPOST /api/doctors/:id/slots -- create available time slots for a doctor (array of start/end time pairs)GET /api/doctors/:id/slots -- get available slots for a doctor on a given date (query param: date)POST /api/patients -- register a patientPOST /api/appointments -- book an appointment (patientId, timeSlotId, reason). The time slot must be available and in the future.GET /api/appointments/:id -- get appointment details including doctor and patient infoPATCH /api/appointments/:id/cancel -- cancel an appointment (only SCHEDULED appointments can be cancelled, release the time slot)GET /api/patients/:id/appointments -- list a patient's appointmentsBusiness rules:
Use PostgreSQL for the database.
Produce a complete Spring Boot project with:
pom.xml with dependenciesYou may create additional files as needed.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
springboot-project-structure
verifiers