ARTEMIS SRA 2016 Trust, Security, Robustness, and Dependability Dr. Daniel Watzenig ARTEMIS Spring Event, Vienna April 13, 2016.

Slides:



Advertisements
Similar presentations
Information Society Technologies programme 1 IST Programme - 8th Call Area IV.2 : Computing Communications and Networks Area.
Advertisements

Avionics Panel Go For Luna Landing! Graham ONeil United Space Alliance March 2008.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Distributed Systems Architectures Slide 1 1 Chapter 9 Distributed Systems Architectures.
EECE499 Computers and Nuclear Energy Electrical and Computer Eng Howard University Dr. Charles Kim Fall 2013 Webpage:
Distributed Systems 1 Topics  What is a Distributed System?  Why Distributed Systems?  Examples of Distributed Systems  Distributed System Requirements.
Introduction to Cyber Physical Systems Yuping Dong Sep. 21, 2009.
Dynamic Service Composition with QoS Assurance Feb , 2009 Jing Dong UTD Farokh Bastani UTD I-Ling Yen UTD.
Network Management Overview IACT 918 July 2004 Gene Awyzio SITACS University of Wollongong.
Software Engineering for Real- Time: A Roadmap H. Kopetz. Technische Universitat Wien, Austria Presented by Wing Kit Hor.
Designing the system Conceptual design and technical design
Distributed Systems Architectures
CS599 Software Engineering for Embedded Systems1 Software Engineering for Real-Time: A Roadmap Presentation by: Mandar Samant Raghbir Singh Banwait.
1 Quality Objects: Advanced Middleware for Wide Area Distributed Applications Rick Schantz Quality Objects: Advanced Middleware for Large Scale Wide Area.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 30 Slide 1 Security Engineering.
Ensuring Non-Functional Properties. What Is an NFP?  A software system’s non-functional property (NFP) is a constraint on the manner in which the system.
Network Enabled Capability Through Innovative Systems Engineering Service Oriented Integration of Systems for Military Capability Duncan Russell, Nik Looker,
.NET Mobile Application Development Introduction to Mobile and Distributed Applications.
Lecture 1.
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 12 Slide 1 Distributed Systems Design 1.
WORKFLOWS IN CLOUD COMPUTING. CLOUD COMPUTING  Delivering applications or services in on-demand environment  Hundreds of thousands of users / applications.
WORK PROGRAMME 2014 – 2015 Topic ICT 9: Tools and Methods for Software Development Odysseas I. PYROVOLAKIS European Commission DG CONNECT Software & Services,
Issues and Ideas in Software Reliability for FCS Joe Loyall BBN Technologies.
Chapter 1: Hierarchical Network Design
Chapter 1- Introduction
Whitacre College of Engineering Panel Interdisciplinary Cybersecurity Education Texas Tech University NSF-SFS Workshop on Educational Initiatives in Cybersecurity.
Chapter 1- Introduction Lecture 1 Ready, fire, aim (the fast approach to software development). Ready, aim, aim, aim, aim... (the slow approach to software.
S1.6 Requirements: KnightSat C&DH RequirementSourceVerification Source Document Test/Analysis Number S1.6-1Provide reliable, real-time access and control.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
No: 1 CEMSIS 1 WP3 - Use of pre-developed products Key issues N. Thuy EDF R&D.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,
1 소프트웨어공학 강좌 Chap 9. Distributed Systems Architectures - Architectural design for software that executes on more than one processor -
Distributed Intelligent Sensing and Control (DISC) for Automotive Factory Automation. Dr. Robert Brennan Dr. Ningxu Cai Mohammad Gholami.
Software engineering. What is software engineering? Software engineering is an engineering discipline which is concerned with all aspects of software.
IMPROUVEMENT OF COMPUTER NETWORKS SECURITY BY USING FAULT TOLERANT CLUSTERS Prof. S ERB AUREL Ph. D. Prof. PATRICIU VICTOR-VALERIU Ph. D. Military Technical.
ICT-NCP Meeting 12 May 2009 Dr. Jorge Pereira DG INFSO G3 Embedded Systems and Control
Networks Of Mobile Arbitrary Devices (NOMADs) Miroslaw Malek Humboldt-University Berlin, Germany
Tools and Technology Development Hardware-in-the-Loop Dennis Culley NASA Glenn Research Center Collaboration Forum Ohio Aerospace Institute August 25,
Advanced Computer Networks Topic 2: Characterization of Distributed Systems.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 3.
Investigating Survivability Strategies for Ultra-Large Scale (ULS) Systems Vanderbilt University Nashville, Tennessee Institute for Software Integrated.
Networked Embedded and Control Systems WP ICT Call 2 Objective ICT ICT National Contact Points Mercè Griera i Fisa Brussels, 23 May 2007.
Information Technology Needs and Trends in the Electric Power Business Mladen Kezunovic Texas A&M University PS ERC Industrial Advisory Board Meeting December.
10/03/05 Johan Muskens ( TU/e Computer Science, System Architecture and Networking.
Safety-Critical Systems 7 Summary T V - Lifecycle model System Acceptance System Integration & Test Module Integration & Test Requirements Analysis.
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
Use of Fieldbus in safety related systems, an evaluation study of WorldFIP according to proven-in-use concept of IEC Jean Pierre Froidevaux WorldFIP.
1 CALL 6 Key Action IV Introduction and Action Lines: IV.1.2, IV.2.1, IV.2.2, IV.2.4 Brussels, 16. Jan 2001 Colette Maloney European Commission.
Enabling the Future Service-Oriented Internet (EFSOI 2008) Supporting end-to-end resource virtualization for Web 2.0 applications using Service Oriented.
1 V&V Needs for NextGen of 2025 and Beyond A JPDO Perspective Maureen Keegan JPDO Integration Manager October 13, 2010.
Abstract A Structured Approach for Modular Design: A Plug and Play Middleware for Sensory Modules, Actuation Platforms, Task Descriptions and Implementations.
Jacques Bus Head of Unit, DG INFSO-F5 “Security” European Commission FP7 launch in the New Member States Regional on-line conference 22 January 2007 Objective.
Real-Time Systems, Events, Triggers. Real-Time Systems A system that has operational deadlines from event to system response A system whose correctness.
Slide 1 Security Engineering. Slide 2 Objectives l To introduce issues that must be considered in the specification and design of secure software l To.
"... To design the control system that effectively matches the plant requires an understanding of the plant rivaling that of the plant's designers, operators,
CSC 480 Software Engineering Lecture 17 Nov 4, 2002.
©Ian Sommerville 2000, Tom Dietterich 2001 Slide 1 Distributed Systems Architectures l Architectural design for software that executes on more than one.
Euro-Par, HASTE: An Adaptive Middleware for Supporting Time-Critical Event Handling in Distributed Environments ICAC 2008 Conference June 2 nd,
SRA Key Topics Reference Architectures for Cyber-Physical Systems Dr. Christian El Salloum AVL List GmbH.
SRA 2016 – Strategic Research Challenges Design Methods, Tools, Virtual Engineering Jürgen Niehaus, SafeTRANS.
Session 1: Technology Development August 15 NSF Workshop.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 5:Architectural Design l Establishing the overall structure of a software.
IOT Critical Impact on DC Design
Security Engineering.
Avionics Panel Go For Luna Landing!
Software Architecture Lecture 20
Self-Managed Systems: an Architectural Challenge
Luca Simoncini PDCC, Pisa and University of Pisa, Pisa, Italy
Presentation transcript:

ARTEMIS SRA 2016 Trust, Security, Robustness, and Dependability Dr. Daniel Watzenig ARTEMIS Spring Event, Vienna April 13, 2016

Ideal house – building blocks

Content of the chapter Dependability Security Robustness Resilience Standardisation Research challenges

Dependability - standards International Electrotechnical Commission Technical Committee 56 (IEC TC 56)

R&D&I challenges Systematic software engineering methods – to reduce the development complexity and increase reliability and robustness by using appropriate software models and abstractions. Dynamic configuration – as components appear and disappear as CPS devices, and communication links are established/released depending on the actual availability of network connectivity. Self-diagnostic tools and robust control algorithms – that ensure adaptability and survivability in the presence of security attacks, random faults, unpredictable events, uncertain information, and so-called sensor false positives (sensor misinterpretations). Inclusion of models of the incentives of human decision makers in the design process to improve CPS resilience. Scalable health management architectures – integrating diagnostic and prognostic capabilities from CPS to system of systems (from single board to complete aircraft) for reducing logistic impacts and Life Cycle Costs Evaluation and experimentation – using extended simulation and test-bed infrastructures for an integration of Cyber- Physical Systems Platforms that directly interface with human decisions.

R&D&I challenges Architectures – which support distribution, modularity, and fault containment units in order to isolate faults. Secure real-time systems Transparent fault tolerance – Advanced hardware-related and software-implemented fault-injection for dependability evaluation. – Provision of a generic fault-tolerance layer, independent of the application – Tolerance with respect to arbitrary failure modes of components – On-line maintenance of fault-tolerant systems – Automated reconfiguration

R&D&I challenges Certification and component-based recertification of high-dependability applications – Modular certification of a composable design – Validation of high dependability – Proof of absence of failure modes with high impact (safety criticality) – Independent validation of component interface properties – Integration and validation of legacy systems – Worst-case execution time (WCET) research (hardware, algorithms, tools) – Standardised procedures and processes to develop and design dependable SoS …

Ultimately we want From fail-safe to fail-operational (fault-tolerance, multiple redundancy) From expensive prototypes/solutions to low cost reliability and minimal redundancy based on reliable software Autonomous CPS in unconstrained operational environments trusting the dependability and robustness of multi-vendor distributed system components, tolerating environmental uncertainty, and ensuring sufficiently rigorous validation of autonomous CPS in order to attain very low failure rates. 24/7 reliability, with 100% availability, and 100% connectivity, in addition to the real-time response (time-critical, i.e. deadlines defined by the system integrators). Dependability can no longer be considered as an aspect of single, separate and encapsulated devices, but in a more and more connected world must be regarded as dependability of systems of systems (SoS).

ARTEMIS SRA 2016 April 13, 2016, Vienna