Dependency Graph

zmscitizenview and refarch-gateway are built on top of zmscitizenapi, but they do not directly pull dependencies from it. Similarly, while zmscitizenapi sends requests to zmsapi, zmsapi is not a direct dependency of zmscitizenapi.

The graph also shows the runtime services every deployment depends on:

• eappointment-php-base — pre-built PHP runtime images for every PHP module (see PHP Base Images).
• Digital Citizen Service (DBS) — Munich's open-source citizen identity broker for BundID, BayernID and Elster, reached at the refarch-gateway layer (see it-at-m/dbs).
• zmsautomation — Maven-based acceptance tests on ATAF (Agile Test Automation Framework; artifacts de.muenchen.ataf): Cucumber scenarios with REST Assured for API tests and Selenium (via ATAF web) for UI tests. Not a Composer dependency of the PHP modules; it drives HTTP/browser flows against deployed instances (see zmsautomation/README.md).

Reading the edges

• Solid arrow (A --> B): A has B as a code dependency (composer).
• Dashed arrow (A -.-> B): build / integration dependency. A is built and deployed on top of B but does not pull it as a code dependency.
• Thick arrow (A ==> B): runtime / infrastructure dependency. A talks to B at runtime, or B provides A's runtime environment.

In the Test automation subgraph only, the dashed edge ataf -.-> zmsautomation reads as framework → consumer (ATAF supplies Cucumber plus REST Assured for API and Selenium for UI to zmsautomation), not as the Composer-style “A built on B” rule above.

%%{init: {"flowchart": {"defaultRenderer": "elk"}} }%%
graph TD;
    %% Code dependencies (composer)
    zmsapi --> zmsslim & zmsclient & zmsdldb & zmsdb & zmsentities;
    zmsadmin --> mellon & zmsclient & zmsslim & zmsentities;
    zmscalldisplay --> mellon & zmsclient & zmsentities & zmsslim;
    zmsstatistic --> mellon & zmsentities & zmsslim & zmsclient;
    zmsmessaging --> mellon & zmsclient & zmsentities & zmsslim;
    zmsticketprinter --> mellon & zmsclient & zmsentities & zmsslim;

    zmsdb --> zmsentities & zmsdldb & mellon;
    zmsclient --> zmsentities & zmsslim & mellon;
    zmsentities --> mellon;
    zmsslim --> mellon;

    zmscitizenapi --> mellon & zmsslim & zmsclient & zmsentities;

    %% Build / integration dependencies (dashed)
    zmscitizenapi -.-> zmsapi;
    refarch-gateway -.-> zmscitizenapi;
    zmscitizenview -.-> refarch-gateway;

    %% Runtime / external services (thick)
    refarch-gateway ==>|citizen identity| dbs;
    phpbase ==>|PHP runtime image| zms_modules;

    %% Test automation: ATAF supplies the stack; zmsautomation consumes it (targets: see section below)
    ataf -.-> zmsautomation;

    %% Subgraphs
    subgraph refarch [refarch]
        style refarch stroke-dasharray: 5
        refarch-gateway
        zmscitizenview
    end

    subgraph zms_modules [ZMS PHP Modules]
        style zms_modules stroke-dasharray: 5, 5, 1, 5
        zmsapi
        zmsadmin
        zmscalldisplay
        zmsstatistic
        zmsmessaging
        zmsticketprinter
        zmsdb
        zmsclient
        zmsentities
        zmsslim
        zmsdldb
        mellon
        zmscitizenapi
    end

    subgraph runtime [Runtime / external services]
        style runtime stroke-dasharray: 2, 4
        dbs["Digital Citizen Service (DBS)<br>BundID · BayernID · Elster broker"]
    end

    subgraph foundation [Infrastructure foundation]
        style foundation stroke-dasharray: 2, 4
        phpbase["eappointment-php-base<br>PHP runtime images"]
    end

    subgraph testing [Test automation]
        style testing stroke-dasharray: 5
        ataf["ATAF<br>Maven · Cucumber<br>API: REST Assured<br>UI: Selenium"]
        zmsautomation
    end

    %% Styling
    classDef citizenapi fill:#e1f5fe,stroke:#01579b,stroke-width:2px;
    classDef gateway fill:#f3e5f5,stroke:#4a148c,stroke-width:2px;
    classDef citizenview fill:#e8f5e8,stroke:#1b5e20,stroke-width:2px;
    classDef runtimeSvc fill:#fff3e0,stroke:#e65100,stroke-width:2px;
    classDef infra fill:#e3f2fd,stroke:#0277bd,stroke-width:3px;
    classDef automation fill:#fce4ec,stroke:#880e4f,stroke-width:2px;

    class zmscitizenapi citizenapi;
    class refarch-gateway gateway;
    class zmscitizenview citizenview;
    class dbs runtimeSvc;
    class phpbase infra;
    class zmsautomation automation;
    class ataf automation;

Frontend vs Backend Modules

Frontend

• zmscitizenview: Vue3 citizen-facing booking frontend built on RefArch.
• refarch-gateway: frontend gateway/BFF layer used by zmscitizenview.
• zmsadmin: administration UI module (with backend/API integration).
• zmsstatistic: statistics/reporting UI module (with backend/API integration).
• zmscalldisplay: call display UI module.
• zmsticketprinter: ticket printer UI/runtime module.

zmscitizenview follows the RefArch reference architecture patterns and uses refarch-gateway as its gateway layer. This means requests from zmscitizenview are routed through refarch-gateway before they reach zmscitizenapi. For gateway behavior and security/routing details, see the RefArch API Gateway docs: RefArch API Gateway.

Backend APIs and Core Services

• zmscitizenapi: API layer for citizen booking flows, mapping backend entities into thinned frontend DTOs.
• zmsapi: core backend API for process, queue, appointment, and administration flows.
• zmsdb: database access/query layer for providers/requests/processes.
• zmsdldb: importer/transformer for external DLDB/SADB sources.
• zmsclient: HTTP/API client abstractions used between modules.
• zmsslim: shared Slim framework layer/helpers.
• zmsmessaging: messaging/notification backend module.
• mellon: shared base/library dependency used by multiple backend modules.

Shared Across Frontend-Facing and Backend PHP Modules

• zmsentities: shared domain/entity model used by both frontend-facing PHP modules and backend PHP modules.

Test automation

• zmsautomation: Maven module; REST Assured for API tests and Selenium (ATAF web) for UI tests, both driven by Cucumber under ATAF (de.muenchen.ataf). Not part of the Composer graph — it validates running deployments (CI zmsautomation-workflow, local zmsautomation-test). Typical targets include zmsapi, zmscitizenapi, and browser flows against zmsadmin, zmscitizenview, zmsstatistic, and refarch-gateway.

Runtime Services and Infrastructure

These are not pulled as code dependencies but are required at deploy/runtime.

• eappointment-php-base: pre-built PHP runtime images that every PHP module runs on. Detailed dependency view: PHP Base Images.
• Digital Citizen Service (DBS): Munich's open-source citizen identity broker for BundID, BayernID and Elster, integrated at the refarch-gateway layer ahead of zmscitizenapi for the citizen booking flow. See it-at-m/dbs.