Skip to content

Business to infrastructure

Quick Summary

Business capabilities describe what an organization does, bounded contexts group the entities that belong together, and C4 software systems implement them. This page shows how all three layers connect -- so you can trace from a business question all the way down to the infrastructure that runs it.

Bounded Contexts

Bounded contexts group related business entities and show how data flows across domain boundaries. BelFoot FC has 13 bounded contexts -- see the full index in the Capability Map. Here is one -- Gameday Match/Event Delivery -- covering ticketing, access control, and event operations:

flowchart TB
    subgraph "Gameday Match/Event Delivery"
        MATCH[Match]
        EVENT[Event]
        TICKET[Ticket]
        SEASON_PASS[Season Pass]
        SEAT[Seat]
        ACCESS_BADGE[Access Badge]
        MATCHDAY_PLAN[Matchday Plan]
        SECURITY_DEPLOYMENT[Security Deployment]
        AWAY_TRIP[Away Trip]
        ESPORTS_EVENT[E-Sports Event]
    end

    EVENT --> |is a| MATCH
    TICKET --> |assigns| SEAT
    TICKET --> |for| EVENT
    SEASON_PASS --> |covers| SEAT
    MATCHDAY_PLAN --> |for| MATCH
    MATCHDAY_PLAN --> |includes| SECURITY_DEPLOYMENT
    ACCESS_BADGE --> |grants entry to| EVENT

Tracing a Business Question

"What systems are affected if we change our ticketing strategy?"

Start at the bounded context. Gameday Match/Event Delivery owns TICKET, SEASON_PASS, and MATCH. But tickets don't exist in isolation -- cross-context links show that CUSTOMER_PROFILE (from Customer/Fan Services) purchases tickets, and TRANSACTION (from Product Delivery) records the payment at the VENUE.

That tells you which software system implements this domain:

Ticketing Platform — Containers

And which infrastructure runs it -- the Ticketing Platform sits in the stadium data center because it cannot tolerate cloud round-trips during a match:

Production — On-Premise

One question, traced from business entity to bounded context to software system to container to infrastructure. That is the value of a connected model.

Organizational Groups

BelFoot FC organizes its 28 software systems into five departments. Each has its own system landscape view:

Ticketing, merchandise, CRM, sponsorship, fan engagement, and marketing.

Commercial Systems

Finance (SAP S/4HANA), HR, compliance, strategy, and external relations.

Corporate Systems

Identity management, integration platform, data platform, lakehouse, and AI/ML.

IT Systems

Stadium management, IoT sensors, cashless payment, logistics, and matchday coordination.

Operations Systems

Player performance analytics, medical records, and youth academy scouting.

Sporting Systems