Develop a Safety Assurance approach for Complex Systems (Problem Definition) Supervisors: Tim Kelly, Rob Alexander Chris Leong HISE Group Giving a Presentation.

Slides:



Advertisements
Similar presentations
Vehicle-infrastructure integration: creating co-operative mobility systems and services Hearing EU Parliament, 22 January 2009 Hermann Meyer, CEO.
Advertisements

ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Lecture # 2 : Process Models
Unit 2. Software Lifecycle
Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University 1 Pittsburgh, PA Dennis Smith, David Carney and Ed Morris DEAS.
Vulnerability of Complex System Lokaltermin des ETH-Präsidenten Mittwoch, 1. Juli 2009 Laboratory for Safety Analysis.
Systems Engineering in a System of Systems Context
Interaction and adaptation in SCORM-based SE course Todorka Glushkova, University of Plovdiv, Bulgaria
Software Engineering Techniques for the Development of System of Systems Seminar of “Component Base Software Engineering” course By : Marzieh Khalouzadeh.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Site Skin Structure Services Space plan Stuff Software Architecture and Software Architecture Patterns (1)
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
1 FM Overview of Adaptation. 2 FM RAPIDware: Component-Based Design of Adaptive and Dependable Middleware Project Investigators: Philip McKinley, Kurt.
Equipment Capability Customer DAES Analysis-Experimentation-Simulation 1 DARP Workshop System of Systems Safety Cases Parallel Session 18 th & 19 th April.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
David Harrison Senior Consultant, Popkin Software 22 April 2004
Breakout Group 2: Software Quality Assurance Outcome 8/18/10 1.
The web application development process Basharat Mahmood, COMSATS Institute of Information Technology, Islamabad, Pakistan. 1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 2 Slide 1 Systems engineering 1.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR ESM'2009, October 26-28, 2009, Holiday Inn Leicester, Leicester, United Kingdom.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements l.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 19 Slide 1 Component-based software engineering 1.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Systems Thinking and Systems Engineering Introduction to the course 22 January 2013 Francois Christophe Galina Medyna Eric Coatanéa.
WHAT IS SYSTEM SAFETY? The field of safety analysis in which systems are evaluated using a number of different techniques to improve safety. There are.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 2Slide 1 Chapter 2 Computer-Based System Engineering As modified by Randy Smith.
Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Disaster Dynamics Five Year Plan 03-Dec Scientific Goals Disaster Dynamics transform descriptive case studies of natural hazard events into interactive.
ASG - Towards the Adaptive Semantic Services Enterprise Harald Meyer WWW Service Composition with Semantic Web Services
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 09. Review Introduction to architectural styles Distributed architectures – Client Server Architecture – Multi-tier.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Software Engineering Management Lecture 1 The Software Process.
Requirements Engineering ments_analysis.
CPSC 871 John D. McGregor Module 6 Session 3 System of Systems.
Design engineering Vilnius The goal of design engineering is to produce a model that exhibits: firmness – a program should not have bugs that inhibit.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
EMER: Engineering Critical Systems: human scale systems with emergence.
Development of Methodologies for Independent Verification and Validation of Neural Networks NAG OSMA-F001-UNCLASS Methods and Procedures.
1 | 2010 Lecture 1: Systems – what and why?. Covered in this lecture Systems and systems thinking Why we use Systems Engineering Systems from “cradle.
Open Platform for EvolutioNary Certification Of Safety-critical Systems Large-scale integrating project (IP) Nuanced Term-Matching to Assist in Compositional.
EMER: Engineering Critical Systems Human-scale systems with emergence.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Component Oriented Programming 1 Introduction to COP.
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. NFP Design Techniques Software Architecture Lecture 20.
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. NFP Design Techniques Software Architecture Lecture 20.
The Rational Unified Process 1 EECS810: Software Engineering.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
Toulouse, September 2003 Page 1 JOURNEE ALTARICA Airbus ESACS  ISAAC.
Csci 490 / Engr 596 Special Topics / Special Projects Software Design and Scala Programming Spring Semester 2010 Lecture Notes.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
© Drexel University Software Engineering Research Group (SERG) 1 The OASIS SOA Reference Model Brian Mitchell.
Requirements Engineering ments_analysis.
Architecture Tradeoff Analysis Method Software Engineering Institute Carnegie Mellon University Presented by: Senthil ayyasamy CS 590l- winter 2003.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Component-based Software Engineering CBSE seminar, Oslo, 4 Feb Christian Bunse
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
ARO Workshop Wendy Roll - May 2004 Topic 4: Effects of software certification on the current balance between software/system modeling, analysis and testing.
Alex Ezrakhovich Process Approach for an Integrated Management System Change driven.
1 Software Testing and Quality Assurance Lecture 38 – Software Quality Assurance.
SRA Key Topics Reference Architectures for Cyber-Physical Systems Dr. Christian El Salloum AVL List GmbH.
ARTEMIS SRA 2016 Trust, Security, Robustness, and Dependability Dr. Daniel Watzenig ARTEMIS Spring Event, Vienna April 13, 2016.
Industrial Emergency Response for Municipal-Based Responders.
The Software Lifecycle Stuart Faulk. Definition Software Life Cycle: evolution of a software development effort from concept to retirement Life Cycle.
The Web Application Development Process Models
AIM Operational Concept
Presentation transcript:

Develop a Safety Assurance approach for Complex Systems (Problem Definition) Supervisors: Tim Kelly, Rob Alexander Chris Leong HISE Group Giving a Presentation - Nov 14

2 Problem Definition With more and more independent entities (systems and platforms) dynamically networking as a complex system to achieve a common purpose (e.g. operation and training), How safe is considered safe enough for such complex system? Is the current way of doing hazard and risk analysis and safety assessment sufficient to analyse such complex system? How can simulation help to make safety assessment of such complex system more effective and efficient? How do we consider the unique characteristics (e.g. adaptive and emergent) of such complex system as part of safety assessment?

3 What is Safety Assurance? Which description of Complex System best describes the problem space? Key Concepts Develop a Safety Assurance approach for Complex Systems

4 HA PSA SSA HA: Hazard Analysis Identifies potential hazards and safety risks of the system PSA: Preliminary Safety Assessment Performs safety analyses as the system is being developed to suggest design and architectural choices to meet safety goals SA: Safety Assessment Verifies compliance of the system architecture with the safety requirements Safety Assurance [Bozzano10] General safety assessment workflow

5 Properties System-of- Systems Open Adaptive Systems Cyber Physical Systems IndependenceYes Geographical distributedYes Emergent behaviourYes Evolutionary developmentYes Interface interactions Yes Complex System Cyber-Physical Systems (CPS) [Shi11] systems that integrate the dynamics of the physical processes with those of the software and communication, providing abstraction and modelling, design, and analysis techniques for the integrated world Open Adaptive Systems (OAS) [Trapp13] systems that dynamically connect to each other (openness) and adapt to a changing context at runtime (adaptive) System-of-Systems (SoS) [Kazman13] Is a set of systems that are cooperating while simultaneously working as independent entities Dynamic of Complex System [Yam97] A complex system is a system formed out of many components whose behaviour is emergent, that is, the behaviour of the system cannot be simply inferred from the behaviour of its components. The amount of information necessary to describe the behaviour of such a system is a measure of its complexity. ….

6 Safety assurance: Leverage on the different phases under the safety engineering practices to minimize the risks of operational hazards (e.g. HRA, PSA, SSSA, certification, awareness). Complex Systems: Intend is not to present a unified definition but to gain awareness of the unique characteristics compared to monolithic systems (e.g. independence, emergent behaviour, evolutionary) Summary