# jaftdelgado/italiapizza-client architecture

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

- Interactive diagram: https://gitdiagram.com/jaftdelgado/italiapizza-client
- Repository: https://github.com/jaftdelgado/italiapizza-client

## Overview

##### Project type and purpose
- This is a Windows desktop client for the “Italia Pizza” restaurant management system.
- It implements a Client–Server architecture using WPF on the client side and WCF for communication with a separate server component.

##### File structure
- A WPF solution (XAML views, view‐models, code‐behind)
- An App.config for WCF endpoint configuration
- Service proxy/stubs generated for the WCF interfaces

##### Review README insights
- Technology stack: C#, .NET Framework, WPF, WCF
- Architecture: Cliente-Servidor
- Key features exposed by the client: staff management, order entry, inventory, reports, etc.
- Configuration: WCF service URL in App.config

##### Main components
a. Client Tier (this project)
- Presentation Layer
– WPF Views (XAML)
– ViewModels (MVVM pattern)
- Service Layer / Proxy
– Generated WCF client proxies
– WCF binding & endpoint config (from App.config)
b. Communication Channel
- WCF over HTTP/NetTCP (show binding type)
c. Server Tier (external)
- WCF Service Host
- Business Logic Layer
- Data Access Layer
- Database (e.g., SQL Server)
d. External Services (if any)
- Payment processor, report engine, authentication, etc. (if applicable)

##### Relationships and interactions
- Service Layer uses WCF channel to invoke operations on the remote WCF Service Host.
- WCF Service Host orchestrates calls into Business Logic, which accesses the Database.

##### Architectural patterns and design principles
- MVVM on the client (highlight separation of UI, state, and commands).
- Client–Server via WCF (clear boundary).
- Layered architecture on the server (Service → Business Logic → Data Access).

##### Technologies and frameworks
- Client: WPF (.NET Framework), MVVM, WCF Client Proxies
- Communication: WCF Bindings (specify HTTP or NetTCP)
- Server (to be depicted): WCF Service Library or Host, .NET Business Logic, ADO.NET/EF, SQL Server

## Diagram (Mermaid)

```mermaid
flowchart TD
    subgraph "Italia Pizza Client (WPF)"
        direction TB
        PD["Project Documentation"]:::doc
        VIEWS["WPF Views (XAML)"]:::client
        VMS["ViewModels"]:::client
        PROXY["IPizzaServiceClient (WCF Proxy)"]:::client
        CFG["App.config"]:::config
    end

    subgraph "Italia Pizza Server"
        direction TB
        HOST["WCF Service Host"]:::server
        BL["Business Logic Layer"]:::server
        DAL["Data Access Layer"]:::server
        DB["Database (SQL Server)"]:::database
    end

    PD --> VIEWS
    VIEWS -->|"DataBinding"| VMS
    VMS -->|"ServiceCalls"| PROXY
    CFG -->|"EndpointConfig"| PROXY
    PROXY -->|"WCF (HTTP/NetTCP)"| HOST
    HOST -->|"InvokeServices"| BL
    BL -->|"DataOperations"| DAL
    DAL -->|"Queries/Commands"| DB

    click PD "https://github.com/jaftdelgado/italiapizza-client/blob/main/README.md"

    classDef client fill:#ADD8E6,stroke:#333,stroke-width:1px
    classDef server fill:#90EE90,stroke:#333,stroke-width:1px
    classDef database fill:#FFEFDB,stroke:#333,stroke-width:1px
    classDef doc fill:#FFFFE0,stroke:#333,stroke-width:1px
    classDef config fill:#E6E6FA,stroke:#333,stroke-width:1px
```
