Examining the UML Models: Static Models - Components

(Page 8 of 13 )

The key element of component diagrams is the component element. A component element represents some kind of software. It can represent a code module, an executable, a DLL, and so on. The following are the key properties of a component:

• Name: Typically, the physical name of the file (such as customer.dll)

• Stereotype: Specifies the subtype of the component, for example, EXE or DLL

• Nodes: Specifies on which node (server) the component will be implemented

• Classes: Specifies which classes make up your component

These properties are all accessible from the UML Component Properties dialog box, which opens when you double-click a component on a diagram.

In Exercise 5-15, you’ll create a component diagram and add three component elements.

---

EXERCISE 5-15

1. Open VEA, if isn’t already open.

2. Create a component diagram named MyComponentDiagram.

3. Add a component named Component1 to the diagram.

4. Add a component named Component2 to the diagram.

5. Add a component named Imageshrink.dll to the diagram.

---

You can see the notation of each component in Figure 5-25.

Nodes

The node element identifies a physical, runtime object representing a processing resource. A node will typically be a server on which your components are processed or to which they are related. The following are some of the key node properties:

Chapter 5

• Name: The name of the node

• Location: The node location

• Components: Specifies which components are related to the node

In Exercise 5-16, you’ll add a node to your component diagram, and then specify which component will execute on this node.

---

EXERCISE 5-16

1. On MyComponentDiagram, add a node named Node1.

2. Double-click Node1 to open the UML Node Properties dialog box.

3. Select the Components category.

4. Select Imageshrink.dll, as shown in Figure 5-26.

Figure 5-26.  Components category of the UML Node Properties dialog box for Node1

   5.  Click OK.

---

You can see the notation of the node in Figure 5-25. Because you set the Components property for Node1 to the Imageshrink.dll component, the Imageshrink.dll file will execute on this server/node.

Next: Dependencies >>
 

More .NET Articles
More By Apress Publishing

Comments On: Examining the UML Models: Static Models

>>> Be the FIRST to comment on this article!

Buy this book...

This article is excerpted from Enterprise Development with Visual Studio .NET, UML, and MSF written by John Erik Hansen and Carsten Thomsen (Apress, 2004; ISBN: 1590590422) Buy this book now.