How fernandovcg33/programacion-2 works
Project type and purpose
• This is not a single product but a coursework repository for “Programación 2” (semester 1-2025).
• It contains multiple small Java applications (console and Swing GUI), each in its own top-level folder:
• Ajedrez (Chess CLI)
• Examenes/Segundo examen (Student records CLI)
• Futbol (Soccer CLI)
• Medallas (Medals CLI)
• interfaces_graficas/primera_interfaz (Simple GUI)
• interfaces_graficas/elecciones/Elecciones (Election management GUI)
• There is no central database or web server—each is a standalone Java module.
File structure
• Top-level directories represent independent sub-projects.
• Each sub-project follows the Java module layout:
• module-info.java at root of src
• src/<package> contains .java domain, UI, and Main classes
• Some GUI projects also include resource files (e.g., .txt data files).
• No build scripts (Maven/Gradle)—likely compiled/run via Eclipse or command line.
Examining the README
• Confirms this is an assignment-collection for a course.
• No further architectural guidance in the README.
Relationships and interactions
• Main → UI layer (invokes window creation or console prompts)
• UI layer → Domain layer (passes user input to model objects)
• Domain layer → Persistence layer (through Archivos utility)
• Persistence layer → Domain layer (on startup/load operations)
Architectural patterns and principles
• Each app is a simple layered monolith (Presentation → Domain → Persistence).
• No frameworks, just procedural/Swing code.
• Separation of concerns: keep UI code in window classes, domain logic in model classes, and file I/O in Archivos.
Technologies and libraries
• Java SE 9+ modules (module-info.java)
• Swing (interfaces_graficas projects)
• Plain files for data storage
• No external dependencies or databases