Zum Hauptinhalt springen

Repository Conventions

🤖 Generated with Claude Code

⚠️ Not yet reviewed

Co-Authored-By: Claude (noreply@anthropic.com)

Orientation for new developers: what the repository prefixes mean and which project types exist. All repositories live in Azure DevOps under togethercca/tis-cca.

This document describes the naming scheme, not the full inventory. Which services actually run, and how heavily they are used, is covered by platform-usage-overview.md. How we work inside a repository — branches, commits, pull requests — is in git/.

Namespace Prefixes​

PrefixMeaningExamples
tis.gf.*Geschäftsfall framework — business processes toward insurers and customerstis.gf.api, tis.gf.smr5, tis.gf.soagfx, tis.gf.esign
tis.bestand.*Portfolio data managementtis.bestand.omdsexplorer, tis.bestand.klauselservice, tis.bestand.omdsdownload
tis.identity.*Identity and access managementtis.identity (IdentityServer), tis.identity.api, tis.identity.ovbselfservice
Tis.Partner.*Integrations with individual insurers (VU)Tis.Partner.UniqaIntegration, Tis.Partner.AllianzIntegration
Tis.Hosting.*Platform building blocks and librariesTis.Hosting.Extensions, Tis.Hosting.ApiGateway, Tis.Hosting.Dispatcher
Tis.Omds3.*Services around the OMDS3 standardTis.Omds3.DeepLink
tis-cca.*Organisation-wide repositories, not a single servicetis-cca.documentation, tis-cca.pipeline-templates, tis-cca.wiki

Further repositories follow none of these prefixes (tis.core, tis.userprofile, tis.volltextsuche, boa-api, tiscca.cads-parent, …).

Casing: capitalisation is historically inconsistent — Tis.Partner.UniqaIntegration next to tis.partner.VigIntegration, tis.bestand.omdsCollector next to tis.bestand.omdsdownload. A new repository MUST follow whichever casing already dominates its prefix.

Project Types​

Together Platform​

TypeDescriptionExamples
Internal API servicesREST APIs consumed only by other TOGETHER/TIS servicestis.identity.api, tis.userabgleich
Public API servicesREST APIs for partners, large customers and other software vendorstis.gf.api, boa-api
Web applicationsASP.NET Core with a frontendtis.identity (IdentityServer), tis.gf.wgp
Partner integrationsInsurer-specific integrations, used by API services as a backendTis.Partner.AllianzIntegration
LibrariesNuGet packages consumed by other servicesTis.Hosting.Extensions
ToolsCommand-line utilitiestis-secrets (in Tis.Hosting.Extensions)
Windows servicesBackground servicestis.volltextsuche.gf.import.service

API services use REST and OAuth2 throughout. Partner integrations additionally carry partner-specific OAuth2 flows and a reverse-proxy pattern.

CCA​

TypeDescriptionExamples
Desktop applications.NET Framework / WinForms, installed at the customerCCA9
Web applicationsWeb interfaces, either an add-on to CCA9 or standaloneCCAOnline

Where Does the Documentation Live?​

Application-specific documentation MUST live in that repository under docs/. Anything spanning several applications belongs here — see DOCUMENTATION-GUIDELINES.md in the repository root.