Reading a goal structure
How a goal structure is laid out, the two notation profiles, the summary strip, and what the Node Inspector and Focus branch show on a Goal Structuring Notation (GSN) argument.
How it is laid out
- The top goal is at the top, and each SupportedBy step is one level lower.
- Contexts, assumptions and justifications sit beside the element they qualify, stacked and centred on it, not on a level of their own.
- An element that challenges another is placed beside its target, together with whatever supports the challenge.
- The elements beneath one parent stay together, in Order.
- Every element has its identifier above its statement, and an away element has its module reference in the band beneath it.
- Several top goals are allowed. Each starts its own hierarchy.
Nodes cannot be dragged. Change the result with Order, orientation, density and spacing. Every orientation is available under both profiles.
Notation profiles
| Profile | How it draws | Settings it controls |
|---|---|---|
| GSN Community Standard v3 (default) | Every element in the standard's shape, in black on white. SupportedBy and InContextOf are both solid lines, told apart by a filled or a hollow head. Challenges are dashed. | Corner radius is fixed. Border width is limited to 1–4 px. |
| Custom | Coloured elements. InContextOf is dashed, and challenges are red and dashed. | None. |
Choose the profile under Diagram → Notation → Profile. Assumptions and justifications carry their letter, A or J, only under the standard. Decorator marks are drawn under both profiles.
Summary strip
Turn on Labels → Summary strip → Show summary. A goal structure counts goals and solutions separately, by Status. For the example it counts 4 goals, 2 Supported, 1 Open and 1 with No data, and 1 solution, Current. An element typed Undeveloped Goal is not counted; a Goal with the undeveloped mark is.
Node Inspector
The first section is headed Argument state. It lists the element's Status, Health, Module reference and Decorators, and its Identifier when an Identifier column is mapped, wherever they have a value.
There is no Relationships section, except on an element that several others connect to, such as a context shared by two goals. That shows Used in with the number of connections arriving, and the elements they come from.
Focus branch
Focus branch keeps the element, everything it leads to, including its own contexts, and its path up to the top goal. Focused on G2 in the example, it keeps G1, S1, G2 and Sn1, and fades the rest.