Node (UML): Difference between revisions

Revision as of 14:11, 26 January 2009

Latest revision as of 11:18, 10 June 2024

(25 intermediate revisions by 17 users not shown)

Line 1:

{{notability|date=October 2015}}

In [[Unified Modeling Language]],

{{Refimprove|date=February 2009}}

[[File:Nodes.PNG|thumb|240px|Two execution environments instances nested in a device instance]]

<blockquote>

A '''node'''<ref name=OMG>{{cite book

"A node is a computational resource upon which [[artifact]]s may be deployed for execution.

|chapter=Nodes

Nodes can be interconnected through communication paths to define network structures."<ref>[[UMLSuperstructure|UML Siperstructure]], p. 210.</ref>

|title=Unified Modeling Language 2.5.1

</blockquote>

|series=[[Object Management Group |OMG]] Document Number formal/2017-12-05

|date=December 2017

|publisher=[[Object Management Group]] Standards Development Organization (OMG SDO)

|page=387, 396, 403, 657

|url=https://www.omg.org/spec/UML/2.5.1/PDF

}}

</ref>

"Ain nodethe [[Unified Modeling Language]] (UML) is a computational resource upon which [[artifact (UML)|UML artifact]]s may be deployed for execution.<ref name=OMG/>

There are two types of nodes: ''device'' nodes and ''execution environments''.

* A device represents hardware devices: a physical computational resource with processing capability upon which [[Artifact (UML)|UML artifact]]s may be deployed for execution. Devices may be complex (i.e., they may consist of other devices).<ref name= "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] {{Webarchive|url=https://web.archive.org/web/20100923033721/http://www.omg.org/spec/UML/2.1.2/Superstructure/PDF |date=2010-09-23 }}'' p.199-210.</ref>

The former represent hardware devices:

<blockquote>

"A device is a physical computational resource with processing capability upon which artifacts 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>

The* laterAn representexecution environment represents [[software containerscontainer]]s (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 name= "OMG UML V2.1.2"/>

<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. 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>

Execution environments can be nested.

== Usage Tips==

Nodes are connected using communication paths:

<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>

==Usage Tips==

When modeling devices, it is possible to model them in several different ways:

Line 34 ⟶ 32:

Use tagged values to specify characteristics of devices / execution environments, for instance "Memory=2GB", "Disk Space=32GB", "Version=2.5.1".

==NotesReferences==

{{reflist}}

{{UML}}

==References==

* <cite id=umlsuperstructure>[http://www.omg.org/spec/UML/2.1.2/Superstructure/PDF|OMG Unified Modeling Language, Superstructure, V2.1.2]</cite>

In [[Category:Unified Modeling Language]],

{{uml-stub}}