Industrial Avionics Working Group 18/04/07 Modular Certification Basic Concepts.

Slides:



Advertisements
Similar presentations
Module N° 4 – ICAO SSP framework
Advertisements

Whole Airspace Safety Case Meeting – Overview of Prior Work – 1 Whole Airspace Safety Case Meeting Overview of Prior Work Tim Kelly John McDermid Department.
Software Engineering Key design concepts Design heuristics Design practices.
Package Diagrams A package diagram is a UML diagram composed only of packages and the dependencies between them. A package is a UML construct that enables.
Solutions to Review Questions. 4.1 Define object, class and instance. The UML Glossary gives these definitions: Object: an instance of a class. Class:
Industrial Avionics Working Group 18/04/07 Propose Safety Case Architecture.
1 CS 426 Senior Projects Chapter 19: Interfaces and Components [Arlow & Neustadt 2005] February 28, 2008.
Industrial Avionics Working Group 19/04/07 Modular Certification Developing Safety Case Modules.
Software Engineering 1 Provisional Revision Plan.
Industrial Avionics Working Group 19/04/07 The Relationship Between the Design and Safety Domains in IAWG Modular Certification What are DGRs and How are.
Industrial Avionics Working Group 18/04/07 Assessing the Safety Case Architecture Optimising the Design Architecture and Safety Case Architecture.
Industrial Avionics Working Group 13/09/06 Incremental Certification Phil Williams – General Dynamics (UK) Ltd Representing the Industrial Avionics Working.
Industrial Avionics Working Group 18/04/07 Application Integration.
Industrial Avionics Working Group 19/04/07 Architecture Integration.
Industrial Avionics Working Group 18/04/07 Modular Certification Safety Case Contracts.
Façade Design Pattern Source: Design Patterns – Elements of Reusable Object- Oriented Software; Gamma, et. al.
Industrial Avionics Working Group 19/04/07 Block, OSL and MSL Safety Argument Modules.
Industrial Avionics Working Group 18/04/07 Defining the Safety Case Architecture IAWG Modular Certification.
The Design Discipline.
Expert System Presentation On…. Software Certification for Industry - Verification and Validation Issues in Expert Systems By Anca I. Vermesan Presented.
Systems Analysis and Design in a Changing World, Fifth Edition
GRASP Principles. How to Design Objects The hard step: moving from analysis to design How to do it? –Design principles (Larman: “patterns”) – an attempt.
CPSC 872 John D. McGregor Session 16 Design operators.
The Architecture Business Cycle. Software Architecture Definition The software architecture of a program or computing system is the structure or structures.
Ceg860 (Prasad)L6MR1 Modularity Extendibility Reusability.
Copyright © 2015 Pearson Education, Inc. Chapter 7: Software Engineering.
Systems Analysis and Design in a Changing World, 6th Edition
 2004 by SEC Chapter 4 Software Design. 2  2004 by SEC Chapter 4 Software Design 4.1 Design Fundamentals 4.2 Design Method 4.3 Architecture Design
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
SOFTWARE DESIGN.
SOFTWARE DESIGN Design Concepts Design is a meaningful engineering representation of something that is to be built It can be traced to a customer’s requirements.
Chapter 17 GRASP: Designing Objects with Responsibilities. 1CS6359 Fall 2011 John Cole.
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
December 9, 2001Architectural Design, ECEN Architectural Design Principles & Techniques A Long Road of History.
Architectural Design Yonsei University 2 nd Semester, 2014 Sanghyun Park.
Architectural Design Identifying system components and their interfaces.
Systems Analysis and Design in a Changing World, 3rd Edition
1 Class Diagrams: Advanced Concepts. 2 Overview Class diagrams are the most commonly used diagrams in UML. Class diagrams are the most commonly used diagrams.
CS212: Object Oriented Analysis and Design Lecture 13: Relationship between Classes.
CPSC 372 John D. McGregor Module 3 Session 1 Architecture.
Open Platform for EvolutioNary Certification Of Safety-critical Systems Large-scale integrating project (IP) Nuanced Term-Matching to Assist in Compositional.
CPSC 871 John D. McGregor Module 3 Session 1 Architecture.
Software Design: Principles, Process, and Concepts Getting Started with Design.
Software Design Patterns Curtsy: Fahad Hassan (TxLabs)
Software Engineering and Object-Oriented Design Topics: Solutions Modules Key Programming Issues Development Methods Object-Oriented Principles.
© 2010 John Wiley & Sons Ltd. Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
Chapter 19: Interfaces and Components [Arlow and Neustadt, 2005] University of Nevada, Reno Department of Computer Science & Engineering.
Chapter 7: Software Engineering
Industrial Avionics Working Group 18/04/07 The Relationship Between the Design and Safety Domains in IAWG Modular Certification Part 2: Completeness of.
ANU comp2110 Software Design lecture 10 COMP2110 Software Design in 2004 lecture 10 Software Architecture 2 of 2 design lecture 5 of 6 Goal of this small.
Week 6: Software Design HNDIT Software Engineering Software Design Learning Outcomes  Understand the activities involved in the Design process.
Object- oriented Design Principles
Industrial Avionics Working Group 18/04/07 Design for Safety IAWG Modular Certification.
Basic Characteristics of Object-Oriented Systems
About Us! Rob StockhamBA IEng MIEE General Manager Moore Industries-Europe, Inc MemberIEE Honorary Secretary ISA England Institute of Directors DirectorThe.
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Discussion of Course Syllabus Class will start momentarily. Please Stand By … CS 8532: Advanced.
Design Engineering 1. Analysis  Design 2 Characteristics of good design 3 The design must implement all of the explicit requirements contained in the.
Project Report Format for Final Year Engineering Students.
Chapter 7: Software Engineering
Chapter 1: Software design
CompSci 280 S Introduction to Software Development
Software Engineering Design
Lecture 9- Design Concepts and Principles
Software Design and Architecture
SOFTWARE DESIGN AND ARCHITECTURE
CIS 375 Bruce R. Maxim UM-Dearborn
Lecture 9- Design Concepts and Principles
PPT and video are due no later than February 15, 2019
Presentation transcript:

