How space99999/sistema-gestion-reservas-hotel works
Project Type and Purpose
• This is a console-based Java application for hotel reservation management.
• It handles domain entities (rooms, clients, reservations, invoices) and persists data in text files.
• No GUI; interaction is via the command line.
File Structure Analysis
• Top level:
• src/proyecto_2p: Contains all Java source files grouped by functionality.
• build/, dist/: Ant-generated build output and distributable JAR.
• nbproject/: NetBeans project configuration.
• *.txt files at root: Data stores for rooms, reservations, clients, invoices.
• Within src/proyecto_2p:
• Domain classes: Habitaciones, HabitacionSencilla, HabitacionesMatrimoniales, HabitacionesMultiples, Cliente, Reservaciones, Factura.
• Data access: ArchivoCliente.java, ArchivoReservaciones.java, ArchivoFactura.java, ArchivosHabit.java.
• Main entry point: Proyecto_2p.java.
README Insights
• Defines core features: CRUD for rooms, booking, listing reservations/clients, invoice generation/listing.
• Specifies Java 17 and Maven requirement (although project uses Ant).
• Data persistence solely via text files named habitaciones.txt, Reservaciones.txt, Clientes.txt, Factura.txt.
a. Main Components
• Presentation Layer: Console UI (Proyecto_2p.java).
• Business Logic / Services: orchestrates operations on domain entities.
• Data Access Layer: Archivo*.java classes reading/writing text files.
• Data Stores: the four text files.
• Domain Model: classes for Cliente, Habitaciones, Reservaciones, Factura.
b. Relationships & Interactions
• User inputs command in the console → routed by Proyecto_2p to the appropriate service logic.
• Service logic instantiates/manipulates domain objects and invokes the corresponding Archivo*.java to persist or retrieve data.
• Archivo*.java reads/writes to the .txt data stores.
• Retrieved data is mapped back into domain objects and passed up to the presentation layer for display.
c. Architectural Patterns
• Layered architecture: Presentation → Business Logic → Data Access → Data Store.
• Separation of concerns: file I/O code isolated in Archivo*.java, domain logic in domain classes.
d. Key Technologies
• Java 17 language.
• Ant build scripts (build.xml, nbproject).
• Text files as the persistence mechanism.