Normal Accidents: Living with High-Risk Technologies Minho Jeung Trinity Team 12/06/2005.

Slides:



Advertisements
Similar presentations
Frankenstein homes: would you want to live in one? Bruce Taylor SEARCH (Scottish Centre for Environmental Design Research) Robert Gordon University Aberdeen.
Advertisements

© 2007, PETER-SERVICE Minimizing Effect of Defects and Abnormal Conditions by Loosely Coupled Architecture of Convergent Billing Solution Maxim Samsonov.
CS3500 Software Engineering Project Management (1) In 1986 one well-known software engineer (Tom DeMarco) made the simple but important observation: “You.
1 Graduates’ Attributes : EMF, EUR-ACE and Federal Educational Standards Alexander I. Chuchalin, Chair of the RAEE Accreditation Board Graduates’ Attributes.
MULTIMEDIA DEVELOPMENT 4.3 : AUTHORING TOOLS. At the end of the lesson, students should be able to: 1. Describe different types of authoring tools Learning.
RISK INFORMED APPROACHES FOR PLANT LIFE MANAGEMENT: REGULATORY AND INDUSTRY PERSPECTIVES Björn Wahlström.
Software Quality Ranking: Bringing Order to Software Modules in Testing Fei Xing Michael R. Lyu Ping Guo.
SYSTEMS-THEORETIC ACCIDENT MODEL AND PROCESSES (STAMP) APPLIED TO DESIGN A SAFETY-DRIVEN CONCEPT OF AN AIR NAVIGATION SERVICE PROVIDER (ANSP)
Workshop on Machine Protection, focusing on Linear Accelerator complexes Summary of Fifth Session – Operational Aspects 1)RF Breakdown recovery 2)CLIC.
1 1 File Systems and Databases Chapter 1 The Worlds of Database Systems Prof. Sin-Min Lee Dept. of Computer Science.
1 Software Testing and Quality Assurance Lecture 34 – Software Quality Assurance.
André Weiß, DLR Institute of Space Systems Concurrent Evaluation – An Application for DLR’s Concurrent Engineering Facility SECESA 2010, October,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
1 1 File Systems and Databases Chapter 1 Prof. Sin-Min Lee Dept. of Computer Science.
Quality Risk Management ICH Q9 Annex I: Methods & Tools
Dynamic Islanding of Critical Infrastructures, a Suitable Strategy to Survive and Mitigate Critical Events Joint Infrastructure Interdependencies Research.
Systems Engineer An engineer who specializes in the implementation of production systems This material is based upon work supported by the National Science.
FAILURES AND CAUSES NASA MISSIONS SYSM Advance Requirements Engineering Dr. Chung Muhammad Ayaz Shaikh 05/19/2012.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Eunice Hsiao-Hui Wang*, Hung-Yung Tang * Associate Professor, Innovation Center for Big Data and Digital Convergence/Department of Information Communication.
POWER SYSTEM PROTECTION
Nuclear Power as a High Risk System And the Accident at Three Mile Island Discussing Perrow Chapters 1 and 2 Presented by Gus Scheidt Friday the Thirteenth.
Risk Management for Technology Projects Geography 463 : GIS Workshop May
Organizing Your Information
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects.
Building Dependable Distributed Systems Chapter 1 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 1 DATABASE SYSTEMS Instructor Ms. Arwa Binsaleh.
Product & Technology Quality. Excellence. Support SIL Explanation 27.JAN 2006 Automation & Safety.
Managing the CERN LHC Tier0/Tier1 centre Status and Plans March 27 th 2003 CERN.ch.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
1. What do you understand by software engineering? Discuss the role of engineering software development. 2. What do you understand by software requirement.
A Fault Tolerant Control Approach to Three Dimensional Magnetic Levitation By James Ballard.
Living with High Risk Technologies
University of Virginia Department of Computer Science Complex Systems and System Accidents presented by: Joel Winstead.
Disaster Tolerant Computing and Communications Systems Mitch Thornton Steve Szygenda.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Chapter 3 Polarization of Light Waves
IAEA Training Course on Safety Assessment of NPPs to Assist Decision Making Common Cause Failure Analysis Workshop Information IAEA Workshop City, Country.
Statistics and Probability Theory Lecture 01 Fasih ur Rehman.
CPSC 873 John D. McGregor Session 3 Requirements V & V.
RISK MANAGEMENT. CONTENTS  DEFINITION  WHAT IS RISK  TYPES OF RISK  RISK MANAGEMENT PROCESS  APPROACHES TO RISK MANAGEMENT.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
Overview of the handbook Chapter 5: Levee inspection, assessment and risk attribution.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
September st Evening Vocational School of Trikala our IT lessons …
CASE Tools and their Effect on Software Quality
CASE (Computer-Aided Software Engineering) Tools
A fault tree – Based Bayesian network construction for the failure rate assessment of a complex system 46th ESReDA Seminar May 29-30, 2014, Politecnico.
Failure Modes, Effects and Criticality Analysis
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
1 Project management Organising, planning and scheduling software projects.
Introduction GIS often represent spatial information with a two-dimensional x,y coordinate system. Some data linearly measured. In order to use the information.
An Iterative Method For System Integration
TOPIC: THE VALUE OF BIOMEDICAL ENGINEERS AND TECHNICIANS IN HOSPITAL PRESANTED BY: KWIZERA ABRAHAM STUDENT IN: BMET /FINALIST STU INSTITUTION: IPRC KIGALI.
Conduction of a simulation considering cascading effects
BASIC PROFESSIONAL TRAINING COURSE Module V Safety classification of structures, systems and components Case Studies Version 1.0, May 2015.
Final Presentation of (Field Study or OCI) Project named …
Risk Management for Technology Projects
John D. McGregor Session 3 Requirements V & V
Tradeoff Analysis of Strategies for System Qualities
Tools of Software Development
Digital Control Systems (DCS)
تكملة الوحدة الاولى الفصل الثاني بالكتاب للاطلاع ثم الفصل الثالث التخطيط لبناء الاختبارات التحصيلية الفصل الثالث من الكتاب (87-164)
Conduction of a simulation considering cascading effects
Power Design Rodger Hyle. Power Design Rodger Hyle.
Capstone Team Project title
Failure Mode and Effect Analysis
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
Review and comparison of the modeling approaches and risk analysis methods for complex ship system. Author: Sunil Basnet.
Luca Simoncini PDCC, Pisa and University of Pisa, Pisa, Italy
Presentation transcript:

