Creating a Node

Important

Please make sure that you do not modify the auto-generated node names (such as NSG1, NSG2, OSG1, OSG2). Use step 2 and 3 below to change node labels via the Tagged Values Editor.

---

Step 1

1) Double-click to open a desirable diagram name in "Model Explorer" ("SIG1" in this example).
2) Click a desirable node type in the desirable tool panel ("NFR Softgoal" in this example).
3) Click in the opened diagram at a desirable location. A new node of the selected type will be created.

---

Step 2

1) Right-click the newly created node to view the pull-down menu. (Alternatively, click the newly created node then press Ctrl-F7 as a short-cut.)
2) Click "Tagged Value Editor" to open the Tagged Value Editor dialog.

---

Step 3

1) Click to enter values for the desirable attributes. In this example, "Confidentiality" and "Account" are entered for Type and Topic attributes respectively.
2) Some attribute values are automatically reflected on the diagram appropriate for the node type. In this example, the Softgoal node is displayed with ""Confidentiality[Account]" label using the newly entered values.
3) Click "Close".

---

Important points to check

If your diagram looks similar to "Incorrect naming 1" or "Incorrect naming 2" examples below, please re-create your node by following Step 1, 2, and 3 closely so that it would like similar to the "Correct naming" example.

Correct naming

1) Select a node
2) Ensure that the corresponding element name in the Model Explorer has 3 alphabets and 1 or more digits ("NSG1" in this example)
3) Ensure that the corresponding element name in the Properties area has 3 alphabets and 1 or more digits ("NSG1" in this example)
4) Open the Tagged Value Editor (right-click the node then select Tagged Values, or left-click the node then press Ctrl-F7)
5) Ensure that the attributes have values as appropriate for the notation in question. For example, for the NFR Framework, each node should have at least the Type attribute filled, optionally with the Topic attribute also filled.
6) Ensure that the diagram shows the node with the appropriate label for the notation in question. For example, for the NFR Framework, the node's label should be derived from the Type and Topic attributes.

Incorrect naming 1

1) Select a non-UML node (NFR Framework node in this example)
2) Ensure that the element name has 3 alphas + 1 or more digits (e.g., "NSG1") in the Model Explorer area and is not replaced with your user-defined name. For example, an NFR Softgoal should have an auto-assigned named, such as "NSG1", instead of user-defined "Confidentiality[Account]" name in this example.
3) Similarly, ensure that the 3-alpha_1-digit name (e.g., "NSG1") in the Properties area is not replaced with your user-defined name ("Confidentiality[Account]" in this example)
4) Open the Tagged Value Editor
5) Ensure that the required attributes for the notation in question are not blank. For example, for the NFR Framework, Type attribute should not be blank as shown.
6) If Type and Topic are blank, the diagram would show the default label to indicate that either or both Type and Topic are not provided (shown with the default hint "Type[Topic]" in this example)

Incorrect naming 2

1) Select a node. The node should have a correct shape for the notation in question, not a rectangle as shown.
2) Ensure that the 3-alpha_1-digit name (e.g., "NSG1") in the Model Explorer area is not replaced with your user-defined name. For example, for the NFR Framework, an NFR Softgoal should have an auto-assigned named, such as "NSG1" instead of "Confidentiality[Account]" in this example.
3) Similarly, ensure that the 3-alpha_1-digit name (e.g., "NSG1") in the Properties area is not replaced with your user-defined name ("Confidentiality[Account]" in this example)
4) Open the Tagged Value Editor
5) Ensure that the required attributes for the notation in question are not blank. For example, for the NFR Framework, Type attribute should not be blank as shown.
6) If Type and Topic are blank, the diagram would show the default label to indicate that either or both Type and Topic are not provided (shown as "Type[Topic]" in this example)