Difference between revisions of "Team:UNebraska-Lincoln/Integrated Practices 2"
| Line 240: | Line 240: | ||
<br> | <br> | ||
<p><font color="white"><span style="font-weight: 400;">A graphical representation, called Goal Structuring Notation (GSN), has been developed by T.P. Kelly (University of York) to help follow the arguments within a safety case. GSN is set up in a flowchart fashion. Standardized shapes have been determined to represent the different “building blocks” of safety cases. A rectangle represents the claims and sub-claims, evidence is represented by a circle, strategies are represented by a parallelogram, and context is represented by a rectangle with rounded edges.</span></p> | <p><font color="white"><span style="font-weight: 400;">A graphical representation, called Goal Structuring Notation (GSN), has been developed by T.P. Kelly (University of York) to help follow the arguments within a safety case. GSN is set up in a flowchart fashion. Standardized shapes have been determined to represent the different “building blocks” of safety cases. A rectangle represents the claims and sub-claims, evidence is represented by a circle, strategies are represented by a parallelogram, and context is represented by a rectangle with rounded edges.</span></p> | ||
| + | |||
| + | <p>For more inforomation on GSN go <a href="http://citeseerx.ist.psu.edu/viewdoc/download;jsessionid=70234D2A40EAEF9478A944CAE1AA0C92?doi=10.1.1.66.5597&rep=rep1&type=pdf"><strong>here.</strong></a></p> | ||
<div class="image"> | <div class="image"> | ||
<img src="https://static.igem.org/mediawiki/2016/1/15/T--UNebraska-Lincoln--IHP3.png" align="middle" style="width:100%; height:auto; transform: scale(0.8)" alt="image"/> | <img src="https://static.igem.org/mediawiki/2016/1/15/T--UNebraska-Lincoln--IHP3.png" align="middle" style="width:100%; height:auto; transform: scale(0.8)" alt="image"/> | ||
Revision as of 17:48, 19 October 2016
<!DOCTYPE HTML>
Safety Cases Overview
What is a Safety Case?
A safety case is an architecture to structure the reasoning software engineers use to gain confidence that systems will work as expected. Safety cases are especially developed for safety-critical software systems, like software controlling avionics systems or nuclear power plants.
Safety cases are recognized as a powerful tool in software engineering, especially in Europe. Safety cases have been used extensively in Europe for over a decade to document safety for safety-critical software systems. Predictability of a safety-critical software system is essential. By developing safety cases, unexpected defects and vulnerabilities can be uncovered prior to implementation of the software system where failures could lead to devastating consequences.
How are Safety Cases formed?
The structure of a safety case follows a hierarchy where a series of arguments complemented with evidence captures the reasons why a system is presumed to work as expected. The high-level goal is the top level of the safety case hierarchy. To gain confidence in the system, high-level claims are then made. These claims are broken down into sub-claims and finally supported by evidence when it seems like a natural transition from a claim to evidence. Argumentation strategies are identified throughout the safety case to help clarify the arguments. Context is also provided to claims when deemed necessary.
GSN Fundamentals
A graphical representation, called Goal Structuring Notation (GSN), has been developed by T.P. Kelly (University of York) to help follow the arguments within a safety case. GSN is set up in a flowchart fashion. Standardized shapes have been determined to represent the different “building blocks” of safety cases. A rectangle represents the claims and sub-claims, evidence is represented by a circle, strategies are represented by a parallelogram, and context is represented by a rectangle with rounded edges.
For more inforomation on GSN go here.
Want to see more outreach?
