Dependability ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August.

Slides:



Advertisements
Similar presentations
Auditing Computer-Based Information Systems
Advertisements

Software Fault Injection for Survivability Jeffrey M. Voas & Anup K. Ghosh Presented by Alison Teoh.
Lecture 1: Overview modified from slides of Lawrie Brown.
Term Paper OLOMOLA,Afolabi( ). Dependability Modellling.
Fundamentals of Computer Security Geetika Sharma Fall 2008.
Software Engineering Lecture 2 ASPI8-4 Anders P. Ravn, Feb
Dependability TSW 10 Anders P. Ravn Aalborg University November 2009.
Software Fault Tolerance – The big Picture RTS April 2008 Anders P. Ravn Aalborg University.
1 ITC242 – Introduction to Data Communications Week 12 Topic 18 Chapter 19 Network Management.
CSE 322: Software Reliability Engineering Topics covered: Dependability concepts Dependability models.
Process ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August.
Presented By: Vinay Kumar.  At the time of invention, Internet was just accessible to a small group of pioneers who wanted to make the network work.
Mini Project ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August.
ABCSG - Dependable Systems - 01/06/ ABCSG Dependable Systems.
Dependability ITV Real-Time Systems Anders P. Ravn Aalborg University February 2006.
Documentation ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August.
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The need for comprehensive software quality requirements Classification.
Software Fault Tolerance – The big Picture mMIC-SFT September 2003 Anders P. Ravn Aalborg University.
Introduction ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August.
Safety Assessment (Fault Trees) ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg.
EEC 693/793 Special Topics in Electrical Engineering Secure and Dependable Computing Lecture 2 Wenbing Zhao Department of Electrical and Computer Engineering.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 10 Slide 1 Formal Specification.
Summary and Safety Assessment mMIC-SFT November 2003 Anders P. Ravn Aalborg University.
Issues on Software Testing for Safety-Critical Real-Time Automation Systems Shahdat Hossain Troy Mockenhaupt.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 10 Slide 1 Critical Systems Specification 3 Formal Specification.
EADS TEST & SERVICES TS/EL/T N°08_04/08 Page 1© Copyright EADS TEST & SERVICES 2008 Engineering Process for Systems Testability Analysis. Presentation.
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
Auditing Logical Access in a Network Environment Presented By, Eric Booker and Mark Ren New York State Comptroller’s Office Network Security Unit.
CCSB223/SAD/CHAPTER141 Chapter 14 Implementing and Maintaining the System.
Software Testing and Reliability Software Test Process
Standard WBS Version 1.0 WBS2-3.pptPage 1 Standard Work Breakdown Structure Legend = Decomposes to lower level WBS elements 4.0 Implementation 4.0 Implementation.
CPIS 357 Software Quality & Testing
How Hospitals Protect Your Health Information. Your Health Information Privacy Rights You can ask to see or get a copy of your medical record and other.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
WXGE6103 Software Engineering Process and Practice Formal Specification.
Ch. 1.  High-profile failures ◦ Therac 25 ◦ Denver Intl Airport ◦ Also, Patriot Missle.
Chapter 1 Overview The NIST Computer Security Handbook defines the term Computer Security as:
M. Frize, Winter 2003 Reliability and Medical Devices Prof. Monique Frize, P. Eng., O.C. ELG5123/ February 2003.
Replicated State Machines ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg.
Building Dependable Distributed Systems Chapter 1 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
Code Complete Steve McConnell. 20. The Software-Quality Landscape.
Quality of System requirements 1 Performance The performance of a Web service and therefore Solution 2 involves the speed that a request can be processed.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
Lecture 14 Maintaining the System and Managing Software Change SFDV Principles of Information Systems.
Software quality factors
Safety-Critical Systems 7 Summary T V - Lifecycle model System Acceptance System Integration & Test Module Integration & Test Requirements Analysis.
Lecture slides prepared for “Computer Security: Principles and Practice”, 3/e, by William Stallings and Lawrie Brown, Chapter 1 “Overview”. © 2016 Pearson.
CS 505: Thu D. Nguyen Rutgers University, Spring CS 505: Computer Structures Fault Tolerance Thu D. Nguyen Spring 2005 Computer Science Rutgers.
Formal Methods in Software Engineering Credit Hours: 3+0 By: Qaisar Javaid Assistant Professor.
Formal Methods in SE Software Verification Using Formal Methods By: Qaisar Javaid, Assistant Professor Formal Methods1.
Basic Concepts of Dependability Jean-Claude Laprie DeSIRE and DeFINE Workshop — Pisa, November 2002.
Diversity for Dependability * Jean-Claude Laprie PRDC’99 — December 16-17, 1999 — Hong Kong * Elaboration on «Diversity against Accidental and Deliberate.
1 5/18/2007ã 2007, Spencer Rugaber Architectural Styles and Non- Functional Requirements Jan Bosch. Design and Use of Software Architectures. Addison-Wesley,
1 INTRUSION TOLERANT SYSTEMS WORKSHOP Phoenix, AZ 4 August 1999 Jaynarayan H. Lala ITS Program Manager.
Thomas L. Gilchrist Testing Basics Set 3: Testing Strategies By Tom Gilchrist Jan 2009.
Application of Fault Injection to Globus Grid Middleware Nik Looker & Jie Xu University of Leeds, Leeds. LS2 9JT, UK Tianyu Wo & Jinpeng Huai Beihang University,
Attributes Availability Reliability Safety Confidentiality Integrity Maintainability Dependability Means Fault Prevention Fault Tolerance Fault Removal.
 Software Testing Software Testing  Characteristics of Testable Software Characteristics of Testable Software  A Testing Life Cycle A Testing Life.