Industrial Avionics Working Group 18/04/07 Modular Certification Basic Concepts

Industrial Avionics Working Group 18/04/07 Overview Objectives of Incremental Certification Principles Modular GSN Patterns/Templates Product/Process Containment IAWG Modular Software Safety Case Process

Industrial Avionics Working Group 18/04/07 Objectives: Typical Cost Relationships for Certification Cost of re-certification is related to the size and complexity of the system. Cost of re-certification is related to the size and complexity of the change. £ Change Size & Complexity £ CurrentAim for the Future

Industrial Avionics Working Group 18/04/07 Principles of Modular Certification First step towards Incremental Certification is Modular Certification Apply principles of object orientation to Safety Cases: –High cohesion –Low coupling –Information Hiding –Well-defined interfaces

Industrial Avionics Working Group 18/04/07 Modular GSN – Basic Symbols Public Goal ‘Away’ Goal Module Reference

Industrial Avionics Working Group 18/04/07 Modular GSN – Module View/Safety Case Architecture

Industrial Avionics Working Group 18/04/07 MSL OSL Application Layer (AL) RT BP Design ArchitectureSafety Case Architecture

Industrial Avionics Working Group 18/04/07 Patterns/Templates Patterns –Authoring-Time Instantiations Template –Read-Time Instantiations Instantiation Number {Requirement A}{Evidence B} 1Displayed information is redSection 3.2 2Font is Times New RomanSection

Industrial Avionics Working Group 18/04/07 Product/Process DEF STAN issue 2 requires that process to develop system/software is appropriate DEF STAN issue 3 requires that product is demonstrated to be acceptably safe and only uses process argument where needed to support product evidence Parallel study undertaken to DEF STAN issue 3 –Process acceptability only highlighted where product argument relies upon it – public ‘process’ goal –Public process goal could be supported Empirically, per instance of dependence on process argument Generically, as individual public goals within an overall process argument Variance of process with assurance requirements has not yet been considered

Industrial Avionics Working Group 18/04/07 Containment Safety Case equivalent to ‘information hiding’, to manage complexity in safety case architectures It is not always necessary for each safety case module to have visibility of all other safety case modules Where elements of one safety case module are of limited applicability, their scope can be limited through containment Particularly useful for Process arguments which relate only to a single product argument module

Industrial Avionics Working Group 18/04/07 Containment Simplifying the SCA Without Containment

Industrial Avionics Working Group 18/04/07 Containment Simplifying the SCA With Containment

Industrial Avionics Working Group 18/04/07 Methods for Modular Certification Probably many ways to do modular certification IAWG have investigated modular software safety cases Further material refers to experience gained in defining the IAWG Modular Software Safety Case method Start by looking at how to define the Safety Case Architecture