# unamfi/sistop-2025-2 architecture

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

- Interactive diagram: https://gitdiagram.com/unamfi/sistop-2025-2
- Repository: https://github.com/unamfi/sistop-2025-2

## Overview

- Repository Metadata & Configuration: Represent files such as .gitignore, COPYING.md, README.md, and the license image. These provide the foundational configuration for Git and the licensing information.
- Ejemplos_en_clase (Class Examples): A container for in-class examples (with subdirectories like “1.Introducción”, “2.Administración_de_procesos”, “3.Administración_de_memoria”). This shows sample implementations in various languages (C, Python, Ruby, assembly, etc.) used for teaching fundamental Operating Systems concepts.
- Exposiciones (Presentations): Contains folders with presentation PDFs, documentation, and links to videos. This segment is used for student or instructor expositions.
- Practicas (Practices): Further subdivided by assignment number (1, 2, 3, 4) and inside each assignment, each student or team has their own subdirectory with source code and documents. There are many programming languages involved (C, Go, Java, Python, etc.) indicating that the practicas are hands-on coding exercises.
- Proyectos (Projects): Although less populated, it similarly contains its own README and organization for project submissions.
- Tareas (Assignments/Tasks): Contains directories for individual or team tasks with a mix of source code and documentation. This area also has its own organization (e.g., “CanoCarlos-CortesAngel”, “MelendezAnuar”, etc.).

##### Relationships and Interactions
- The top-level repository acts as the “hub” that organizes all the course deliverables.
- Each main directory (ejemplos_en_clase, exposiciones, practicas, proyectos, tareas) can be visualized as separate components that have a similar internal structure: grouping by assignment type or activity, then by individual submissions.

##### Architectural Patterns and Design Principles
- Modular and Organized Structure: The repository is divided by activity type (class examples, practices, tasks, etc.), which is similar to a modular architecture. Each module (directory) is self-contained, with its own README (in some cases), Git configuration files, and source files.
- Consistent Naming Conventions and Hierarchical Organization: Folders are named according to assignment numbers and student names, indicating a standardized submission process as described in the README.

##### Technologies, Frameworks, or Tools
- Git and GitHub: These are the underlying version control and collaboration systems.
- Multiple Programming Languages: (C, Python, Ruby, Go, Java, etc.) which indicate that various Operating Systems concepts are practiced in different environments.
- Documentation & Licensing Files: CC BY 4.0 license, which plays an important role in the legal aspect of contributions.

## Diagram (Mermaid)

```mermaid
flowchart TD
    subgraph "Repository Structure"
        RM["Repository Metadata & Configuration"]:::metadata
        EJ["Ejemplos_en_clase"]:::module
        subgraph "Ejemplos_en_clase"
            EJ1["1.Introducción"]:::submodule
            EJ2["2.Administración_de_procesos"]:::submodule
            EJ3["3.Administración_de_memoria"]:::submodule
        end
        EX["Exposiciones"]:::module
        subgraph "Exposiciones"
            EX1["LopezEstrada_VeraMorales"]:::submodule
            EX2["NavaDavid-TaveraDavid"]:::submodule
            EX3["SeguraLuisa"]:::submodule
        end
        PR["Practicas"]:::module
        subgraph "Practicas"
            PR1["Practicas/1"]:::submodule
            PR2["Practicas/2"]:::submodule
            PR3["Practicas/3"]:::submodule
            PR4["Practicas/4"]:::submodule
        end
        PJ["Proyectos"]:::module
        subgraph "Proyectos"
            PJ1["Proyectos/1"]:::submodule
        end
        TA["Tareas"]:::module
        subgraph "Tareas"
            TA1["Tareas/1"]:::submodule
        end
    end

    subgraph "Git Workflow"
        FW1["Fork"]:::workflow
        FW2["Commit"]:::workflow
        FW3["Pull Request"]:::workflow
        FW1 --> FW2 --> FW3
    end

    FW3 -->|"merge"| RM

    click RM "https://github.com/unamfi/sistop-2025-2/blob/main/.gitignore"
    click EJ "https://github.com/unamfi/sistop-2025-2/tree/main/ejemplos_en_clase"
    click EX "https://github.com/unamfi/sistop-2025-2/tree/main/exposiciones"
    click PR "https://github.com/unamfi/sistop-2025-2/tree/main/practicas"
    click PJ "https://github.com/unamfi/sistop-2025-2/tree/main/proyectos"
    click TA "https://github.com/unamfi/sistop-2025-2/tree/main/tareas"

    classDef metadata fill:#f9f,stroke:#333,stroke-width:2px;
    classDef module fill:#ccf,stroke:#333,stroke-width:2px;
    classDef submodule fill:#eef,stroke:#333,stroke-width:1px;
    classDef workflow fill:#cfc,stroke:#333,stroke-width:2px;
```