Safety Assessment: Safety Integrity Levels
Langley Research Center An Architectural Concept for Intrusion Tolerance in Air Traffic Networks Jeffrey Maddalon Paul Miner {jeffrey.m.maddalon,
CS646: Software Design and Architectures Introduction and Overview †  Definitions.  The general design process.  A context for design: the waterfall.
By: Mark Reed.  Protecting information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction.
CS457 Introduction to Information Security Systems
Software Dependability
Final HIPAA Security Rule
IoTSec Taxonomy Proposal
Chapter 8 Software Evolution.
Fault Tolerance Distributed
Luca Simoncini PDCC, Pisa and University of Pisa, Pisa, Italy
Presentation transcript:

Dependability ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August 2011

Basic Concepts Availability: readiness for correct service. Reliability: continuity of correct service. Safety: absence of catastrophic consequences. Confidentiality: absence of unauthorized disclosure of information Integrity: absence of improper system alterations. Maintainability: ability to undergo modifications.

Other terms

Threats and Means

Development Phase and Faults 1.the physical world with its natural phenomena, 2.human developers, some possibly lacking competence or having malicious objectives, 3.development tools: software and hardware used by the developers to assist them in the development process. 4.production and test facilities. Fault * prevention ? * tolerance ? * removal ? * prediction ?

Use Phase and Faults 1.the physical world with its natural phenomena, 2.administrators (including maintainers): entities (humans or other systems) that have the authority to manage, modify, repair and use the system; some authorized humans may lack competence or have malicious objectives; 3.users: entities that receive service from the system at their use interfaces; 4.providers: entities that deliver services to the system at its use interfaces; 5.infrastructure: entities that provide specialized services to the system, such as information sources (e.g., time, GPS, etc.), communication links, power sources, cooling airflow, etc. 6.intruders: malicious entities that attempt to exceed any authority they might have and alter service or halt it, alter the system’s functionality or performance, or to access confidential information. Examples include hackers, vandals, corrupt insiders, agents of hostile governments or organizations, and malicious software. Fault * prevention ? * tolerance ? * removal ? * prediction ?

ElementaryFaultClassesElementaryFaultClasses

Combined classification

Failure Modes

Means Fault prevention removal prediction or forecasting tolerance

Fault prevention Systematic procedures Clean room (Harlan Mills) Inspection Reviews

Fault prevention Careful Design Conservative Design process (activities) notations tools robust functionality testability tracability

Fault Removal In Development 1.Verification and validation 2.Diagnosis 3.Correction In Use Preventive maintenance Corrective maintenance Fault isolation

Verification Techniques

Test approaches

Fault forecasting Qualitative evaluation Quantitative evaluation Models: Markov-processes, Fault-trees,...

Fault Forecasting Calculation – analysis of design Simulation – measurement on design Test -- measurement on implementation

Means

Exercise Where would you add prevention, removal and forecasting in a V-model process? What would you add? Requirements Spec Accpt. Test Report Acceptance Test Spec Architectural Spec Integr. Test Report Integration Test Spec Module Interface Spec Module Spec Module Test Report Module Test Spec Program Source text