# aneprados/examen_parcial_poo architecture

> Architecture diagram of the GitHub repository aneprados/examen_parcial_poo, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-04-01). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/aneprados/examen_parcial_poo
- Repository: https://github.com/aneprados/examen_parcial_poo

## Overview

##### 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.

## Diagram (Mermaid)

```mermaid
graph TD
    %% Program Flow
    subgraph "Program Flow"
        A["Main Entry (main.py)"]:::module
        B["Controller/Launcher (Lanzador.py)"]:::module
        A -->|"calls"| B
    end

    %% Domain Models
    subgraph "Domain Models"
        C(("Point Class (Clase_punto.py)")):::domain
        D(("Rectangle Class (Rectangulos_clase.py)")):::domain
        B -->|"instantiates"| C
        B -->|"instantiates"| D
        D -->|"uses"| C
    end

    %% Legend
    Legend["Legend: Rectangle = Module, Ellipse = Domain Model"]:::legend

    %% Click Events
    click A "https://github.com/aneprados/examen_parcial_poo/blob/main/main.py"
    click B "https://github.com/aneprados/examen_parcial_poo/blob/main/Lanzador.py"
    click C "https://github.com/aneprados/examen_parcial_poo/blob/main/Clase_punto.py"
    click D "https://github.com/aneprados/examen_parcial_poo/blob/main/Rectangulos_clase.py"

    %% Styles
    classDef module fill:#cce5ff,stroke:#0056b3,stroke-width:2px;
    classDef domain fill:#d4edda,stroke:#155724,stroke-width:2px;
    classDef legend fill:#fff3cd,stroke:#856404,stroke-width:2px,dasharray: 5 5;
```
