B. Todd AB/CO/MI 30 th January 2008 Safety in Mind…

Slides:



Advertisements
Similar presentations
Test process essentials Riitta Viitamäki,
Advertisements

HSE’s Ageing and Life Extension Key Programme (KP4) and Human Factors
Welcome to the Comanche art room. Ms. Howe Seating Chart You will be assigned a seat at random for the first quarter. 2 nd, 3 rd, and 4 th quarter you.
1 Design by Contract Building Reliable Software. 2 Software Correctness Correctness is a relative notion  A program is correct with respect to its specification.
1 Basic Definitions: Testing What is software testing? Running a program In order to find faults a.k.a. defects a.k.a. errors a.k.a. flaws a.k.a. faults.
Reliability Risk Assessment
CS351 © 2003 Ray S. Babcock Software Testing What is it?
Building Reliable Software Requirements and Methods.
Type-Safe Programming in C George Necula EECS Department University of California, Berkeley.
Quality Assurance. Software Qualities Maintainer User Customer Good Documentation Readable Code Good Design Low Cost Portability Increased productivity.
Illinois Institute of Technology
Karlstad University Computer Science Design Contracts and Error Management Design Contracts and Errors A Software Development Strategy (anpassad för PUMA)
Objectives Understand the basic concepts and definitions relating to testing, like error, fault, failure, test case, test suite, test harness. Understand.
EE694v-Verification-Lect5-1- Lecture 5 - Verification Tools Automation improves the efficiency and reliability of the verification process Some tools,
ECI 2007: Specification and Verification of Object- Oriented Programs Lecture 0.
Chapter 11: Testing The dynamic verification of the behavior of a program on a finite set of test cases, suitable selected from the usually infinite execution.
System Testing There are several steps in testing the system: –Function testing –Performance testing –Acceptance testing –Installation testing.
 By the end of this, you should be able to state the difference between DATE and INFORMAITON.
Product Quality, Testing, Reviews and Standards
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
CRASH AND BURN ARIANE 5 Kristen Hieronymus SYSM6309 Advanced Requirements Engineering
Objectives Understand the basic concepts and definitions relating to testing, like error, fault, failure, test case, test suite, test harness. Explore.
TECHNICAL WRITING October 31 st, With a partner Write simple “step-by-step” instructions for sending a Kakao Talk message with a phone.
Software Safety CS3300 Fall Failures are costly ● Bhopal 1984 – 3000 dead and injured ● Therac – 6 dead ● Chernobyl / Three Mile.
Introduction CS 3358 Data Structures. What is Computer Science? Computer Science is the study of algorithms, including their  Formal and mathematical.
Protecting the Public, Astronauts and Pilots, the NASA Workforce, and High-Value Equipment and Property Mission Success Starts With Safety Believe it or.
INVARIANTS EEN 417 Fall When is a Design of a System “Correct”? A design is correct when it meets its specification (requirements) in its operating.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 23 Reliability III.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
Introduction CS 3358 Data Structures. What is Computer Science? Computer Science is the study of algorithms, including their  Formal and mathematical.
Data and information. Information and data By the end of this, you should be able to state the difference between DATE and INFORMAITON.
B. Todd et al. 25 th August 2009 Observations Since v1.
Reliability and Recovery CS Introduction to Operating Systems.
1 1.Introduction Objectives Understand uncertainty and variability and their significance in design Understand concept, benefits of reliability-based design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 3.
AS Computing Verification. Once sensible data has been entered, the second of method of ensuing data integrity can be employed. Verification is the process.
Safety Critical Systems 5 Testing T Safety Critical Systems.
1 Reducing the Software Impact to System Safety Paul Mayo – SafeEng Limited.
Safety-Critical Systems 7 Summary T V - Lifecycle model System Acceptance System Integration & Test Module Integration & Test Requirements Analysis.
1 Legacy Code From Feathers, Ch 2 Steve Chenoweth, RHIT Right – Your basic Legacy, from Subaru, starting at $ 20,295, 24 city, 32 highway.
1 EE29B Feisal Mohammed EE29B: Introduction to Software Engineering Feisal Mohammed Ph: x3156.
RELIABILITY ENGINEERING 28 March 2013 William W. McMillan.
Nonbehavioral Specifications Non-behavioral Characteristics Portability Portability Reliability Reliability Efficiency Efficiency Human Engineering.
Introduction to Measurement. According to Lord Kelvin “When you can measure what you are speaking about and express it in numbers, you know something.
Verification – The importance
Mechanical Integrity Equipment Deficiencies. Lesson Objectives  Describe Actions When Equipment Deficiencies Found in Operating Equipment  Describe.
PRESENTER PRIYANKA GUPTA.  Testing the complete system with respect to requirements.  In System testing, the functionalities of the system are tested.
CSCI1600: Embedded and Real Time Software Lecture 28: Verification I Steven Reiss, Fall 2015.
BT/BP AB/CO/MI 17 th September 2008 Safe Machine Parameters Status & Update.
Thursday August 20, 2009 John Anderson Page 1 Accelerator Interlock System Issues Flow Down of Requirements from the Safety Order to Engineered Safety.
29 March Software Quality and Testing. Why do we care? Therac-25 (1985) Multiple space fiascos (1990s) Ariane V exploded after 40 seconds (conversion)
Silicon Programming--Testing1 Completing a successful project (introduction) Design for testability.
Definitions, Goals and Objectives Embry-Riddle Aeronautical University Chapter 3.
Failure Modes, Effects and Criticality Analysis
Beam Interlock System Dependability Study RSWG – 31 st January 2005.
Chapter 9 Testing the System 9.1 Principles of System Testing Focus A: The objective of unit and integration ensure the code implemented the design.
INTRODUCTION CSE 470 : Software Engineering. Goals of Software Engineering To produce software that is absolutely correct. To produce software with minimum.
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Testing the System.
Dependability Requirements of the LBDS and their Design Implications
Software Testing Introduction CS 4501 / 6501 Software Testing
Verification and Testing
Creating high confidence, highly dependable, critical software
Chapter 18 Software Testing Strategies
Software testing strategies 2
Standards.
Therac-25.
Creating high confidence, highly dependable, critical software
Creating high confidence, highly dependable, critical software
Chapter 8 Software Evolution.
Presentation transcript:

