João Batista Camargo Jr Safety Analysis Group (GAS) www.gas.pcs.poli.usp.br Computer and Digital Systems Engineering Department (PCS) Escola Politécnica.

Slides:



Advertisements
Similar presentations
XIAOXI XU AND CHENG-CHEW LIM, SENIOR MEMBER, IEEE IEEE TRANSACTIONS ON COMPUTER-AIDED DESIGN OF INTEGRATED CIRCUITS AND SYSTEMS, VOL. 29, NO. 6, JUNE 2010.
Advertisements

1 Universidade de São Paulo Brasil Safety Analysis Group (GAS) Computer and Digital Systems Engineering Department (PCS)
Design Concepts and Principles
Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University 1 Pittsburgh, PA Dennis Smith, David Carney and Ed Morris DEAS.
Prepared By: Certified Compliance Solutions, Inc. August 2012
Automated Analysis and Code Generation for Domain-Specific Models George Edwards Center for Systems and Software Engineering University of Southern California.
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.
Software Requirements
Software Engineering for Safety : A Roadmap Presentation by: Manu D Vij CS 599 Software Engineering for Embedded Systems.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
Course Instructor: Aisha Azeem
©Ian Sommerville 2006Critical Systems Slide 1 Critical Systems Engineering l Processes and techniques for developing critical systems.
©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.
MultiPARTES Towards Model-Driven Engineering for Mixed- Criticality Systems: MultiPARTES Approach A. Alonso, C. Jouvray, S. Trujillo, M.A. de Miguel, C.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
© Joseph F Iaquinto, PE May 14, © Joseph F Iaquinto, PE May 14, 2012 EAI / SOA Composite System A System Engineering Approach.
Evaluating Goal Achievement in Enterprise Modeling – An Interactive Procedure and Experiences Jennifer Horkoff 1 Eric Yu 2 1 Department of Computer Science,
1 Chapter 2 Socio-technical Systems (Computer-based System Engineering)
CLEANROOM SOFTWARE ENGINEERING.
VTT-STUK assessment method for safety evaluation of safety-critical computer based systems - application in BE-SECBS project.
©Ian Sommerville 2000 Software Engineering, 6th edition. Slide 1 Component-based development l Building software from reusable components l Objectives.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Management Information Systems: An Overview. SYSTEMS, DATA, AND INFORMATION A system is:  A set of interrelated components  That interact  To achieve.
1 Systems Engineering Process Review Mark E. Sampson EMIS 8340 Systems Engineering Tool—applying tools to engineering systems.
Formalizing the Asynchronous Evolution of Architecture Patterns Workshop on Self-Organizing Software Architectures (SOAR’09) September 14 th 2009 – Cambrige.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
SOFTWARE DESIGN.
Overview of Formal Methods. Topics Introduction and terminology FM and Software Engineering Applications of FM Propositional and Predicate Logic Program.
Intent Specification Intent Specification is used in SpecTRM
Chapter 13 Architectural Design
Software Design Deriving a solution which satisfies software requirements.
ARTEMIS JU Grant Agreement number ARTEMIS JU Grant Agreement number Sept 25-27, 2013 Riga Safety Certification of Software-intensive.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Integrating Systems: models and fault modes SESAM-möte, 19 Oktober, 2005 Jonas Elmqvist Real-Time Systems Laboratory Department of Computer and Information.
Lach1MAPLD 2005/241 Accessible Formal Verification for Safety-Critical FPGA Design John Lach, Scott Bingham, Carl Elks, Travis Lenhart Charles L. Brown.
Software Engineering Principles. SE Principles Principles are statements describing desirable properties of the product and process.
Open Platform for EvolutioNary Certification Of Safety-critical Systems Large-scale integrating project (IP) Nuanced Term-Matching to Assist in Compositional.
Chapter 4 프로세스 모델 Process Models
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.
Formal Methods.
Formal Methods in SE Software Verification Using Formal Methods By: Qaisar Javaid, Assistant Professor Formal Methods1.
National Research Council Of the National Academies
Hosted by: Institute for Software Integrated Systems (ISIS) Vanderbilt University Software Reliability for FCS Discussion Format May 18-19, 2004 ARO Workshop.
Industrial Avionics Working Group 18/04/07 The Relationship Between the Design and Safety Domains in IAWG Modular Certification Part 2: Completeness of.
ARO Workshop Wendy Roll - May 2004 Topic 4: Effects of software certification on the current balance between software/system modeling, analysis and testing.
Duminda WijesekeraSWSE 623: Introduction1 Introduction to Formal and Semi- formal Methods Based on A Specifier's Introduction to Formal Methods (J. Wing)
Design CS 470 – Software Engineering I Sheldon X. Liang, PH.D.
Lach1MAPLD 2005/241-W Accessible Formal Verification for Safety-Critical FPGA Design BOF-W Presentation John Lach, Scott Bingham, Carl Elks, Travis Lenhart.
Toward a New ATM Software Safety Assessment Methodology dott. Francesca Matarese.
About Us! Rob StockhamBA IEng MIEE General Manager Moore Industries-Europe, Inc MemberIEE Honorary Secretary ISA England Institute of Directors DirectorThe.
An Integrated Model-Based Approach to System Safety and Aircraft System Architecture Development Eric Villhauer – Systems Engineer Brian Jenkins – System.
Luca Pazzi, Marco Pradelli University of Modena and Reggio Emilia
Software Development and Safety Critical Decisions
CEA LIST Expression of interest: dt-fof
Lecture 9- Design Concepts and Principles
Software Design Methodology
Overview of System Engineering
Model-Driven Analysis Frameworks for Embedded Systems
COT 5611 Operating Systems Design Principles Spring 2012
Lecture 9- Design Concepts and Principles
Systems Engineering for Mission-Driven Modeling
Submitted by the experts of OICA
Department of Computer Science Abdul Wali Khan University Mardan
Automated Analysis and Code Generation for Domain-Specific Models
Luca Simoncini PDCC, Pisa and University of Pisa, Pisa, Italy
Presentation transcript:

