Node is a computational resource upon which artifacts may be stored or deployed for execution. Think of a node as a logical container for Devices and System Software. Indeed at the highest level a node could represent some form of software or hardware resource. Nodes can consist of sub-nodes. Its name should be a noun.
In the model below, we see an Application Server node, which consists of a Blade device and Java EE-based application server system software.
Nodes aggregated, composed of other Nodes, Devices and System Software
Nodes can be interconnected by Communication Paths
Artifacts can be assigned to Nodes
Device is a hardware resource upon which artifacts may be stored or deployed for execution. A Device is a physical resource with processing capability, such as Mainframes, PCs and Routers. Often assigned with System Software, and can have sub-devices. Its name should be a noun, possibly including Vendor or product information.
The model below shows an example of a number of servers, modeled as devices, interconnected through a local area network (LAN).
Devices interconnected by Networks
Artifacts assigned to Devices
System Software assigned to Devices
Device composed, aggregated of other Devices
Node composed, aggregated of Devices
System Software is a software environment for specific types of components and objects that are deployed on it in the form of artifacts. System Software represents things like the Operating System, J2EE Application Server, a database system, workflow engine, communications middleware. Artifacts, such as a Java class can be deployed (assigned) to System Software. Often name with the appendage “...server” depending on the environment involved. Often combined with a device to form a general node.
In the model below, we see a mainframe device that deploys two system software environments: a customer transaction server and a database management system (DBMS).
System software assigned to Device
Artifacts assigned to System Software
Node composed, aggregated of System Software
System Software realises Application Component, Collaboration, Interface, Service
Infrastructure Interface a point of access where infrastructure services offered by a node can be accessed by other nodes and application components. How a Technology Service is exposed to the environment. In the technology area interfaces could range from URL / Web Pages; Network Card; URL/Web Service. A quality of interfaces is that they represent an obligation or contract that a component realizing the interface must provide. Name should be a noun.
This example contains the software and hardware infrastructure elements supporting the application layer, such as physical devices, networks, or system software (e.g., operating systems, databases, and middleware).
Node composed of Infrastructure Interfaces
Interface used by other Nodes
Infrastructure Interface assigned to Infrastructure Service
Communications Path is a link between two or more nodes, through which these nodes can exchange data. The Communication Path is a logical communications link between nodes. Can logically represent qualities of the physical network.
In the model below, we see a communication path “message queuing” between an Application Server and a Client.
A Communications Path connects one or more Nodes
Network realizes one or more Communication Paths