Normal Accidents: Living with High-Risk Technologies Minho Jeung Trinity Team 12/06/2005

Contents 1. Introduction 2. Normal Accident Theory 3. Three Mile Island 4. Policy Recommendations 5. Conclusion 2/11

Modern people manage to get along one way or others meeting with an accident. People forget accident immediately and adapt themselves the dangerous environment People do not have any solution to address the problem Tightly coupled technology system makes people not avoid an accident Accidents are neither abnormal nor deviatory. Accidents are normal events for complex system. 3/11 1. Introduction

The accidents caused by component failures The accidents are caused by interactive complexity in the presence of tight coupled system. Modern systems can tolerate the impact of the fault of a single component. Normal accidents are not caused by the failure of component but the interaction of components. 4/11 2. Normal Accident Theory This picture is referenced by Introduction Accidents Analysis, Yu-Hsing Huang, CSELAB, University of Linkoping

Tightly coupled interactions: These are represented to those that do not tolerate delay. They have invariant sequences and small slack. Loosely coupled interactions: These have the opposite characteristics. The interactions are linear or complex. The linear means simple system. The other is complex. Thus, Perrow made the following framework to classify systems according to these definitions. 5/11 2. Normal Accident Theory

Systemic elements led to major accidents, not the actions of the operators themselves Systemic elements led to major accidents, not the actions of the operators themselves The combination of interactive complexity and tight coupling of the high risk systems The combination of interactive complexity and tight coupling of the high risk systems 6/11 3. Three Mile Island This picture is referenced by

7/11 3. Three Mile Island This picture is referenced by

Perrow made a set of policy recommendations, which are targeted at specific systems. The three policies are: abandon, restrict, tolerate and improve. Plotted various systems on the chart, and then draws curves to split them into three categories. 8/11 4. Policy Recommendations

5. Conclusion Tightly coupled system can cause catastrophic accidents. Tightly coupled system can cause catastrophic accidents. The system is made loosed or the system has some redundancy. The system is made loosed or the system has some redundancy. 9/11 ► Lessons Learned

► How we apply Normal Accident Theory to Studio? 10/11 5. Conclusion The VR engine can be used in various fields of industry It will be tightly coupled with the legacy system Design the system to have redundancy.

Thank you