cactuzzz24/-proyecto-final-poo-csti-1830-4361

Purpose and Runtime

A desktop Java clinic-management system for medical consultations, disease surveillance, vaccinations, patient clinical histories, summaries, and dashboard reporting. It is an Eclipse project with packaged third-party JARs, using Swing/WindowBuilder-style visual screens rather than a web stack. Primary persisted data appears to be local serialized/data files: ProyectoFinal/clinica.dat and ProyectoFinal/clinica_respaldo.dat.

Entry and Session Routing

The user-facing entry point is the login UI at ProyectoFinal/src/Visual/IniciarSesion.java. Authentication and role selection route users into distinct principal screens:

• Administrator: ProyectoFinal/src/Visual/PrincipalAdmin.java

• Doctor: ProyectoFinal/src/Visual/PrincipalMedico.java

• Patient: ProyectoFinal/src/Visual/PrincipalPaciente.java

User identity and authorization are represented by ProyectoFinal/src/Logic/Usuario.java, with person specialization/modeling in ProyectoFinal/src/Logic/Persona.java, ProyectoFinal/src/Logic/Doctor.java, and ProyectoFinal/src/Logic/Paciente.java.

Core Domain and Aggregate Boundary

ProyectoFinal/src/Logic/Clinica.java is the likely central clinic aggregate/service: it owns or coordinates the application’s collections, domain operations, and persistence-facing state. The main medical record workflow is modeled through:

• Appointments: ProyectoFinal/src/Logic/Cita.java

• Consultations: ProyectoFinal/src/Logic/Consulta.java

• Clinical-history summaries: ProyectoFinal/src/Logic/ResumenClinico.java

This forms the principal boundary between Swing screens and business data: UI dialogs collect actions and fields; logic objects represent clinic entities and execute domain updates.

Clinical Operations

Consultation registration is driven by ProyectoFinal/src/Visual/RegConsulta.java, while appointment registration is handled by ProyectoFinal/src/Visual/RegCita.java. Their records can be viewed through ProyectoFinal/src/Visual/ListarConsultas.java and ProyectoFinal/src/Visual/ListarCitas.java.

Disease monitoring is modeled by ProyectoFinal/src/Logic/Enfermedad.java and managed through ProyectoFinal/src/Visual/RegEnfermedad.java / ProyectoFinal/src/Visual/ListarEnfermedad.java. Vaccination management uses ProyectoFinal/src/Logic/Vacuna.java, with registration/application screens at ProyectoFinal/src/Visual/RegVacuna.java and ProyectoFinal/src/Visual/AplicarVacuna.java.

Administration and Master Data

User registration is split between general administration and patient-oriented onboarding:

• ProyectoFinal/src/Visual/RegUsuario.java

• ProyectoFinal/src/Visual/RegUsuarioParaPaciente.java

Role/entity listings expose administrative read and maintenance flows: ProyectoFinal/src/Visual/ListarAdministrador.java, ProyectoFinal/src/Visual/ListarDoctor.java, and ProyectoFinal/src/Visual/ListarPaciente.java. These screens are clients of the domain model rather than separate service tiers.

Reporting and Visualization

Dashboard/chart refresh logic is concentrated in ProyectoFinal/src/Logic/UptadeGraficas.java. It likely transforms clinic data into chart-ready datasets for the principal interfaces. Reporting depends on bundled JFreeChart and JCommon libraries in ProyectoFinal/lib/jfreechart-1.0.19.jar and ProyectoFinal/lib/jcommon-1.0.23.jar; date input uses ProyectoFinal/lib/jdatepicker-1.3.4.jar.

Persistence, Integrations, and Deployment Shape

The application is local-first: no database schema, build system, or remote API client is present in the tree. clinica.dat is the main data store and clinica_respaldo.dat is a backup artifact, implying file-based persistence coordinated from the logic layer. ProyectoFinal/src/server/Servidor.java indicates a server/runtime boundary may exist, but the repository’s dominant architecture remains a Java desktop client with local domain objects and data files. Phone validation/formatting can use bundled ProyectoFinal/lib/libphonenumber-8.13.16.jar.