How drodriguezgarces/poo_2024_25 works
Project type and purpose
• This is a Java-based, console-driven OOP application (POO_2024_25) for managing mobility services (vehicles, trips, users, bases, maintenance staff, etc.).
• There is no web/UI layer; it follows a classic layered architecture: entry point → controller → service → domain models → utilities.
File structure
• Top-level folders:
– src/: Java source organized by package
· controller/ – SistemaController.java
· movilidad/ – Movilidad.java (main class)
· service/ – BaseService, UsuarioService, VehiculoService, ViajeService
· model/ – domain entities (Usuario, Vehiculo subclasses, Base, Viaje, Trabajador, etc.)
· util/ – Constants, ValidationUtils
· module-info.java – Java module descriptor
– bin/: compiled class output mirroring src/ packages
– README.md – project title only
Key architectural insights
• Layered pattern (somewhat MVC-inspired):
– Presentation/Orchestration: Movilidad (main) + SistemaController
– Business logic: Service layer
– Domain layer: Model classes
– Cross-cutting concerns: ValidationUtils, Constants
• No external persistence layer is visible (likely in-memory or future extension).
a. Main components
1. Movilidad (application entry point)
2. SistemaController (handles user input/commands)
3. Service Layer (BaseService, UsuarioService, VehiculoService, ViajeService)
4. Model Layer (domain entities: Usuario, Vehiculo, Base, Viaje, Trabajador, etc.)
5. Utility Layer (ValidationUtils, Constants)
b. Relationships & interactions
– Movilidad → invokes SistemaController methods
– SistemaController → calls appropriate Service methods
– Services ↔ manipulate Model objects (create/read/update domain entities)
– Services & Controller → utilize ValidationUtils and Constants for input checks/config values
c. Architectural patterns & principles
– Layered architecture (Separation of concerns)
– Single responsibility per class (e.g., each service handles one entity)
– Java Module System for modularization
d. Technologies & frameworks
– Java (SE), package modules (module-info.java)
– No external frameworks currently (pure Java implementation)
Final advice
– Ensure the module boundary (module-info.java) is shown if modularization is important to your architecture.
– Review the source to confirm any missing components (e.g., logging or exception-handling utilities) and add them.