CEA LIST Expression of interest: dt-fof

Slides:



Advertisements
Similar presentations
Ways to Improve the Hazard Management Process
Advertisements

Medical Device Software Development
2009 – E. Félix Security DSL Toward model-based security engineering: developing a security analysis DSML Véronique Normand, Edith Félix, Thales Research.
Presentation by Prabhjot Singh
Guaranteed Component Assembly with Round Trip Analysis for Energy Efficient High-integrity Multi-core Systems Artemis-AAL day 7 May, Budapest 1BME and.
Software system modeling
4.1 Blended approaches: Information Engineering IMS Information Systems Development Practices.
Software Testing and Quality Assurance
Developing safety critical systems
Software Engineering for Safety : A Roadmap Presentation by: Manu D Vij CS 599 Software Engineering for Embedded Systems.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
CSC 402, Fall Requirements Analysis for Special Properties Systems Engineering (def?) –why? increasing complexity –ICBM’s (then TMI, Therac, Challenger...)
João Batista Camargo Jr Safety Analysis Group (GAS) Computer and Digital Systems Engineering Department (PCS) Escola Politécnica.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Quality Risk Management ICH Q9 Annex I: Methods & Tools
Testing safety-critical software systems
Chapter 3 Software Processes.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR ESM'2009, October 26-28, 2009, Holiday Inn Leicester, Leicester, United Kingdom.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
What is UML? What is UP? [Arlow and Neustadt, 2005] January 23, 2014
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 3 Slide 1 Software Processes l Coherent sets of activities for specifying, designing,
Views from different perspectives
FAULT TREE ANALYSIS (FTA). QUANTITATIVE RISK ANALYSIS Some of the commonly used quantitative risk assessment methods are; 1.Fault tree analysis (FTA)
1 FRENCH PROPOSAL FOR ESARR6 1 - BACKGROUND - 15/02/00 : Kick-off meeting, Presentation of the CAA/SRG input (SW01), Request from the chairman to comment.
Safety-Critical Systems 5 Testing and V&V T
Quality Assurance.
Safety-Critical Systems 7 Summary T V - Lifecycle model System Acceptance System Integration & Test Module Integration & Test Requirements Analysis.
Software Safety Case Why, what and how… Jon Arvid Børretzen.
Over View of CENELC Standards for Signalling Applications
Toulouse, September 2003 Page 1 JOURNEE ALTARICA Airbus ESACS  ISAAC.
Center for Reliability Engineering Integrating Software into PRA B. Li, M. Li, A. Sinha, Y. Wei, C. Smidts Presented by Bin Li Center for Reliability Engineering.
RLV Reliability Analysis Guidelines Terry Hardy AST-300/Systems Engineering and Training Division October 26, 2004.
Safety methods within Agile and RUP methods TORGRIM LAURITSEN BUCS project.
Toward a New ATM Software Safety Assessment Methodology dott. Francesca Matarese.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
An Integrated Model-Based Approach to System Safety and Aircraft System Architecture Development Eric Villhauer – Systems Engineer Brian Jenkins – System.
M&CML: A Monitoring & Control Specification Modeling Language
Model-based design inspection based on traceability information models and design slicing Shiva Nejati April 15, 2015.
Medical Device Software Development
Introduction to Project Management
Software Testing.
Prototyping in the software process
Software Prototyping.
PRA: Validation versus Participation in Risk Analysis PRA as a Risk Informed Decision Making Tool Richard T. Banke– SAIC
Installations Systems and
TQS - Teste e Qualidade de Software (Software Testing and Quality) Test Case Design – Model Based Testing João Pascoal.
SysML 2.0 Formalism: Requirement Benefits, Use Cases, and Potential Language Architectures Formalism WG December 6, 2016.
Chapter 6: Database Project Management
What is UML? What is UP? [Arlow and Neustadt, 2005] October 5, 2017
Towards connecting geospatial information and statistical standards in statistical production: two cases from Statistics Finland Workshop on Integrating.
FMEA.
Safety and Risk.
Software Processes (a)
UML: Unified modeling language
Software Prototyping Animating and demonstrating system requirements.
The Extensible Tool-chain for Evaluation of Architectural Models
Regulatory Oversight of HOF in Finland
Chapter 5 Architectural Design.
Baisc Of Software Testing
New Assessment & Test Methods
Requirements Engineering Process – 1
Software system modeling
Software Engineering for Safety: a Roadmap
PSS verification and validation
Uml diagrams In ooad.
ISO and TR Update for FDA Regulated Industries
Review and comparison of the modeling approaches and risk analysis methods for complex ship system. Author: Sunil Basnet.
Presentation transcript:

CEA LIST Expression of interest: dt-fof-02-2018 Juan Cadavid CEA LIST, Software and Systems Engineering department Juan.Cadavid@cea.fr

Software and systems engineering department CEA TECH: Overview CEA TECH: A many domains RTO: LIST-LETI-LITEN, a go-between research and innovation Software and systems engineering department 15+ years in model-driven design, formal techniques, proof, safety & security of systems Expertise and commitment to standards Large world-wide engineering tools development Papyrus, Frama-C

Expression of interest: dt-fof-02-2018 “Past research to implement HRC in an industrial setting concentrated largely on safety of humans… This has already led to production environments with safe interaction between humans and robots… However more attention has to be paid to develop novel inherently-safe robotic concepts where collaboration with humans is taken up already in the design phase… Proposals should cover development of methods for robotic hazard assessment and risk management to clarify trade-offs between productivity and safety for mixed human-robot smart devices environments… and reduction in product reconfiguration time and cost”

Eclipse Safety Framework Eclipse Safety Framework provides a set of tools for integrating safety techniques within a model driven engineering process based on both modelling standards, SysML and MARTE. Model-Based Safety Analysis relies on the idea that safety analysis activities can follow the design process in a parallel flow using the system functional and physical architectures as a common basis. The system model is used to capture the overall architectures and the interactions between their components. Models may be enriched with dedicated annotations in order to describe possible dysfunctional behaviours.

Eclipse Safety Framework ESF allows better interactivity between design and safety assessment activities. A dysfunctional model is built from the system model. It is used to specify possible failure-modes, mitigation barriers and propagation behaviour at components level. From the specification of feared events (expressed in safety requirements), it can then with an automatic global analysis produce propagation paths and corresponding fault trees. The dysfunctional model can be improved in an iterative way, until the safety requirements are fully satisfied. Finally, reports can be exported in different formats (e.g. HTML and PDF) to document the analyses hypothesis and results.

Eclipse safety framework A complete toolset: FMEA and FMECA FTA, fault tree generation, minimal cut sets, probabilistic calculations Safety Requirements derivation Automatic report generation We show how to simulate the dysfunctional behavior of the system and Fault Circumvention Process Visualization (through animation) of the faulty module Identification of the fault circumvention process Execution of the model to apply the circumvention procedure directly on the factory Safety Analysis Simulation of dysfunctional behaviour Fault Circumvention Process

Inherently-safe system design: Hazard assessment Safety Requirements Specification and Derivation

Inherently-safe system design: Hazard assessment Hazard criticality assessment over system architecture

Eclipse Robotml: model-based design of robotics systems Standard RAMI 4.0 On utilise RobotML pour modéliser les composants de chacun des modules de l’usine MANUFLEX Carnot Project| 9

Thanks! Juan Cadavid CEA LIST, Software and Systems Engineering department Juan.Cadavid@cea.fr