Standards families
UML component and composite structure
Components wired through provided and required ports, and the internal parts-and-connectors view of a structured classifier.
uml.composite@1New DDN source
Why use it?
Ports make interfaces explicit — the diagram says what may connect to what before the wiring exists.
When it helps
Component architecture, integration design, or explaining how a big part is built from smaller ones.
How to read it
- Ball-and-socket pairs are provided/required interfaces; assembly connectors join compatible pairs.
- In the structures variant, parts inside the boundary play roles in the whole.
What you need
- The components and parts
- The interfaces (provided and required)
- The connectors
Things to check
- Do not connect a required interface to another required one.
- A port without an interface type is a wish, not a contract.
Scope of this diagram
Declared structure with port compatibility validated; no deployment or runtime wiring is implied.
Work with the converted example
- Open the viewer and select
components. 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.