Standards families
UML package and profile diagrams
Packages grouping model elements with imports and merges, and profiles declaring stereotypes that extend the metamodel.
uml.structure@2New DDN source
Why use it?
Large models fail at the boundaries between teams; packages declare those boundaries and who depends on them.
When it helps
Partitioning a big model, or documenting a domain-specific UML extension.
How to read it
- A folder shape is a package; dashed arrows are imports/merges with direction.
- In the profile variant, stereotypes and tagged values extend, never replace, the base metaclass.
What you need
- The relevant UML package or profile definitions
- Their declared dependencies
- The intended profile rules
Things to check
- Do not let imports form a cycle — that is one package wearing two hats.
- A stereotype without a base metaclass is undefined.
Scope of this diagram
Declared packaging and profiling; element ownership is validated, code packaging is not implied.
Work with the converted example
- Open the viewer and select
packages. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.