Chapter - Software Engineering Fail safe design problems Component jams Operator detected failure Erroneous input Unsafe modes Programming errors Sabotage.

Slides:



Advertisements
Similar presentations
/// MELSEC Safety /// QS001CPU /// QS0J61BT12 /// QS0J65BTB2-12DT /// MELSEC Safety /// Mitsubishi Electric - MELSEC Safety - Training Documentation -
Advertisements

EECE499 Computers and Nuclear Energy Electrical and Computer Eng Howard University Dr. Charles Kim Fall 2013 Webpage:
Dynamic Self-Checking Techniques for Improved Tamper Resistance Bill Horne, Lesley Matheson, Casey Sheehan, Robert E. Tarjan STAR Lab, InterTrust Technologies.
 Description of PressurePro System  Identify system components  Display and Operational Modes  Sensor alerts  Checking of tire pressures  Manual.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development.
© 2005 by Prentice Hall Chapter 4 System Testing & Implementation Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph.
U NIVERSITY OF M ASSACHUSETTS, A MHERST Department of Electrical and Computer Engineering.
System for Engine Location Of a Web Train Paul Wimmer and Adam Weintrop Dr. Irwin and Dr. Schertz 2/27/06.
1 CMSC 132: Object-Oriented Programming II Software Development III Department of Computer Science University of Maryland, College Park.
Data Structures and Programming.  John Edgar2.
Software Integration and Documenting
PRACTICAL ELECTRICITY
Min Kwan Park Test Tech Lead Visual C# QA team. Fail fast To-Dos for fail fast Analyze issues Information for further action Q&A Agenda.
Problem Solving and Diagnostic Skills Software Maintenance.
Software faults & reliability Presented by: Presented by: Pooja Jain Pooja Jain.
System Implementation. System Implementation and Seven major activities Coding Testing Installation Documentation Training Support Purpose To convert.
TESTING.
Chapter 9 PLC and System Maintenance
Temperature Controller DT3 Series & Delta Machine Vision Automation for a Changing World.
Therac 25 Nancy Leveson: Medical Devices: The Therac-25 (updated version of IEEE Computer article)
Verification and Validation Overview References: Shach, Object Oriented and Classical Software Engineering Pressman, Software Engineering: a Practitioner’s.
© Cisco Systems, Inc. All rights reserved. Cisco Public ITE PC v4.1 Chapter 4 1 Chapter 12: Advanced Troubleshooting IT Essentials v5.0.
Lecture 11 Testing and Debugging SFDV Principles of Information Systems.
Version 3 Troubleshooting PC Hardware Module 13. Version 3 2 Troubleshooting Basics Effective troubleshooting uses techniques to diagnose and fix computer.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
 Once the system has been installed it will be monitored to check whether it is working correctly. Sometimes problems with a system will not be found.
LSST Camera CD-3 Review Brookhaven National Laboratory, Brookhaven, NY LSST Safety Council Camera Review Bremerton, WA 2015 LSST Camera Environment,
1 Life Cycle of Software Specification Design –Risk Analysis –Verification Coding Testing –Refining –Production Maintenance.
IT Essentials: PC Hardware and Software v4.0. Chapter 4 Objectives 4.1 Explain the purpose of preventive maintenance 4.2 Identify the steps of the troubleshooting.
Troubleshooting Foundations of Technology Troubleshooting © 2013 International Technology and Engineering Educators Association, STEM  Center for Teaching.
Reliability & Maintainability Engineering An Introduction Robert Brown Electrical & Computer Engineering Worcester Polytechnic Institute.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 10 Systems Implementation.
1 Introduction to Software Testing. Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Chapter 1 2.
Verification and Validation Assuring that a software system meets a user's needs.
The basics of the programming process The development of programming languages to improve software development Programming languages that the average user.
RELIABILITY ENGINEERING 28 March 2013 William W. McMillan.
1 Chapter 26 Cleanroom Software Engineering Cleanroom Developed in early 80’s by Harlan Mills Reported very good results –reliable, high-quality.
Troubleshooting PC Hardware. Troubleshooting Steps 1. Identify the problem 2. Gather Information 3. Develop & implement a solution 4. If the problem isn't.
Software Engineering 2004 Jyrki Nummenmaa 1 BACKGROUND There is no way to generally test programs exhaustively (that is, going through all execution.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
Copyright © 2002 Delmar Thomson Learning Chapter 14 Documenting Your PLC System.
5.01 Understand Different Types of Programming Errors
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
BASIC SECURITY THREATS TO INFORMATION SYSTEMS. All information systems linked up in networks are prone to security violations. All information systems.
Lean Six Sigma: Process Improvement Tools and Techniques Donna C. Summers © 2011 Pearson Higher Education, Upper Saddle River, NJ All Rights Reserved.
Software Troubleshooting Eliminate possible programming and timing errors by stopping all programs ( and ). Use the Executive program terminal and send.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
The Troubleshooting Process. Hardware Maintenance Make sure that the hardware is operating properly.  Check the condition of parts.  Repair or replace.
Control System and Automatic Sequences
5.01 Understand Different Types of Programming Errors
Computer troubleshooting
Chapter 9, Testing.
Verification and Testing
Verification and Validation Overview
Fault Tolerance In Operating System
ECE 477 Final Presentation Team 8 Spring 2013
GE 6757 TOTAL QUALITY MANAGEMENT
Failure and Design Jaime Baber October 12, 2000
5.01 Understand Different Types of Programming Errors
Software testing strategies 2
Lecture 09:Software Testing
Verification and Validation Unit Testing
Computer troubleshooting
Chapter 2. Problem Solving and Software Engineering
The Troubleshooting theory
PSS0 Configuration Management,
Computer in Safety-Critical Systems
Software Development Plan and Software Requirements
Presentation transcript:

Chapter - Software Engineering Fail safe design problems Component jams Operator detected failure Erroneous input Unsafe modes Programming errors Sabotage Random failure

Debugging Programs A fail-safe design Proper programming techniques Modular programs Predictable, non-configured programs Inaccessible to unauthorized persons Check for system OK at start-up. Built in functions for error and failure detection. People Clear and current documentation Training for new users and engineers

Debugging Minimized by good design techniques

Troubleshooting 1. Look at the process 2. PLC error lights HALT - something has stopped the CPU RUN - the PLC thinks it is OK (and probably is) ERROR - a physical problem has occurred with the PLC 3. Indicator lights on I/O cards and sensors 4. Consult the manuals, or use software if available 5. Call for help

Process Modeling

Function Diagrams

Design steps for verification 1. Structured design 2. Modular testing 3. Code review 4. Modular building 5. Design confirmation 6. Error proofing 7. Burn-in

Documentation

Commissioning 1. Visual inspection 2. Mechanical installation 3. Electrical installation 4. Functional tests 5. Process verification 6. Contract/specification verification 7. Put into production