# shakeenacampbell/analytical_projects architecture

> Architecture diagram of the GitHub repository shakeenacampbell/analytical_projects, 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/shakeenacampbell/analytical_projects
- Repository: https://github.com/shakeenacampbell/analytical_projects

## Overview

##### Main Components
- Data Source(s) (if applicable): Although there isn’t an explicit raw data file in the repository, indicate that there may be external data sources feeding into the analytical process.
- SQL Processing Component: Represent the D205_SQL.sql file as the component that executes data extraction or transformation tasks.
- Analysis & Visualization Notebooks: Represent the Jupyter notebooks (D207_project.ipynb and d206_project_final.ipynb) as the interactive environments where data analysis, visualization, and further processing occur.
- Optional: A component for Project Documentation/Management can be noted, referencing the README and LICENSE files.

##### Relationships
- From the SQL component, indicate that the processed or aggregated data is then utilized by the notebooks for further analysis and visualization.
- Optionally, highlight that the outputs (results, visualizations, insights) from the notebooks could be documented and refined for iterative project development.

##### Architectural Patterns and Design Principles
- That the notebooks serve as an interactive layer for experimentation, exploration, and presentation unlike a static or production system.
- If applicable, mention that any external data inputs or additional sources should be clearly interfaced with the SQL processing component.

##### Relevant Technologies
- Jupyter Notebook: As the platform for interactive analysis and code experimentation.
- SQL: For data manipulation or querying which feeds into the analytical process.
- (Optionally) Python libraries: Although not explicitly listed, assume common analytical libraries (e.g., pandas, matplotlib) might be used within the notebooks.

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Data Acquisition/Storage Layer
    subgraph "Data Acquisition/Storage"
        A["External Data Source"]:::datasource
    end

    %% Data Processing Layer
    subgraph "Data Processing"
        B["SQL Processing"]:::sql
    end

    %% Analysis & Visualization Layer
    subgraph "Analysis & Visualization"
        C["Interactive Notebook (Project 1)"]:::notebook
        D["Interactive Notebook (Project 2)"]:::notebook
    end

    %% Project Management/Documentation Layer
    subgraph "Project Management"
        E["README"]:::doc
        F["LICENSE"]:::doc
    end

    %% Data Flow Connections
    A -->|"raw-data"| B
    B -->|"processed-data"| C
    B -->|"processed-data"| D
    C -->|"results"| E
    C -->|"results"| F
    D -->|"results"| E
    D -->|"results"| F

    %% Click Events
    click B "https://github.com/shakeenacampbell/analytical_projects/blob/main/D205_SQL.sql"
    click C "https://github.com/shakeenacampbell/analytical_projects/blob/main/D207_project.ipynb"
    click D "https://github.com/shakeenacampbell/analytical_projects/blob/main/d206_project_final.ipynb"
    click E "https://github.com/shakeenacampbell/analytical_projects/blob/main/README.md"
    click F "https://github.com/shakeenacampbell/analytical_projects/tree/main/LICENSE"

    %% Styles
    classDef datasource fill:#F4A261,stroke:#000,stroke-width:2px;
    classDef sql fill:#6BAED6,stroke:#000,stroke-width:2px;
    classDef notebook fill:#74C476,stroke:#000,stroke-width:2px;
    classDef doc fill:#BDBDBD,stroke:#000,stroke-width:2px;
```
