The request
“Create an e-commerce package diagram with web, catalog, checkout, orders, and payments packages and their dependencies.”
Then tryAdd an inventory package.Change PaymentGateway to StripeAdapter.
What is in this drawing
Read the decisions behind it.
01Group by responsibility
Keep UI, catalog, checkout and payment concerns separate.
02Expose dependencies
Show which package calls another.
03Protect payment integration
Isolate the external gateway behind its package.
04Avoid implementation detail
Keep classes as package representatives.
Use for architecture discussions before drilling into a class or component diagram.
More like this
Other examples in this family.
FAQ
Common questions
What belongs in a package diagram?
Major modules, namespaces or layers and the dependencies between them.
Why use representative classes?
They make the responsibility of a package clear without turning the diagram into a full class model.
What does a dashed arrow mean?
It indicates a dependency: one package uses or relies on another.