CheckoutModel
ReceiptSelect a package, element or dashed arrow. Read the package nesting, name ownership and dependency direction.
Infrastructure «import» Application «access» Payments
domain order
Shop::Domain::OrderSelect an element or arrow to edit it.
Shop::Application::CheckoutServiceOwned memberShop::Domain::Inventory::Orderinventory order · Imported member · Available within this namespaceShop::Contracts::Payments::PaymentGatewayImported member · Available for re-exportShop::Domain::Inventory::StockItemImported member · Available within this namespaceShop::Domain::OrderShop::Domain::OrderPaymentGatewayShop::Contracts::Payments::PaymentGatewayStockItemShop::Domain::Inventory::StockItemPaymentGatewayShop::Contracts::Payments::PaymentGatewayThe check separates naming and reference issues from the architecture rules for this case.
The arrow runs from the client to the supplier. A plain dependency does not add names to the client namespace.
Select an element or arrow to edit it.
Shop::Application::CheckoutServiceOwned memberShop::Domain::Inventory::Orderinventory order · Imported member · Available within this namespaceShop::Domain::Inventory::StockItemImported member · Available within this namespaceShop::Domain::OrderShop::Domain::OrderPaymentGatewayShop::Contracts::Payments::PaymentGatewayStockItemShop::Domain::Inventory::StockItemPaymentGatewayShop::Contracts::Payments::PaymentGatewayThe class diagram uses Order and OrderLine to show types, attributes and relationships. The package diagram shows their owning namespaces.
Open the order class diagram ↗The component view shows the order service requiring the PaymentGateway interface, which the payment adapter provides. The package view places the interface type in the Payments namespace.
Open the order component diagram ↗ReceiptTaxSummaryThe dashed «merge» arrow goes from the receiving CheckoutModel to the merged SharedOrders package. In this distinct-name example, CheckoutModel gains TaxSummary and keeps Receipt.
This example combines distinct names. Full UML package merge also has matching and compatibility rules for same-name elements.
Booking and Support each own a Request type. The model needs to refer specifically to the booking request.