# gims-inc/dummy_banking_sys architecture

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

## Overview

##### Main Components
- Core Banking System (Engine): Represented by your current C code (sys.c) that handles essential banking operations and file interactions.
- API Layer (Planned): A component that will later expose banking functionalities programmatically. Although not yet implemented, include it to show how it will interface with the core banking system.
- User Interfaces (Future Enhancements):
– Terminal UI: The initial UI which will use command-line interactions.
– Desktop UI: A planned graphical user interface for desktop applications.
– Web UI: An additional planned UI using web technologies.
- Data Handling/Storage: Even though simple file handling is in place, include a component for data storage representing how file handling is used to persist banking data.

##### Architectural Patterns and Design Principles
- Separation of Concerns: Clearly distinguish between the UI components, the API layer, business logic (Core Banking Engine), and the data persistence mechanisms.
- Modularity: Highlight that the system is being developed in branches where each branch will tackle a specific programming aspect (e.g., one branch for file handling improvements, another for dynamic linking).

##### Technologies and Frameworks
– Standard C libraries for file handling and terminal operations.
– Possible GUI frameworks for the desktop UI.
– Web frameworks/servers (or interfacing with them) for the eventual web UI.
- Mention any build tools or compilation techniques, if applicable, especially when you retain multiple branches focusing on different C concepts (like dynamic linking).

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% Current Implementation
    subgraph "Current Implementation"
        A["Core Banking Engine (C)"]:::core
        B["Executable Banking System"]:::core
        C["Data Storage (File Handling)"]:::storage
    end

    %% API and UI Layers
    subgraph "API and UI Layers (Planned/Implemented)"
        D["Planned API Layer"]:::api
        E["UI – Terminal (Implemented)"]:::ui
        F["UI – Desktop (Planned)"]:::ui
        G["UI – Web (Planned)"]:::ui
    end

    %% Connections among UI and API
    E -->|"sendsRequest"| D
    F -->|"sendsRequest"| D
    G -->|"sendsRequest"| D
    
    %% Connection from API to Core System
    D -->|"calls"| A

    %% Data persistence relation
    A -->|"persistsData"| C

    %% Show compilation flow from core engine to executable
    A -->|"compiledInto"| B

    %% Click Events
    click A "https://github.com/gims-inc/dummy_banking_sys/blob/master/sys.c"
    click B "https://github.com/gims-inc/dummy_banking_sys/tree/master/sys"

    %% Styles
    classDef core fill:#FFCCCB,stroke:#333,stroke-width:2px;
    classDef storage fill:#ADD8E6,stroke:#333,stroke-width:2px;
    classDef api fill:#FFFACD,stroke:#333,stroke-width:2px;
    classDef ui fill:#98FB98,stroke:#333,stroke-width:2px;
```
