Technological Failures

Slides:



Advertisements
Similar presentations
Testing and Quality Assurance
Advertisements

T. E. Potok - University of Tennessee Software Engineering Dr. Thomas E. Potok Adjunct Professor UT Research Staff Member ORNL.
Nana Akua Sarkodie-Mensah, Catherine Melendez.  In 1999, people around the world believed that on January 1, 2000 our lives would be changed forever.
IBM Haifa Research Lab IBM Haifa Labs An Open Source Simulation Model of Software Testing Shmuel Ur Elad Yom-Tov Paul Wernick
What Causes Software Vulnerabilities? _____________________ ___________ ____________ _______________   flaws in developers own code   flaws resulting.
BY RAJESWARI S SOFTWARE TESTING. INTRODUCTION Software testing is the process of testing the software product. Effective software testing will contribute.
Software maintenance Managing the processes of system change.
SEG Software Maintenance1 Software Maintenance “The modification of a software product after delivery to correct faults, to improve performance or.
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
Ethical and Social...J.M.Kizza 1 Module 8: Software Issues: Risks and Liabilities Definitions Causes of Software Failures Risks Consumer Protection Improving.
What if you suspect a security incident or software vulnerability? What if you suspect a security incident at your site? DON’T PANIC Immediately inform:
CS 501: Software Engineering Fall 1999 Lecture 16 Verification and Validation.
Information System Security and Control
Software Testing Testing principles. Testing Testing involves operation of a system or application under controlled conditions & evaluating the results.
What if you suspect a security incident or software vulnerability? What if you suspect a security incident at your site? DON’T PANIC Immediately inform:
Protecting the Public, Astronauts and Pilots, the NASA Workforce, and High-Value Equipment and Property Mission Success Starts With Safety Believe it or.
Dropbox security glitch CASE STUDY Lewis Scaife SYSM 6309 Advanced Requirements Engineering Summer 2013 Professor – Dr. Lawrence Chung.
1 Ontology Summit 2011 Track 3 Value Metrics & Value Models Ontology Use - Maintenance Todd Schneider Raytheon 17 February 2011.
PRESENTER PRIYANKA GUPTA.  Testing the complete system with respect to requirements.  In System testing, the functionalities of the system are tested.
EMGT 506 Challenger Case Study Question 2 Group B.
Economic Justification. Good Enough Quality Time to market Time to market Time to profit Time to profit.
SOFTWARE ENGINEERING MCS-2 LECTURE # 2. ATTRIBUTES OF GOOD S/W  Maintainability;  S/w should be written in such a way that it may evolve to meet the.
ITEC 370 Lecture 21 Testing. Review Questions? Project update on F Bug reporting –Software –Classification / Communication / Responsibilities.
Arrow Math Follow The Arrows Around The Grid. 25 Grid
ITEC 370 Lecture 22 Maintenance. Review Questions? Project update on F, next F give prototype demonstration Interface testing –Checklist of design features.
ITEC 370 Lecture 18 Testing. Review Questions? Design document due W –System can be implemented just by following it Implementation –Methods (prototype,
Operational Issues. Operational Changes It is important to organisations to ensure that they abide by the Law when caring for the safety of their employees,
ITEC 370 Lecture 20 Testing. Review Questions? Project update on F Test plan –Sections –How / when to use it.
1 Saltzer [1974] and later Saltzer and Schroeder [1975] list the following principles of the design of secure protection systems, which are still valid:
Formal methods its uses and limitations. A little about formality Objective knowledge / information Objective knowledge / information Information brought.
Home Stretch 1CPS4: Java for Video Games The Home Stretch.
Software Development Module Code: CST 240 Chapter 6: Software Maintenance Al Khawarizmi International College, AL AIN, U.A.E Lecturer: Karamath Ateeq.
Configuration Management
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
PRA: Validation versus Participation in Risk Analysis PRA as a Risk Informed Decision Making Tool Richard T. Banke– SAIC
Regression Testing with its types
Software Testing Introduction CS 4501 / 6501 Software Testing
AUDACIOUS: USER DRIVEN ACCESS CONTROL WITH UNMODIFIED OPERATING SYSTEM
SEVERITY & PRIORITY RELATIONSHIP
Chapter 18 Maintaining Information Systems
Contact Norton Support Canada for Firewall Issues.
Configuration Management
Different Types of Testing
Putting It All Together
Putting It All Together
Introduction SOFTWARE ENGINEERING.
Software engineering – 1
A Trojan is a computer program that contains the malicious code and it misleads users and user's computer. It aims to designed to perform something is.
Business Should Adopt Agile Testing. Test Driven Development is an essential software development way that is made by an automated test program which.
Real Life Computer Science Stories
Software Quality Assurance
Test Planning Mike O’Dell (some edits by Vassilis Athitsos)
CSCI1600: Embedded and Real Time Software
Reliability and Safety
Chapter 9 – Software Evolution and Maintenance
Black Box Software Testing Fall 2004
Progression of Test Categories
CS240: Advanced Programming Concepts
Technological Failures
CSCI1600: Embedded and Real Time Software
Risk Management CSCE 489/689 (Software Security) Fall 2018
Baisc Of Software Testing
Chapter 8 Software Evolution.
That is the Question Jane Fraser, Electronic Arts
How might a digital footprint effect my future
Can you find all the ways to solve them?
Digital Signatures Network Security.
The Home S t r e t c h.
CREDIT BUILDER CARD How Does It Work?
ACE – Auditing Control Environment
Presentation transcript:

Technological Failures Biggest challenges are foreseeing a technologies impact before it is put into widespread use. Even if the problems are foreseen, humans may be unable to prevent failure of a technology if cultural and social issues get in the way (e.g. NASA culture and org. structure). Poorly designed interface of complex systems can lead to devastating accidents (e.g. cluttered control panels). For digital technology – complexity and security issues dominate concerns Denial of service attacks, power grid dependability Bug fixing is never 100% PhD in math can prove correctness of 10 lines of code/day Cyber attacks – cyberwar Media “spin” affects cultural public opinion Hindenburg, shuttle, nuclear power, etc. Ice fall off was normal on shuttle, bugs normal in testing with abnormal data but ignored in production X-ray SW, denial of service attack ITEC 102

Bugs in software Verify and validate Testing is expensive Testing is never done Users can do things never considered by developers codecs ITEC 102