Skip to content
Design structure matrix templates

DSM — Checkout Service Coupling

Sixteen services of a commerce platform taken in the alphabetical order the service registry lists them, where partitioning turns 23 backwards call dependencies into 4 and exposes a five-service checkout core — checkout, orders, inventory, fraud scoring, payments — that no deployment order can untangle.

Template previewDesign structure matrix
Commerce platform — service couplingComponent DSM · IR/FAD — read across a row for that element's inputs; marks above the diagonal are feedback.As declared23223233222322223332223222Analytics sink1Cart2Catalogue3Checkout4Config service5Feature flags6Fraud scoring7Fulfilment8Identity9Inventory10Notifications11Orders12Payments13Pricing engine14Recommendations15Search index16Analytics sinkCartCatalogueCheckoutConfig serviceFeature flagsFraud scoringFulfilmentIdentityInventoryNotificationsOrdersPaymentsPricing engineRecommendationsSearch indexPartitioned sequence2322323322232222333222322212Identity1Config service2Catalogue3Feature flags4Pricing engine5Cart6Checkout7Orders8Inventory9Fraud scoring10Payments11Fulfilment12Recommendations13Search index14Analytics sink15Notifications16IdentityConfig serviceCatalogueFeature flagsPricing engineCartCheckoutOrdersInventoryFraud scoringPaymentsFulfilmentRecommendationsSearch indexAnalytics sinkNotificationsinout0712251222424226233133213132403023 feedback marks reduced to 4 across 2 iteration blocks.16 components · 39 dependency marks · density 16% · 8 sequenced stages · largest block 5Sequence runs top-left to bottom-right; 4 remaining feedback marks sit inside the boxed blocks.Highest fan-out: Identity (feeds 7) · highest fan-in: Analytics sink (needs 4)Block 1 · positions 7–11 · Checkout, Orders, Inventory, Fraud scoring, PaymentsBlock 2 · positions 13–14 · Recommendations, Search indexdependencystrength 3feedback (rework)iteration blockdiagonal (self)

Make it your own.

title "Commerce platform — service coupling"
mode component
convention ir-fad

# Declared in the order the service registry lists them, which is
# alphabetical — a perfectly normal starting point and a terrible sequence.
components: Analytics sink, Cart, Catalogue, Checkout, Config service, Feature flags
components: Fraud scoring, Fulfilment, Identity, Inventory, Notifications, Orders
components: Payments, Pricing engine, Recommendations, Search index

Config service   <- Identity
Feature flags    <- Config service(2)
Catalogue        <- Config service, Identity
Pricing engine   <- Catalogue(3), Feature flags(2)
Inventory        <- Catalogue(2), Orders(3)
Cart             <- Catalogue(2), Pricing engine(3), Identity, Feature flags
Checkout         <- Cart(3), Pricing engine(2), Identity(2), Inventory(2)
Payments         <- Checkout(3), Fraud scoring(2), Identity
Fraud scoring    <- Identity(2), Orders(2), Payments(2)
Orders           <- Checkout(3), Payments(3)
Fulfilment       <- Orders(3), Inventory(2)
Notifications    <- Orders(2), Fulfilment(2), Identity
Search index     <- Catalogue(3), Inventory, Recommendations(2)
Recommendations  <- Search index(2), Orders(2), Catalogue
Analytics sink   <- Orders, Payments, Cart, Search index