uml/deployment-diagram.md

@@ -8,14 +8,17 @@ The type level deployment illustrates relationships between "kinds" or types of
 
 <br />
 
-The introduced (abstract) classes  *DeploymentArtifact* and *DeploymentTarget* (elements of the meta model) are extended by *Node* and *Artifact* respectively. In terms of modeling particular deployment diagrams (as shown below), we are mostly talking about *Nodes*, *Artifacts* and *CommunicationPaths* (associations between *Nodes* and *Artifacts* for exchanging signals and messages). The *Node* class is once more extended by *Devices* and *ExecutionEnvironments*. The *Device* stereotype is used for physical machines such as a server upon which *Artifacts* may be deployed. An *ExecutionEnvironment* is as its name implies an execution (typically software) environment for deploying *Components* in the form of the previously mentioned *Artifacts* (p. 698, second paragraph).
+The introduced (abstract) classes  *DeploymentArtifact* and *DeploymentTarget* (elements of the meta model) are extended by *Node* and *Artifact* respectively. In terms of modeling particular deployment diagrams (as shown below), we are mostly talking about *Nodes*, *Artifacts* and *CommunicationPaths* (associations between *Nodes* for exchanging signals and messages). The *Node* class is once more extended by *Devices* and *ExecutionEnvironments*. The *Device* stereotype is used for physical machines such as a server upon which *Artifacts* may be deployed. An *ExecutionEnvironment* is as its name implies an execution (typically software) environment for deploying *Components* in the form of the previously mentioned *Artifacts* (p. 698, second paragraph).
 
 
-# Obligations for the lectures and the final exam in "Softwaretechnik" (Tips for Modeling)
-- Nur type level
-- ExecutionEnvironment kann sehr fein granular geschachtelt werden indem neue Stereotypen dafür genutzt werden. In unserem Kontext nicht weiter notwendig.
-- Wann Kommunikationspfad zwischen Env - Device, Device - Device, Env - Env?
-- Komponenten werden als manifestierende Artefakte umgesetzt - Namenskonvention für Komponente -> Artefakt
+# Obligations for the lectures / exercises and the final exam in "Softwaretechnik" (Tips for Modeling)
+- Only use type level deployment diagrams, thereby we define a common ground and reduce the revision effort.
+
+- Sometimes you will see greatly nested *ExecutionEnvironments*. The nesting itself is UML-conform, but may introduce more complexity, which might be redundant in many cases (such as operating systems). Thus, we ask you to stay close to the tasks. Furthermore, every *Artifact* must be deployed inside of at least one *ExecutionEnvironment*.
+
+- *Artifacts* manifest [*Components*](https://git.informatik.uni-kiel.de/ag-se/teaching-public/wikis/uml/component-diagram). Use similar names for *Artifacts* and *Components*, such that one can see the Manifestation relationships.
+
+- *CommunicationPaths* illustrate the connection between *Nodes*, i.e. *Devices* and *ExecutionEnvironments*. Use a high-layer OSI model protocol (preferably layer seven) for this association and add detailed information in brackets (as shown below). Don't forget multiplicities / cardinalities.
 
 
 # Deployments