Failure and Design Jaime Baber October 12, 2000

Slides:



Advertisements
Similar presentations
Building a Cradle-to-Grave Approach with Your Design Documentation and Data Denise D. Dion, EduQuest, Inc. and Gina To, Breathe Technologies, Inc.
Advertisements

BRYAN YOUNG Preventative Maintenance Working With Safety.
Testing and Quality Assurance
Chapter 4 Quality Assurance in Context
Chapter 16 Medical device reliability Facts and figures, government control and liability NFPA 1200 deaths per year due to faulty instrumentation.
Software Quality Assurance (SQA). Recap SQA goal, attributes and metrics SQA plan Formal Technical Review (FTR) Statistical SQA – Six Sigma – Identifying.
Stepan Potiyenko ISS Sr.SW Developer.
Overview Lesson 10,11 - Software Quality Assurance
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
(c) 2007 Mauro Pezzè & Michal Young Ch 1, slide 1 Software Test and Analysis in a Nutshell.
Introduction ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August.
CSE 466 – Fall Introduction - 1 Safety  Examples  Terms and Concepts  Safety Architectures  Safe Design Process  Software Specific Stuff 
Quality Control and Improvement, Reliability, Liability P. King/Chapter 13 overview.
Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation
Quality Control and Improvement, Reliability, Liability P. King/Chapter 15 overview.
Software Project Management
Ch.4: QA in Context  QA and the overall development context Defect handling/resolution How alternative QA activities fit in process Alternative perspectives:
COURSE TITLE: 1 Software Quality Assurance. Course Aims Introduction to software quality assurance. Software testing terminology. Role and responsibility.
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
1 Chapter 2 Socio-technical Systems (Computer-based System Engineering)
CLEANROOM SOFTWARE ENGINEERING.
Planning and Tracking Software Quality.  What Is Software Quality?  Causes of Software Defects  What is Quality Assurance?  Improving the Software.
Therac 25 Nancy Leveson: Medical Devices: The Therac-25 (updated version of IEEE Computer article)
Software Reliability SEG3202 N. El Kadri.
Software is:  Computer programs, procedures, and possibly associated documentation and data relates to the operation of a computer system. [IEEE_Std_ ]
Software Software is omnipresent in the lives of billions of human beings. Software is an important component of the emerging knowledge based service.
Protecting the Public, Astronauts and Pilots, the NASA Workforce, and High-Value Equipment and Property Mission Success Starts With Safety Believe it or.
Intent Specification Intent Specification is used in SpecTRM
Socio-technical Systems (Computer-based System Engineering)
LSST Camera CD-3 Review Brookhaven National Laboratory, Brookhaven, NY LSST Safety Council Camera Review Bremerton, WA 2015 LSST Camera Environment,
Engineering Design Dein Shaw. Chapter 1 Introduction What is design?
Software Project Management Lecture # 11. Outline Quality Management (chapter 26 - Pressman)  What is quality?  Meaning of Quality in Various Context.
M. Frize, Winter 2003 Reliability and Medical Devices Prof. Monique Frize, P. Eng., O.C. ELG5123/ February 2003.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Introduction to Quality Imran Hussain. Project Development Costs Around 63% of software projects exceed their cost estimates. The top four reasons for.
Software Testing and Quality Assurance Software Quality Assurance 1.
Verification and Validation Assuring that a software system meets a user's needs.
Software Reliabilty1 Software Reliability Advanced Software Engineering COM360 University of Sunderland © 1998.
Ensure that the right functions are performed Ensure that the these functions are performed right and are reliable.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
TESTING FUNDAMENTALS BY K.KARTHIKEYAN.
Bryce Davis Glen Henbest Martin Gilmore Anjul Maheshwari Matt Oster Vanderbilt University Department of Biomedical Engineering November 5, 1998 designsafe.
Chapter - Software Engineering Fail safe design problems Component jams Operator detected failure Erroneous input Unsafe modes Programming errors Sabotage.
Software Engineering Lecture 8: Quality Assurance.
Project Management Quality Management. Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
MAJOR SOFTWARE FAILURES, WHY THEY FAILED AND LESSONS LEARNED BY AKPABIO UWANA.
Failure Modes, Effects and Criticality Analysis
SAFETY AND HEALTH IN PROCESS INDUSTRIES(MKKK1653) 2015/2016 ASSIGNMENT Failure mode, effect and critical analysis (FMECA) By Yahya Gambo (MKK152006) SUBMITTED.
Six Sigma Greenbelt Training
Manufacturing the Safe Product
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
OH&S Plant Obligations make
Software Quality Assurance
Software Project Management
Preventing Medical Device Recalls
FMEA.
Verification & Validation
Quality Quality is “a characteristic or attribute of something.”
BASICS OF SOFTWARE TESTING Chapter 1. Topics to be covered 1. Humans and errors, 2. Testing and Debugging, 3. Software Quality- Correctness Reliability.
Peer Review Agenda (Suggested).
GE 6757 TOTAL QUALITY MANAGEMENT
Introduction to Fault Tolerance
Please read this before using presentation
RELIABILITY Reliability is -
Software Testing Lifecycle Practice
Definitions Cumulative time to failure (T): Mean life:
Presentation transcript:

Failure and Design Jaime Baber October 12, 2000 BME 272: Dr. Paul H. King

Introduction Failure: Degradation of performance of a device outside of a specified value Non Performance or inability to perform for a certain time within space conditions Causes of Failure: Systemic and Random Diabetes Test Kit

Similar Terms Defect : An imperfection (which may/may not lead to failure) Deficiency: Lack of conformance to specifications Malfunction: Unsatisfactory performance Fault: Cause of failure Could be something in environment Something that happens to device: not internal

Failure is a fact of life...

Failure is a fact of life... Define operational issues/normal operation Failure rate Anticipate the worst Failure Mode Analysis Design around it: FAIL SAFE

Hardware Failure Early: First 1,000 hours Random: Mid-life Wearout: Late Artificial Hip

Software Failure Specification errors Design Error Typo Ommission Lack of Verification

Human Error….

Human Error Most important Documentation: Not up-to-date or missing Engineers must review and test Track Failures

Reliability Describes how dependable a device is over time Performs for a stated environment/time w/o failure Plan/Design/Manufacture reliability into product vs Quality

Mechanical Reliability Due to deterioration of design strength or assembly

Electronic Reliability Three distinct time periods

Software Reliability

Overall Device Reliability

Reliabilty Assurance Design Fault Tolerance Improve Manufacturing Quality Assurance Teams/ Inspect Service Manuals Test Monitor

Design….

designsafe... Task Based Safety Analysis Hazard Analysis Users Tasks Risk Assessment Four levels of severity