João Batista Camargo Jr Safety Analysis Group (GAS) Computer and Digital Systems Engineering Department (PCS) Escola Politécnica da Universidade de São Paulo (Poli-USP) São Paulo, Brazil “Challenges in Safety Certification of ATC in view of New Technologies” Fórum de TI para ATM/CDM 18/11/2014 XIII SITRAER

theory experience new technologies…new hazards?......

Safety Certification Safety: high-level emergent property of the whole system, not of it’s isolated parts (sw, hw, operational procedures, etc…) Safety analysis process: should identify the contributions of their several elements in ATC Complex interdependencies among a large and growing number of elements in ATC.

System Complexity: composed of interconnected parts that as a whole present one or more properties (behavior among the possible properties) not obvious from the properties of the individual parts. What we understand as “System Complexity”? …differs from complicated… Complexity raises from the interaction between two or more components of a system. Such interactions lead to a system behavior that is difficult to determine analyzing its components in isolation. The cause-effect relationship of problems are not evident.

Traditional methods for safety analysis (FTA, FMEA, FMECA,…) are based on functional hierarchical decomposition. The interaction among components can lead to emergent misbehaviors which are a concern in complex systems. Coupled systems are prone to failure propagation. Interactivity and coupling are growing in modern systems. Complexity x Safety – Challenges

Simulation may imply simplification in modeling removing the complexity that should be observed. Timing…must be considered… To model a complex system, we have to impose constrains. But these constrains may lower the capability of Dependability Verification. Complexity x Modeling and Simulation

…..more challenges…. Specification of evidence content: what information is necessary to be provided as evidence in a given domain and for a particular set of applicable standards. Construction of safety cases: providing methodological guidance for safety case construction and ways to decompose the arguments and the evidence in a way that permits more precise and effective demonstration of compliance.

Capturing the degree of credibility or relevance of the evidence: different evidence items could have different levels of credibility depending on their source, or different degrees of contribution towards the satisfaction of different compliance requirements. One needs to be able to assign weights to the evidence items or to the links between the evidence items and the safety arguments. Examples: Problems that directly affect the system safety… Problems that affect the safety integrity level… Better development processes and better evidence about process compliance: better development processes for safety-critical systems which make it not so difficult to rigorously verify that the development process followed is in compliance with safety standards.

Certification of systems made up of components and subsystems: challenges related to construction, structuring and assessment of evidence for systems that reuse existing components and subsystems (e.g. COTS software, sw compilers, sw languages, etc…). Safety certification of isolated parts does not guarantee the system (set of parts) safety. Demonstration of compliance for novel technologies: provision of evidence for and certification of systems that make use of technologies that are novel for safety-critical systems.(adaptive systems, FPGA, Matlab/Simulink)

Ambiguities in safety standards: multiple interpretations of the evidence requirements in the standards as a source of certification issues. Need for providing objective argumentation: how evidence fulfills the safety requirements by argumentation?

……some of our researches…. A practical analytical approach with the goal of increasing the confidence in software safety arguments through the elaboration and assessment of counter- evidence that emerge from software failure modes due to robustness issues and not due to functional hierarchical decomposition.

...it is not possible to mathematically prove safety,...we must verify robstuness for safety...in all levels...(since conception, requirements..... until implementation)...The Safety Critical Systems must be developed and certified to be more Robust with focus on Safety..

Thank You for your attention!! João Batista Camargo Junior Phone: Fax: Safety Analysis Group (GAS) Computer and Digital Systems Engineering Department (PCS) Escola Politécnica da Universidade de São Paulo (Poli-USP) São Paulo, Brazil