Reliability and Safety

Slides:



Advertisements
Similar presentations
A Gift of Fire, 2edChapter 4: Can We Trust the Computer?1 PowerPoint ® Slides to Accompany A Gift of Fire : Social, Legal, and Ethical Issues for Computers.
Advertisements

Can We Trust the Computer?
Lecture Outline 10 INFORMATION SYSTEMS SECURITY. Two types of auditors External auditor: The primary mission of the external auditors is to provide an.
Reliability and Safety Lessons Learned. Ways to Prevent Problems Good computer systems Good computer systems Good training Good training Accountability.
SWE Introduction to Software Engineering
A Gift of Fire Third edition Sara Baase
Software Engineering for Safety : A Roadmap Presentation by: Manu D Vij CS 599 Software Engineering for Embedded Systems.
Management Information Systems. (MIS)
EE694v-Verification-Lect5-1- Lecture 5 - Verification Tools Automation improves the efficiency and reliability of the verification process Some tools,
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
Software Quality Chapter Software Quality  How can you tell if software has high quality?  How can we measure the quality of software?  How.
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
Computers & Employment By Andrew Attard and Stephen Calleja.
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
Case Study of Knockbracken Health Care Centre Computer System By Sarah Jane Phillips and Deborah Smith.
Information Systems Security Computer System Life Cycle Security.
Lecture 1 What is Modeling? What is Modeling? Creating a simplified version of reality Working with this version to understand or control some.
Planning and Tracking Software Quality.  What Is Software Quality?  Causes of Software Defects  What is Quality Assurance?  Improving the Software.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Slide 1 Critical Systems Specification 2.
Chapter 8: Errors, Failures, and Risk
1 Can We Trust the Computer? What Can Go Wrong? Case Study: The Therac-25 Increasing Reliability and Safety Perspectives on Failures, Dependence, Risk,
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Verification and Validation Overview References: Shach, Object Oriented and Classical Software Engineering Pressman, Software Engineering: a Practitioner’s.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
1 Chapter 3 Critical Systems. 2 Objectives To explain what is meant by a critical system where system failure can have severe human or economic consequence.
Ranga Rodrigo. The purpose of software engineering is to find ways of building quality software.
1 Ethical Issues in Computer Science CSCI 328, Fall 2013 Session 37 Professional Responsibilities.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 3 Slide 1 Critical Systems 1.
CS 4001Mary Jean Harrold 1 Can We Trust the Computer?
High Performance Embedded Computing © 2007 Elsevier Chapter 1, part 2: Embedded Computing High Performance Embedded Computing Wayne Wolf.
CptS 401 Adam Carter. Announcement  Executive decision: no class Thursday! (CH and exam review will take place tomorrow instead)  Be sure that.
Lecture 1 The University of Lahore Software Engineering Saeed Akhtar
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 3.
A Gift of Fire, 2edChapter 4: Can We Trust the Computer?1 Can We Trust the Computer?
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 24 Delivering the System.
Nonbehavioral Specifications Non-behavioral Characteristics Portability Portability Reliability Reliability Efficiency Efficiency Human Engineering.
Software Defects.
1 Fault-Tolerant Computing Systems #1 Introduction Pattara Leelaprute Computer Engineering Department Kasetsart University
IS444: Modern tools for applications development Dr. Azeddine Chikh.
Chapter 5 How are software packages developed?. What are the main steps in software project development? Writing Specifications - Analysis Phase Developing.
Unit 17: SDLC. Systems Development Life Cycle Five Major Phases Plus Documentation throughout Plus Evaluation…
Validation & Verification Today will look at: The difference between accuracy and validity Explaining sources of errors and how they could be overcome.
FACTORS AFFECTING THE EFFICIENCY OF DATA PROCESSING SYSTEMS.
Topic: Reliability and Integrity. Reliability refers to the operation of hardware, the design of software, the accuracy of data or the correspondence.
Chapter 8: Errors, Failures, and Risk Zach Archer Daniel O’Hara Eric Strittmatter.
Can We Trust the Computer? FIRE, Chapter 4. What Can Go Wrong? What are the risks and reasons for computer failures? How much risk must or should we accept?
Database Principles: Fundamentals of Design, Implementation, and Management Chapter 1 The Database Approach.
IT Service Transition – purpose and processes
INFORMATION SYSTEMS SECURITY AND CONTROL.
Chapter 1- Introduction
Information Systems Development
Chapter 1- Introduction
Verification and Validation Overview
Information and documentation media systems.
The Impact of Information Technology on the Audit Process
The Impact of Information Technology on the Audit Process
Introduction to Software Testing
An Introduction to Software Engineering
A Gift of Fire Third edition Sara Baase
PowerPoint® Slides to Accompany
Reliability and Safety
Software Engineering Software Engineering is the science and art of
Reliability and Safety
Week 13: Errors, Failures, and Risks
Software Engineering Software Engineering is the science and art of
INFS 452 – Computer Ethics & Society
Chapter # 7 Software Development
A Gift of Fire Third edition Sara Baase
Presentation transcript:

Reliability and Safety What can go wrong?

Risks of Computing They support many aspects of our security: Fly by wire aircraft Patient monitoring and care administration Financial transactions Telephone networks Military surveillance and responses

Three Categories of Failures Problems for individuals System failures that affect large numbers of people or cost large amounts of money Problems in safety-critical applications

Problems for Individuals Billing Errors Not enough care - input error Not enough testing - reasonable range Not enough training

Database Accuracy Problems Info in database is not accurate Automatic entering of info - mistakes can be overlooked Erroneous duplication - copies of incorrect info can be in other systems Insufficient training - not knowledgeable enough about the system

Possible States of a Computer Functioning correctly Functioning incorrectly Down Intentionally off

Causes of Computer Failure Faulty design of software or hardware Sloppy implementation Careless or insufficiently trained users Poor user interfaces Hardware/Software malfunctions Specification errors Scope/Application inconsistency

Computer Users Perspective Should user should understand… limitations of the computers the need for proper training the need for responsible use the difference between good products and bad ones

Computer Professional Perspective The professional should… study computer failures study computer ethics

Educated Member of Society Perspective Education will… help us evaluate the reliability and safety of various computer applications help evaluate computer technology

Relevant Research Topics Architecture: hardware and software Systems engineering Reasoning; languages, techniques and engineering Requirements analysis Fault tolerance Repair and maintenance Holistic safety arguments Formal methods Real-time issues

Consumer Hardware and Software Usually have more serious errors in their first releases Regularly sold with known bugs Hardware also has flaws Tradeoff between cost, debugging, and marketing Dishonesty, denials of problems, lack of adequate response to complaints