ArticleslgStudy

engineering

Goal structuring notation

Goal structuring notation is a engineering topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Goal structuring notation rather than just read about it. In short: Goal structuring notation (GSN) is a graphical diagram notation used to show the elements of an argument and the relationships between those elements in a clearer format than plain text. Often used in safety engineering, GSN was developed at the University of York during the 1990s to present safety cases.

Key takeaways

  • Goal structuring notation belongs to engineering; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect Goal structuring notation to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of Goal structuring notation from memory before moving on to harder problems.

Reference excerpt

Goal structuring notation (GSN) is a graphical diagram notation used to show the elements of an argument and the relationships between those elements in a clearer format than plain text. Often used in safety engineering, GSN was developed at the University of York during the 1990s to present safety cases. The notation gained popularity as a method of presenting safety assurances but can be applied to any type of argument and was standardized in 2011. GSN has been used to track safety assurances in industries such as clinical care aviation, automotive, rail, traffic management, and nuclear power and has been used in other contexts such as security cases, patent claims, debate strategy, and legal arguments.

History The goal structuring notation was first developed at the University of York during the ASAM-II (A Safety Argument Manager II) project in the early 1990s, to overcome perceived issues in expressing safety arguments using the Toulmin method. The notation was further developed and expanded by Tim Kelly, whose PhD thesis contributed systematic methods for constructing and maintaining GSN diagrams, and the concept of ′safety case patterns′ to promote the re-use of argument fragments. During the late 1990s and early 2000s, the GSN methodology was taught in the Safety Critical Systems Engineering course at York, and various extensions to the GSN methodology were proposed by Kelly and other members of the university's High Integrity Systems Engineering group, led by Prof John McDermid. By 2007, goal structuring notation was sufficiently popular that a group of industry and academic users came together to standardise the notation and its surrounding methodology, resulting in the publication of the GSN Community Standard in 2011. From 2014, maintenance of the GSN standard moved under the auspices of the SCSC's Assurance Case Working Group. As at 2022, the standard has reached Version 3.

Criticism Charles Haddon-Cave in his review of the Nimrod accident commented that the top goal of a GSN argument can drive a conclusion that is already assumed, such as that a platform is deemed acceptably safe. This could lead to the safety case becoming a "self-fulfilling prophesy", giving a "warm sense of over-confidence" rather than highlighting uncertainties, gaps in knowledge or areas where the mitigation argument was not straightforward. This had already been recognised by Habli and Kelly, who warned that a GSN diagram was just a depiction, not the safety case itself, and likened it to Magritte's painting The Treachery of Images. Haddon-Cave also criticised the practice of consultants producing "outsize GSN charts" that could be yards long and became an end in themselves rather than an aid to structured thinking.

See also Design rationale

References

Worked examples

Example 1 — a first encounter with Goal structuring notation

Start with the simplest possible case. Write down what Goal structuring notation claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In engineering, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Goal structuring notation before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Goal structuring notation ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Goal structuring notation

In research
Goal structuring notation appears in engineering research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses Goal structuring notation in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
Goal structuring notation is common in secondary-school and first-year university syllabi. It links to neighbouring topics Diagrams, Notation, Safety, so understanding it makes those chapters shorter.
In everyday life
Look for Goal structuring notation outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.
Ask Teacher Smith questions about this articleOpens your AI tutor with a question about “Goal structuring notation” →

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Goal structuring notation in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what Goal structuring notation means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain Goal structuring notation out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Goal structuring notation in simple terms?

Goal structuring notation (GSN) is a graphical diagram notation used to show the elements of an argument and the relationships between those elements in a clearer format than plain text. Often used in safety engineering, GSN was developed at the University of York during the 1990s to present safety…

Why does Goal structuring notation matter?

Because it connects several engineering ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Goal structuring notation?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Goal structuring notation.

Tags

  • Diagrams
  • Notation
  • Safety

Keep exploring