# pedro-barbier/t1-gcs architecture

> Architecture diagram of the GitHub repository pedro-barbier/t1-gcs, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-05-15). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/pedro-barbier/t1-gcs
- Repository: https://github.com/pedro-barbier/t1-gcs

## Overview

1. **What this repo is**
   - This is a small **Java SE application** for **medical exam authorization management**.
   - The codebase is organized into a **startup entrypoint**, an **application/service layer**, and a **domain model layer**.

2. **Entrypoint and bootstrapping**
   - `src/Main.java` is the execution entrypoint.
   - Its role is likely limited to starting the application and delegating control to `app/Sistema.java`.

3. **Application orchestration layer**
   - `src/app/Sistema.java` appears to be the main coordinator of use cases.
   - It likely handles the overall flow: user interaction, dispatching operations, and coordinating model classes.
   - This is the closest thing to an application controller/facade in the repo.

4. **Core domain entities**
   - `modelo/Usuario.java` is the base user abstraction.
   - `Administrador.java`, `Medico.java`, and `Paciente.java` represent the concrete actor types in the system.
   - The architecture suggests inheritance or specialization around a shared user model.

5. **Authorization domain**
   - `modelo/AutorizacaoExame.java` is the central business object: a record of an exam authorization.
   - It likely connects a patient, a doctor, an exam type, and status/date information.
   - `modelo/TipoExame.java` defines the supported exam categories used by the authorization flow.

6. **In-memory collection/registry classes**
   - `modelo/Usuarios.java` and `modelo/Autorizacoes.java` look like container or repository-style classes.
   - They probably manage collections, searches, listings, and updates for users and authorizations.
   - This implies **in-memory state management**, not a database-backed architecture.

7. **Validation boundary**
   - `modelo/ValidadorDeDados.java` centralizes input and business-rule checks.
   - This class is likely used before creating users or authorizations to prevent invalid state from reaching the domain objects.
   - It forms an important boundary between raw input and trusted model data.

8. **Statistics and reporting**
   - `modelo/Estatisticas.java` is a dedicated reporting/analytics component.
   - It likely computes counts, summaries, or usage metrics over the authorization data.
   - This indicates a secondary read-oriented subsystem separate from the core write flow.

9. **Typical data flow**
   - A request enters through `Main` and is handled by `Sistema`.
   - `Sistema` validates data, creates or updates domain objects, and stores them through `Usuarios` or `Autorizacoes`.
   - Reporting requests read from the same in-memory collections and are summarized by `Estatisticas`.

10. **Important architectural boundaries**
   - The repo does **not** show persistence, web, API, or external-service integration.
   - All state appears to live inside the process, which keeps the architecture simple and self-contained.
   - The main separation is between **orchestration (`app`)** and **domain/data structures (`modelo`)**.

11. **What to show in an architecture diagram**
   - One entry node: `Main`.
   - One orchestration box: `Sistema`.
   - One domain cluster: `Usuario` hierarchy, `AutorizacaoExame`, `TipoExame`.
   - One storage/collection cluster: `Usuarios`, `Autorizacoes`.
   - One rules/analytics cluster: `ValidadorDeDados`, `Estatisticas`.
   - Arrows should show `Sistema` depending on all model components, with collections holding the system’s current state.

Main entry points: [`Sistema de Autorização de Exames Médicos/src/app/Sistema.java`](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/app/Sistema.java) (Sistema), [`Sistema de Autorização de Exames Médicos/src/modelo/Usuario.java`](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/Usuario.java) (Usuario), [`Sistema de Autorização de Exames Médicos/src/modelo/Estatisticas.java`](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/Estatisticas.java) (Estatisticas), [`Sistema de Autorização de Exames Médicos/src/modelo/Usuarios.java`](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/Usuarios.java) (Usuarios)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_g1["Bootstrap"]
  node_n1(("Main<br/>entrypoint<br/>[Main.java]"))
end

