“Create a layered web app package diagram with routes, application services, domain logic, infrastructure adapters, and dependencies.”
Leggi le decisioni che ne stanno alla base.
Route packages invoke application services.
Business objects remain independent of delivery details.
Persistence and email sit in infrastructure.
Dependencies should point inward where possible.
Use to review module boundaries and communication paths in a web application.
Sfoglia tutti i modelli di tipo diagramma delle classi UML →
Domande frequenti
What is a layered package diagram?
It groups a system by architectural layer and shows how one layer depends on another.
Where do repositories belong?
They are usually infrastructure concerns, even when an interface is referenced by application or domain code.
How detailed should it be?
Show important boundaries and dependencies, not every implementation class.