How aneprados/examen_parcial_poo works
Main Components
• Entry Point (main.py): This file likely serves as the starting point of the application.
• Launcher/Controller (Lanzador.py): Acts as the orchestrator that initiates processes or tests.
• Domain Models:
• Clase_punto.py: Implements the “Point” class, likely encapsulating coordinates and related methods.
• Rectangulos_clase.py: Implements the “Rectangle” class, which might internally use or rely on the Point class.
• Supporting/Generated Artifacts:
Relationships and Interactions
• main.py calls or references Lanzador.py, initiating the program flow.
• Lanzador.py likely creates instances of the domain classes (from Clase_punto.py and Rectangulos_clase.py) to carry out tasks or demonstrate OOP functionalities.
Architectural Patterns and Design Principles
• Emphasis on modular OOP design: Each class is isolated into its file to separate concerns.
• The “Launcher” acts as a controller coordinating operations, which is a typical pattern in small-scale console-based applications.
• No complex layers (like services or databases) exist, so focus on the clear separation between business logic (domain models) and program control (launcher and main).
Detail and Clarity
• Avoid unnecessary complexity; even though the project is simple, breaking it into all logical components will help maintain clarity.