You might have realised that there was a big number of small releases for the main App, Vithanco. I assume you realise the difference in use. I want the App to be as smooth and as easy to use as possible. The version that is currently in review with Apple is Version 1.9.11. Since the release of V1.9, I have done changed the following:
This blog entry is a run through of how to use some of the not-so-well-documented features of Vithanco.
There is a simple feature that helps me a lot. I adjust the standard domains for variations whenever it helps me to express myself better. A typical scenario for me is during Concept Mapping, when I want to show that I am unsure whether I understand a Concept well enough. I simply know that I need more input from someone and I want to show this in the diagram with a different Node Type.
The Node Type Editor
It’s simple. I start by viewing the Node Type of a Concept. For this you open the normal Node Editor. Further down comes a button with “View Node Type”.
Once clicked, the Node Type Editor for the Node Type is opened. In this case it is for the “Concept” Node Type.
This Editor is only useable in the full version of Vithanco. Let me explain a bit it’s design.
- Here are all Domains for the document listed. In this case there are two, with the Basic Domain as the first one. The Basic Domain has AND, OR Node Types, but as well notes and problem Node Types.
- The 2nd Domain is Concept Mapping.
- Concept is a Node Type that belongs to the Concept Mapping domain. The remaining dialog shows details of the Concept Node Type.
- A few points are worth noting about this type. Firstly, there is a tickbox to indicate whether this node can be the first one on the canvas. This controls whether you start an empty diagram with this node or not.
- The starting node setting is in this diagram displayed via the Power On/Off symbol. From the symbol an arrow leads to the Node Type. This symbol wouldn’t be shown if the node wouldn’t be a starting node.
- The rest of this diagram shows the suggested predecessors and successors for this Node Type. The Concept Nodes are always alternating with Relationship Nodes. This is expressed on the Node Type level through predecessors and successor Node Types. Change the predecessors and/or successors and the suggestions (or recommendations) during modelling will change. The diagram here at 6 simply shows these relationships.
- You can change the predecessors and successors here in the editor. (Scroll down a bit).
- If you want to change the looks of the Node Type, select another Type. Concepts are simple rounded boxes with Text in the middle.
- Change Colors in this part. As you can see, the Concept Node Type uses the color with the RGB code 208,236,237. Click and change.
The New Node Type
I said I wanted to show that I am not sure about a concept. I am going to show this through a yellowish Node Type. Hence, I press the button in the lower part of the middle scroll box.
What does this do? It creates a new Node Type with the same settings as the original. I can adjust only the parts that I would like.
What did Change?
- The new Node Type “Unconfirmed Concept” was added to the same Domain “Concept Maps”.
- I changed the name to “Unconfirmed Concept” here – which triggered the change under 1.
- I changed the background color here towards a light yellow.
- The Node Type diagram shows the new Node Type. It has duplicated the predecessors and successors of the Concept Node Type. I can therefore use the new type wherever I used the original.
The changed Domain
In case you wonder about what changed on the Domain level, have a look at the Domain Diagram.
Please note that many arrows are bidirectional. You start (bottom symbol) with one of the three Concept Nodes, and from there there is only an arrow to Relation. From Relation you can access any of the (now) three Concept Node Types, after which I “return” to a Relation. Hence, I can use the new Node Type where I previously used the other Concepts Nodes.
I could as well create a new Relation Node Type in a similar fashion.
Other Domain Hacks
I use this feature regularly for Concept Maps. In fact, I might add the third Node Type to the standard in the future.
Other Domains can benefit similarly. For example the Benefit Breakdown Structure was extended by Disbenefits, HR Enablers, IT Enablers, etc.
Causal Loop diagrams can as well benefit from different colors if you want to show areas of different departments or similar.
Finally, the explanations above should encourage you to create a completely new Domain from scratch. Just try it out. Ask, if something is unclear.
How to use the new Node Type
Now, I can close the Node Type Editor and change the Node Type of the node that triggered my addition to the standard model.
Press the button in middle, on the left side with the sign post to change the type. You will only get “valid” replacements according to the Domain model. As the help text says, you can override this behaviour by keep pressing CTRL before clicking on the button and you can choose any Node Type, even if that means that your Concept Map is no longer easy to read.
The outcome for this example diagram is like this:
Please note, that I am not sure whether Darth Vader is an evil character, which I make clear through the yellow background. No flame war, please.