Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-b-terms-and-definitions:u:uml [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:u:uml to dido:99_annexes:annex-b-terms-and-definitions:u:uml nick_dido | dido:99_annexes:annex-b-terms-and-definitions:u:uml [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Unified Modeling Language (UML) ====== | ====== Unified Modeling Language (UML) ====== | ||
| - | [[dido:99_annexes: | + | [[dido: |
| ===== Discussion ===== | ===== Discussion ===== | ||
| - | The Unified Modeling Language (UML) is a general-purpose | + | The Unified Modeling Language (UML) is a general-purpose |
| UML supports the representation of concerns such as: | UML supports the representation of concerns such as: | ||
| Line 20: | Line 20: | ||
| * Relationships among model elements | * Relationships among model elements | ||
| - | UML defines a modelling | + | UML defines a modeling |
| - | UML also provides a foundation for profiles that specialise | + | UML also provides a foundation for profiles that specialize |
| ===== Definition ===== | ===== Definition ===== | ||
| - | // | + | // |
| ===== Source ===== | ===== Source ===== | ||
| Line 41: | Line 41: | ||
| ===== Example ===== | ===== Example ===== | ||
| - | A software architect may use a UML component diagram to represent software components and their provided and required interfaces, and use an activity diagram to represent the flow of behaviour | + | A software architect may use a UML component diagram to represent software components and their provided and required interfaces, and use an activity diagram to represent the flow of behavior |
| ---- | ---- | ||
| <WRAP centeralign> | <WRAP centeralign> | ||