Application Responsibility Matrix¶
Each UC-BoK application archetype owns one or more Business Objects and consumes services from other applications. Ownership means the application is the system of record for that object's lifecycle.
Source: catalogs/applications.yaml
| Application | Classification | Owns | Consumes |
|---|---|---|---|
| OMS | System of Record | Order | Customer, Inventory, Payment |
| SIM | System of Record | Inventory, Reservation | Order |
| Payment Hub | Platform | Payment | Order |
| WMS | System of Record | Stock Movement, Picking Task | Order, Inventory |
| Loyalty Platform | System of Record | Loyalty Member | Customer, Order |
| CRM | System of Record | Customer, Consent | — |
| eCommerce Platform | System of Engagement | Basket | Customer, Order, Inventory |
| POS | System of Engagement | — | Order, Customer, Payment, Inventory |
| Clienteling App | System of Engagement | Clienteling Session | Customer, Order |
| Promotion Engine | System of Intelligence | Promotion | Customer, Order |
| OMS (Orchestration) | System of Intelligence | — | Order, Fulfillment |
Ownership Rules¶
- Every Business Object SHALL have a single owning application.
- Applications MAY consume objects owned by other applications via published services.
- Ownership SHALL NOT be duplicated across applications.
- The owning application is the authoritative source of truth for the object's lifecycle state.
References¶
catalogs/applications.yamlcatalogs/business-objects/- UCBOK-011 — Application Ontology Specification