[[file:Nodes.PNG|thumb| right|300px240px|Two execution environments instances nested in a device instance (click to see larger version)]]In the [[Unified Modeling Language]] ,▼{{wikify}}
"A '''node ''' In the [[Unified Modeling Language]] (UML) is a computational resource upon which [[artifact_(UML)|artifact]]s may be deployed for execution. "<ref>[[UMLSuperstructure|UML Superstructure]], p. 210.</ref>▼▲[[file:Nodes.PNG|thumb|right|300px|Two execution environments instances nested in a device instance (click to see larger version)]]In the [[Unified Modeling Language]],
* < citeref idname= umlsuperstructure "OMG UML V2.1.2"> OMG (2008). ''[http://www.omg.org/spec/UML/2.1.2/Superstructure/PDF | OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2] '' p.199-210.</ citeref> ▼
<blockquote>
▲"A node is a computational resource upon which [[artifact_(UML)|artifact]]s may be deployed for execution."<ref>[[UMLSuperstructure|UML Superstructure]], p. 210.</ref>
</blockquote>
There are two types of nodes: ''device'' nodes and ''execution environments''.
"* A devicedives isrepresent hardware devices: a physical computational resource with processing capability upon which [[Artifact_(UML)|artifact]]s may be deployed for execution. Devices may be complex (i.e., they may consist of other devices). "<ref >[[#umlsuperstructure| name= "OMG UML Superstructure]], pV2. 2061. <2"/ ref> ▼The former represent hardware devices:
"* An execution environmentenvironments represent software containers (such as operating systems, JVM, servlet/EJB containers, application servers, portal servers etc.) This is a node that offers an execution environment for specific types of components that are deployed on it in the form of deployable artifacts.<ref >[[#umlsuperstructure|UML Superstructure]],name= p"OMG UML V2. 2071. <2"/ ref> ▼<blockquote>
▲"A device is a physical computational resource with processing capability upon which [[Artifact_(UML)|artifact]]s may be deployed for execution. Devices may be complex (i.e., they may consist of other devices)."<ref>[[#umlsuperstructure|UML Superstructure]], p.206.</ref>
</blockquote>
"Execution environments can be nested. Nodes can be interconnected through communication paths to define network structures. A ''communication path '' is an "association between two DeploymentTargets, through which they are able to exchange signals and messages" .<ref >[[#umlsuperstructure|UML Superstructure]],name= p"OMG UML V2. 1991. <2"/ ref> ▼The latter represent software containers (such as operating systems, JVM, servlet/EJB containers, application servers, portal servers etc.)
<blockquote>
▲"An execution environment is a node that offers an execution environment for specific types of components that are deployed on it in the form of deployable artifacts.<ref>[[#umlsuperstructure|UML Superstructure]], p.207.</ref>
</blockquote>
Execution environments can be nested.
Nodes can be interconnected through communication paths to define network structures:
<blockquote>
▲"A communication path is an association between two DeploymentTargets, through which they are able to exchange signals and messages"<ref>[[#umlsuperstructure|UML Superstructure]], p.199.</ref>
</blockquote>
When modeling devices, it is possible to model them in several different ways:
Use tagged values to specify characteristics of devices / execution environments, for instance "Memory=2GB", "Disk Space=32GB", "Version=2.5.1".
==NotesReferences==
{{reflist}}
{{verify}}
==References==
▲* <cite id=umlsuperstructure>[http://www.omg.org/spec/UML/2.1.2/Superstructure/PDF|OMG Unified Modeling Language, Superstructure, V2.1.2]</cite>
{{UML}}
| 