|
**Sources:** http://www.omg.org/spec/UML/2.5 (Starting at PDF page 693)
|
|
**Sources:** http://www.omg.org/spec/UML/2.5 (Starting at PDF page 693)
|
|
|
|
|
|
# Usage Scenarios
|
|
# Usage Scenarios
|
|
The **deployment diagram** is used to describe deployment relationships between artifacts and targets, i.e. which target deploys which artifact. We distinguish *instance* and *type* level deployment relationships (p. 694, first paragraph).
|
|
The **deployment diagram** is used to describe deployment relationships between artifacts and targets, i.e. which target deploys which artifact. We distinguish *instance* and *type* level deployment relationships (l-d-r) (p. 694, first paragraph). Instance l-d-r show the deployment for actual instances of nodes, e.g.
|
|
|
|
|
|
---
|
|
---
|
|
|
|
|
... | @@ -9,11 +9,10 @@ The **deployment diagram** is used to describe deployment relationships between |
... | @@ -9,11 +9,10 @@ The **deployment diagram** is used to describe deployment relationships between |
|
Below you can find two different approaches for modelling a deployment of the previously defined [component diagram](https://git.informatik.uni-kiel.de/ag-se/teaching-public/wikis/uml/component-diagram).
|
|
Below you can find two different approaches for modelling a deployment of the previously defined [component diagram](https://git.informatik.uni-kiel.de/ag-se/teaching-public/wikis/uml/component-diagram).
|
|
|
|
|
|
## Single server (black box) deployment
|
|
## Single server (black box) deployment
|
|

|
|

|
|
|
|
|
|
## Multi server (detailed) deployment
|
|
## Multi server (detailed) deployment
|
|

|
|

|
|
|
|
|
|
|
|
|
|
|
|
|
|
TODO (Besprechen):
|
|
TODO (Besprechen):
|
... | | ... | |