Difference between revisions of "Team:UNebraska-Lincoln/safety cases"
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<html> | <html> | ||
| − | + | <link rel="stylesheet" href="https://2016.igem.org/Team:UNebraska-Lincoln/css/Safetymain?action=raw&ctype=text/css"/> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
<style> | <style> | ||
| + | .wrapper .inner { | ||
| + | padding: 0em 0 1em 0; | ||
| + | margin: 0 auto; | ||
| + | width: 55em; | ||
| + | } | ||
| + | #wrapper > header { | ||
| + | padding: 0em 0 2.25em 0; | ||
| + | } | ||
| + | |||
/* styling for the menu items */ | /* styling for the menu items */ | ||
| Line 54: | Line 49: | ||
height: 200px;} | height: 200px;} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | #vgemcollaboration { | |
| + | background-image:url('https://static.igem.org/mediawiki/2016/d/de/T--Virginia--collabopen.png'); | ||
| + | background-size:180px 220px; /*Adjust background-size and the width and height properties here if you wish to resize the icon*/ | ||
| + | width:180px; | ||
| + | height:220px; | ||
| + | z-index:100; | ||
} | } | ||
| + | #vgemcollaboration:hover { | ||
| + | background-image:url('https://static.igem.org/mediawiki/2016/a/a5/T--Virginia--collabclosed.png'); | ||
| + | } | ||
| + | |||
| + | #vgemcollaboration a { | ||
| + | display:inline-block; | ||
| + | width:100%; | ||
| + | height:100%; | ||
| + | } | ||
| Line 142: | Line 146: | ||
<span class="sdt_descr"></span> | <span class="sdt_descr"></span> | ||
<div class="sdt_box"> | <div class="sdt_box"> | ||
| − | |||
<a href="https://2016.igem.org/Team:UNebraska-Lincoln/human_practices">Human Practices</a> | <a href="https://2016.igem.org/Team:UNebraska-Lincoln/human_practices">Human Practices</a> | ||
<a href="https://2016.igem.org/Team:UNebraska-Lincoln/Integrated_Practices">Integrated Practices</a> | <a href="https://2016.igem.org/Team:UNebraska-Lincoln/Integrated_Practices">Integrated Practices</a> | ||
| Line 176: | Line 179: | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
<style>.image{ | <style>.image{ | ||
position: relative; | position: relative; | ||
| Line 193: | Line 187: | ||
position: absolute; | position: absolute; | ||
}</style> | }</style> | ||
| − | + | <style>.image{ | |
| + | position: relative; | ||
| + | } | ||
| + | .image a{ | ||
| + | display: block; | ||
| + | position: absolute; | ||
| + | }</style> | ||
| + | <div class="drawing board" style=" background-color: #2e3141; padding-top:50px;"> | ||
| + | <section><img src="https://static.igem.org/mediawiki/2016/e/e5/T--UNebraska-Lincoln--safetycases.png" align="middle" style="width:100%; height:100%; padding-bottom: 30px " alt="image"/></section> | ||
| + | <section> | ||
| + | <section> | ||
| + | <div style="transform: scale(1);margin-left:150px; margin-right:150px"> | ||
<h2 class="major">Safety Assurance Cases</h2> | <h2 class="major">Safety Assurance Cases</h2> | ||
| − | <p><font color="silver">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.</font></p | + | <p><font color="silver">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.</font></p> |
<p><font color="silver">Safety cases are recognized as a powerful tool in software 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.</font></p> | <p><font color="silver">Safety cases are recognized as a powerful tool in software 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.</font></p> | ||
<h2>You can read more about our application of safety cases to synthetic biology on our <u><a href="https://2016.igem.org/Team:UNebraska-Lincoln/Integrated_Practices">Integrated Human Practices Page</a></u></h2> | <h2>You can read more about our application of safety cases to synthetic biology on our <u><a href="https://2016.igem.org/Team:UNebraska-Lincoln/Integrated_Practices">Integrated Human Practices Page</a></u></h2> | ||
| + | </div> | ||
</section> | </section> | ||
| Line 212: | Line 218: | ||
</div> | </div> | ||
| − | + | </div> | |
<!-- Scripts --> | <!-- Scripts --> | ||
| Line 283: | Line 289: | ||
}); | }); | ||
</script> | </script> | ||
| − | |||
| − | |||
| − | |||
| − | |||
</html> | </html> | ||
Latest revision as of 02:19, 20 October 2016
Safety Assurance Cases
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 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.
You can read more about our application of safety cases to synthetic biology on our Integrated Human Practices Page
Want else did we do?
