# eitan-wajsberg/tp-gdd-2024-2c architecture

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

- Interactive diagram: https://gitdiagram.com/eitan-wajsberg/tp-gdd-2024-2c
- Repository: https://github.com/eitan-wajsberg/tp-gdd-2024-2c

## Overview

##### Main Components
- Raw Data Source – Although not provided as a physical component in the repository, the project began with a “tabla maestra” (master table) which was disorganized and unnormalized.
- Strategy Documentation – The PDFs (Enunciado.pdf and Estrategia.pdf) provide context for design decisions. Although they are not “executing” components, they are key in explaining why certain architectural decisions were taken.

##### Relationships and Interactions
- Finally, you might include ancillary components or notations referencing how the strategy documents influenced these architectural phases.

##### Architectural Patterns and Design Principles
- The system’s design follows a sequential data transformation architecture:
- First, data normalization (Transactional Model)
- Then, building aggregated or analytical views (BI Model)

##### Technology and Artifacts
- That SQL scripts (data/script_creación_inicial.sql and data/script_creación_BI.sql) are the transformation mechanisms.
- That the overall project was executed within the context of a university assignment for Data Management, so while a production environment isn’t built here, the design represents a realistic simulation of data processing in marketplace systems.

## Diagram (Mermaid)

```mermaid
flowchart TD
    A["Raw Data (Master Table)"]:::source
    B["Normalization Process/ETL"]:::process
    T1["Transactional SQL Script"]:::component
    T2["Transactional ER Diagram"]:::component
    N["Normalized Database (Transactional Model)"]:::database
    C["BI Transformation/Views Creation"]:::process
    BIS1["BI SQL Script"]:::component
    BIS2["BI ER Diagram"]:::component
    D["BI Model (Aggregated Views)"]:::component
    E["Business Intelligence/Analytics"]:::component

    A --> B
    B --> T1
    B --> T2
    T1 --> N
    T2 --> N
    N --> C
    C --> BIS1
    C --> BIS2
    BIS1 --> D
    BIS2 --> D
    D --> E

    subgraph "Strategy Documentation"
        F1["Enunciado"]:::doc
        F2["Estrategia"]:::doc
    end
    F1 -.-> B
    F2 -.-> C

    click T1 "https://github.com/eitan-wajsberg/tp-gdd-2024-2c/blob/main/data/script_creación_inicial.sql"
    click T2 "https://github.com/eitan-wajsberg/tp-gdd-2024-2c/blob/main/diagramas/diagrama-entidad-relacion-inicial.puml"
    click BIS1 "https://github.com/eitan-wajsberg/tp-gdd-2024-2c/blob/main/data/script_creación_BI.sql"
    click BIS2 "https://github.com/eitan-wajsberg/tp-gdd-2024-2c/blob/main/diagramas/diagrama-entidad-relacion-BI.puml"
    click F1 "https://github.com/eitan-wajsberg/tp-gdd-2024-2c/blob/main/Enunciado.pdf"
    click F2 "https://github.com/eitan-wajsberg/tp-gdd-2024-2c/blob/main/Estrategia.pdf"

    classDef source fill:#f9e79f,stroke:#d35400,stroke-width:2px;
    classDef process fill:#aed6f1,stroke:#2980b9,stroke-width:2px;
    classDef component fill:#d5f5e3,stroke:#27ae60,stroke-width:2px;
    classDef database fill:#fcf3cf,stroke:#f1c40f,stroke-width:2px;
    classDef doc fill:#e8daef,stroke:#8e44ad,stroke-width:2px;
```