subgraph group_g2["Orchestration"]
  node_n2["Sistema<br/>orchestrator<br/>[Sistema.java]"]
end

subgraph group_g3["Domain"]
  node_n3["Usuario<br/>base entity<br/>[Usuario.java]"]
  node_n4["Administrador<br/>role entity<br/>[Administrador.java]"]
  node_n5["Medico<br/>role entity<br/>[Medico.java]"]
  node_n6["Paciente<br/>role entity<br/>[Paciente.java]"]
  node_n7["AutorizacaoExame<br/>domain record"]
  node_n8{{"TipoExame<br/>enum-like type<br/>[TipoExame.java]"}}
end

subgraph group_g4["State"]
  node_n9[("Usuarios<br/>user registry<br/>[Usuarios.java]")]
  node_n10[("Autorizacoes<br/>authorization registry<br/>[Autorizacoes.java]")]
end

subgraph group_g5["Rules and Reports"]
  node_n11["ValidadorDeDados<br/>validation service"]
  node_n12["Estatisticas<br/>reporting service<br/>[Estatisticas.java]"]
end

node_n1 -->|"starts"| node_n2
node_n2 -->|"validates"| node_n11
node_n2 -->|"manages users"| node_n9
node_n2 -->|"manages auths"| node_n10
node_n2 -->|"reports"| node_n12
node_n2 -->|"creates"| node_n7
node_n2 -->|"uses"| node_n8
node_n2 -->|"uses"| node_n3
node_n3 -->|"specializes"| node_n4
node_n3 -->|"specializes"| node_n5
node_n3 -->|"specializes"| node_n6
node_n10 -->|"stores"| node_n7
node_n9 -->|"stores"| node_n3
node_n12 -->|"reads"| node_n10
node_n12 -->|"reads"| node_n9

