How salvadorandre/proyecto-i-programaci-n- works
Project type and purpose
• This is a C++20 monolithic, console-oriented (or desktop) application built with CMake/CLion.
• The domain seems to be an academic assignment management system: it handles Estudiantes (students), Profesores (teachers), and Asignaciones (assignments).
File structure
• Top-level files:
• CMakeLists.txt – build configuration
• main.cpp – application entry point
• interfaces/ – abstract headers (DTOs, UI, controllers, models, repositories, services)
• src/ – concrete implementations mirroring the interfaces hierarchy
• src/utils/ – utility code (e.g., Cursos helper)
README
• Only notes C++20 & CLion, no higher-level architecture doc—so we infer a standard layered architecture from the directory layout.
Main components and their interactions
a. Presentation Layer (UI)
• interfaces/UI/ui.h + src/UI/ui.cpp
• Responsible for user input/output and kicking off controller actions
b. Controller Layer
• interfaces/controller/*.h + src/controller/*.cpp
• Receives UI events, validates or transforms input, calls Services
c. Service Layer
• interfaces/services/*.h + src/services/*.cpp
• Implements business logic (e.g., assign a course, manage student/teacher rules)
d. Data Access Layer (Repository)
• interfaces/repository/*.h + src/repository/*.cpp
• Encapsulates persistence (could be file or database behind the scenes)
e. Domain Models & DTOs
• interfaces/models + src/models: Estudiante, Profesor classes
• interfaces/DTOs: Asignacion data‐transfer object
f. Utilities
• src/utils/Cursos.{h,cpp} for shared helper functions
Relationships (data flow):
UI → Controller → Service → Repository → (Persistent storage)
Service ↔ Models/DTOs
Controllers can also orchestrate multiple services
Architectural patterns and technologies
• Layered (n-tier) architecture: separation of concerns across UI, Controllers, Services, Repositories, and Models
• Dependency inversion via interfaces/ abstract headers, implemented in src/
• Build system: CMake for compilation, linking all modules into a single executable
• Language: Modern C++20, likely using STL, possibly smart pointers or dependency injection patterns