B. Todd AB/CO/MI 30 th January 2008 Safety in Mind…

LHC Beam Interlock System 2 of 12 Interesting Times… Safety Systems are all around us: designed by engineers, to a specification. like any other system must be careful! not acceptable to ‘put it together and see if it works’ we must be vigilant! Things can go wrong… 1.Software Failure 2.Hardware Failure 3.Incomplete Procedures 4.Human Error Human error is special, since it is us, humans, who build the systems in the first place…

LHC Beam Interlock System 3 of 12 Software Safety Difficult to quantify ‘safe software’ … A typical mobile phone can have 2 million lines of code A car can have 100 million lines How on earth can these be tested? Complicated verification tools and mathematical proofs can be done $$$$ & Time & People & Experience … When faults cost $$$$ we hear about them:

LHC Beam Interlock System 4 of 12 Software Failures IEEE (reliable source) Software Error - USDOD Software Reset badly written COST 1 Helicopter, 4 marines Airbus A320 Crash at Airshow The pilot claims he was misled on the aircraft's true height by a bug in the software COST 3 lives, one aircraft Ariane 5 Rocket Failure Software error in the inertial reference system COST $500 million

LHC Beam Interlock System 5 of 12 Hardware Safety It’s easier to quantify ‘safe hardware’ … Reduce the critical function Use military handbooks Use tried and tested methods Redundancy and testing But still it takes some energy $$ & Time & People & Experience … It takes extra effort to build safe systems… MUCH more effort to correct an existing system to be safe And it can still go wrong …

LHC Beam Interlock System 6 of 12 Hardware Failures Titan 4 Exploded after Takeoff Hardware failure COST $1 Billion Bruncefield oil fire Two safety interlocks failed

LHC Beam Interlock System 7 of 12 Procedural Safety Using the safety equipment … Needs PROCEDURES! Components degrade Safety must be verified by checking and testing Maintenance has to be carried out to make something as good as new Two good examples of bad procedures causing loss are: Chernobyl – ‘special’ procedure being followed Piper Alpha - safety maintenance was underway

LHC Beam Interlock System 8 of 12 Human Error Using the safety equipment … Needs operators! Humans are… ABSOLUTELY… the weakest link Human Error - CNN Engineers mis-converted English to Metric COST $125-million 1998 USS York town - GCN Managed to enter zero for a setting, which crashed the systems 2004 Thunderbird Crash Pilot miscalculated height above sea-level

LHC Beam Interlock System 9 of 12 Why are we the weakest link A couple of fun examples… change blindness from UBC in Canada inattention blindness from University of Illinois

LHC Beam Interlock System 10 of 12 And so… no magic bullet to make us ‘safe engineers’ We are after all, just human. This presentation is only intended to illustrate that. -Less Software means more provable safety -Hardware can be designed to be safe -Procedures must be complete so safety can be verified -we are just human -Everyone is entitled to make a mistake AB/CO/MI has gone considerable way to developing a safety culture We’ve learned from our mistakes and those of others The time is now, to expand this safety culture!

LHC Beam Interlock System 11 of 12 Rules for VHDL Design But there ARE rules for the VHDL realisation 1.Specification has to be complete 2.Add safety rules and recommendations to specification 3.Describe how you will check that those rules are met 4.Use lots of Asserts in VHDL 5.Use complete Testbenches that PROVE you tested them 6.Design small blocks of code that can be completely tested 7.Build a real-life test bench to prove your design 8.Document anything which is ‘dangerous’ These are the minimum. They all assume you have safe hardware as a basis We accept no compromise here.

LHC Beam Interlock System 12 of 12 FIN