click node_n1 "https://github.com/pedro-barbier/t1-gcs/blob/master/Sistema de Autorização de Exames Médicos/src/Main.java"
click node_n2 "https://github.com/pedro-barbier/t1-gcs/blob/master/Sistema de Autorização de Exames Médicos/src/app/Sistema.java"
click node_n3 "https://github.com/pedro-barbier/t1-gcs/blob/master/Sistema de Autorização de Exames Médicos/src/modelo/Usuario.java"
click node_n4 "https://github.com/pedro-barbier/t1-gcs/blob/master/Sistema de Autorização de Exames Médicos/src/modelo/Administrador.java"
click node_n5 "https://github.com/pedro-barbier/t1-gcs/blob/master/Sistema de Autorização de Exames Médicos/src/modelo/Medico.java"
click node_n6 "https://github.com/pedro-barbier/t1-gcs/blob/master/Sistema de Autorização de Exames Médicos/src/modelo/Paciente.java"
click node_n7 "https://github.com/pedro-barbier/t1-gcs/blob/master/Sistema de Autorização de Exames Médicos/src/modelo/AutorizacaoExame.java"
click node_n8 "https://github.com/pedro-barbier/t1-gcs/blob/master/Sistema de Autorização de Exames Médicos/src/modelo/TipoExame.java"
click node_n9 "https://github.com/pedro-barbier/t1-gcs/blob/master/Sistema de Autorização de Exames Médicos/src/modelo/Usuarios.java"
click node_n10 "https://github.com/pedro-barbier/t1-gcs/blob/master/Sistema de Autorização de Exames Médicos/src/modelo/Autorizacoes.java"
click node_n11 "https://github.com/pedro-barbier/t1-gcs/blob/master/Sistema de Autorização de Exames Médicos/src/modelo/ValidadorDeDados.java"
click node_n12 "https://github.com/pedro-barbier/t1-gcs/blob/master/Sistema de Autorização de Exames Médicos/src/modelo/Estatisticas.java"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_n1 toneBlue
class node_n2 toneAmber
class node_n3,node_n4,node_n5,node_n6,node_n7,node_n8 toneMint
class node_n9,node_n10 toneRose
class node_n11,node_n12 toneIndigo
```

## Components

### Bootstrap

Application entrypoint and startup coordination.

- [Main](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/Main.java): entrypoint · Starts the application and delegates to the system coordinator. · `Sistema de Autorização de Exames Médicos/src/Main.java`

### Orchestration

Main application flow and use-case coordination.

- [Sistema](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/app/Sistema.java): orchestrator · Central application facade that coordinates flows and domain interactions. · `Sistema de Autorização de Exames Médicos/src/app/Sistema.java`

### Domain

Core business entities and value types.

- [Usuario](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/Usuario.java): base entity · Shared user abstraction for system actors. · `Sistema de Autorização de Exames Médicos/src/modelo/Usuario.java`
- [Administrador](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/Administrador.java): role entity · Administrative user specialization. · `Sistema de Autorização de Exames Médicos/src/modelo/Administrador.java`
- [Medico](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/Medico.java): role entity · Doctor user specialization. · `Sistema de Autorização de Exames Médicos/src/modelo/Medico.java`
- [Paciente](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/Paciente.java): role entity · Patient user specialization. · `Sistema de Autorização de Exames Médicos/src/modelo/Paciente.java`
- [AutorizacaoExame](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/AutorizacaoExame.java): domain record · Core authorization record linking the exam workflow data. · `Sistema de Autorização de Exames Médicos/src/modelo/AutorizacaoExame.java`
- [TipoExame](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/TipoExame.java): enum-like type · Supported exam categories used by authorization logic. · `Sistema de Autorização de Exames Médicos/src/modelo/TipoExame.java`

### State

In-memory registries for users and authorizations.

- [Usuarios](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/Usuarios.java): user registry · In-memory collection and lookup service for users. · `Sistema de Autorização de Exames Médicos/src/modelo/Usuarios.java`
- [Autorizacoes](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/Autorizacoes.java): authorization registry · In-memory collection and lookup service for authorizations. · `Sistema de Autorização de Exames Médicos/src/modelo/Autorizacoes.java`

### Rules and Reports

Validation and reporting components.

- [ValidadorDeDados](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/ValidadorDeDados.java): validation service · Checks input and business rules before objects are created or updated. · `Sistema de Autorização de Exames Médicos/src/modelo/ValidadorDeDados.java`
- [Estatisticas](https://github.com/pedro-barbier/t1-gcs/blob/HEAD/Sistema%20de%20Autoriza%C3%A7%C3%A3o%20de%20Exames%20M%C3%A9dicos/src/modelo/Estatisticas.java): reporting service · Computes summaries and usage metrics over authorization data. · `Sistema de Autorização de Exames Médicos/src/modelo/Estatisticas.java`

## Connections

- Main → Sistema: starts · Main hands control to the application coordinator.
- Sistema → ValidadorDeDados: validates · System validates incoming data before domain changes.
- Sistema → Usuarios: manages users · Coordinates user creation, search, and listing through the registry.
- Sistema → Autorizacoes: manages auths · Coordinates authorization creation, updates, and retrieval.
- Sistema → Estatisticas: reports · Requests summaries and statistics from the reporting component.
- Sistema → AutorizacaoExame: creates · Builds authorization records as part of core use cases.
- Sistema → TipoExame: uses · Relies on exam types when classifying authorizations.
- Sistema → Usuario: uses · Operates on the shared user abstraction.
- Usuario → Administrador: specializes · Administrator is a concrete user role.
- Usuario → Medico: specializes · Medico is a concrete user role.
- Usuario → Paciente: specializes · Paciente is a concrete user role.
- Autorizacoes → AutorizacaoExame: stores · Authorization registry holds current authorization records.
- Usuarios → Usuario: stores · User registry holds user objects and role instances.
- Estatisticas → Autorizacoes: reads · Statistics are computed from authorization data.
- Estatisticas → Usuarios: reads · Statistics may also use user registry data for summaries.
