Illustration of the Information Model for Complex System Modeling: from Requirement to V&V Illustration of the Information Model for Complex System Modeling:

Slides:



Advertisements
Similar presentations
Integration of MBSE and Virtual Engineering for Detailed Design
Advertisements

Piedmont Region - Italy Supporting Equal DPs – The Experience of the Piedmont Region Erica Giordano.
1 centre dÉtudes de la navigation aérienne COMMON METRICS FRAMEWORK FOR ATM PERFORMANCE ASSESSMENT AND MONITORING Almira Williams, CSSI Inc.
Early Effort Estimation of Business Data-processing Enhancements CS 689 November 30, 2000 By Kurt Detamore.
Overview of Advanced Design White Paper Farrokh Najmabadi Virtual Laboratory for Technology Meeting June 23, 1998 OFES Headquarters, Germantown.
Strategic Directions in Real- Time & Embedded Systems Aatash Patel 18 th September, 2001.
Department of Computer Science & Engineering College of Engineering Dr. Betty H.C. Cheng, Laura A. Campbell, Sascha Konrad The demand for distributed real-time.
ESA PetriNet: Petri Net Tool for Reliability Analysis Romaric Guillerm, Nabil Sadou, Hamid Demmou 14 Oct LAAS-CNRS.
Complex Adaptive Systems (CAS) Mirsad Hadzikadic.
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
A Combat Support Agency Defense Information Systems Agency Model Based Systems Engineering and Systems Modeling Language Chris Gedo Chief, Architecture.
Engineering Systems of.
Introduction to Systems Engineering Abd-El-Kader SAHRAOUI Industrial Dept Toulouse University: and Laboratoire d‘Analyse.
SysML: A Modeling Language for Systems of Systems
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR ESM'2009, October 26-28, 2009, Holiday Inn Leicester, Leicester, United Kingdom.
Codex Guidelines for the Application of HACCP
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1 August 15th, 2012 BP & IA Team.
Model Based Systems Engineering (MBSE) using SysML GSFC Systems Engineering Seminar June 8, 2010 Sanford Friedenthal Lockheed Martin
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
1 CASE STUDIES IN PROJECT MANAGEMENT Lecture 3 Project management methodologies.
Systems Modeling Language ™ Overview Cris Kobryn and Sandy Friedenthal SysML Partners ( October 2003.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
Effective Requirements Management – an overview Kristian Persson Field Product Manager, Telelogic Asia/Pacific.
Software Architecture CS3300 Fall Beware the Fuzzy Front End We are already almost 1/3 of the way done Need to negotiate deliverable schedule: SDP.
Verification and Validation in the Context of Domain-Specific Modelling Janne Merilinna.
The Sixth NASA Langley Formal Methods Workshop (LFM 2008) 1/15.
IntelliDrive SM Vehicle Safety Communications Working Toward V2V Deployment John Harding July 20, 2010.
SysML Reference Model Definition Model Based System Development in the Joint Strike Missile project Svein-Erik Søgård KDS/Missile Division.
Lecture-3.
SysML Awareness John Davies BSc, PhD, CEng, FIET.
Requirement Engineering for Trust Management : Model, Methodology Reasoning P. Giorgini, F. Massacci, J. Mylopoulos, N. Zannone, “Requirements Engineering.
Development of Methodologies for Independent Verification and Validation of Neural Networks NAG OSMA-F001-UNCLASS Methods and Procedures.
A common meta-model for the interoperation of tools with heterogeneous data models ECMFA 2010 Third Workshop on Model-Driven Tool & Process Integration.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
OSLC PLM Reference model April Summary of the OSLC PLM Reference Model V0.4 April 4th 2011 Gray Bachelor Mike Loeffler OSLC PLM Workgroup.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
20CC Ltd Independent Consultants © 20CC Ltd Systems Thinking Overview Sources from The Open University acknowledged.
The FDES revision process: progress so far, state of the art, the way forward United Nations Statistics Division.
Lamsade – Université Paris IX Dauphine Indexes socially "understandable" 4th December 2008.
Lectures 2 & 3: Software Process Models Neelam Gupta.
INCOSE IW12 MBSE Workshop 15 INCOSE (MBSE) Model Based System Engineering Integration and Verification Scenario Ron Williamson, PhD Raytheon
Toward a New ATM Software Safety Assessment Methodology dott. Francesca Matarese.
A fault tree – Based Bayesian network construction for the failure rate assessment of a complex system 46th ESReDA Seminar May 29-30, 2014, Politecnico.
Standards Development for Climate Change  Consensus reached between UNFCCC & ISO that internationally accepted standards will be promoted globally  Include.
An Integrated Model-Based Approach to System Safety and Aircraft System Architecture Development Eric Villhauer – Systems Engineer Brian Jenkins – System.
Status of SysML v2 Planning & Requirements Berlin, Germany June 16, roadmap:sysml_assessment_and_roadmap_working_group.
Model-based design inspection based on traceability information models and design slicing Shiva Nejati April 15, 2015.
Verification Matrix Process
Systems Engineering Concept Model (SECM) Update
AVIATION SYSTEM BLOCK UPGRADES (ASBU)
AFIS MBSE Working Groups
SysML v2 Usability Working Session
System Engineering Concept Model – Domain 8/5/2015 Status
Systems Engineering Workflow Use Cases Activity SysML Roadmap Activity
Engineering Processes
© 2018 Lockheed Martin Corporation
Societal resilience analysis
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Engineering Processes
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Nicholas J. Di Liberto 20 June 2011
Systems Engineering Workflow Use Cases Activity SysML Roadmap Activity
Status of SysML v2 Planning & Requirements
Review and comparison of the modeling approaches and risk analysis methods for complex ship system. Author: Sunil Basnet.
Presentation transcript:

Illustration of the Information Model for Complex System Modeling: from Requirement to V&V Illustration of the Information Model for Complex System Modeling: from Requirement to V&V Romaric Guillerm 1, 2, Hamid Demmou 1, 2, Nabil Sadou 3 1 CNRS, LAAS, 7 avenue du colonel Roche, F Toulouse, France 2 Université de Toulouse, UPS, INSA, LAAS, F-31400, Toulouse, France 3 SUPELEC / IETR, avenue de la Boulais, F-35511, Cesson-Sevigne, France 3rd Edition of the International Conference on Complex Systems Design & Management (CSDM 12) December, 2012 – Paris, France We have defined an information model to assist the design of complex systems in a context of Model Based System Engineering (MBSE). This poster illustrates the utilization of this information model through a case study.  System Engineering (SE) as framework for the design of complex system.  EIA-632 standard to guide the SE approach.  Information model to address requirements definition and their traceability towards the solution and the Verification and Validation (V&V) elements.  The work considers especially an important system property which is safety.  SysML language is used to establish the information model thanks to the different available diagrams, which make SysML as the language for systems engineering. Context The information model that we propose is adapted to the EIA-632 standard and makes a clear distinction between different requirements types. The case study illustrates the interest of the SysML information model on a complex example. It consists on an S18 aircraft that the specifications are provided by the standard ARP Materials and Methods Illustration The involved subsystems for the decelerate function are:  the thrust inverser system (or reverse),  the spoiler system,  and the wheel brake system. 2. Requirements The Top-level requirements diagram presents the requirements at system level. It connects those requirements to the risks they deal with the “treat” link. References Conclusion 3. V&V  Different concepts are handled in complex system design: requirements, design solution and V&V.  An information model aims to help engineers in the expression of these concepts, and the creation of traceability links between them in order to facilitate the comprehension and/or the impacts analysis. It also helps to formalize the practice of systems engineering through the use of models.  The objective is to improve quality/productivity and to reduce risks by introducing rigor, precision, and communications among stakeholders and managing complexity. 1.Guillerm R., Demmou H. and Sadou N., Safety evaluation and management of complex systems: A system engineering approach, Concurrent Engineering: Research and Application, vol.20 pp , June Martin J. N., Overview of the EIA-632 Standard: Processes for Engineering a System, Digital Avionics Systems Conference, 31 Oct-7 Nov Friedenthal S., Moore A., and Steiner R., A Practical Guide to SysML: The Systems Modeling Language, 576 The MK/OMG Press Series ARP-4761: Guidelines and methods for conducting the safety assessment process on civil airborne systems and equipment, Society of Automotive Engineers (SAE) standard, December The study is limited to the “Decelerate aircraft on the ground” function. 1. Design Solution Blocks Diagram: Equipment Breakdown Structure. The Requirement declinations diagram shows the declination of the system requirements into subsystem requirements through the “composition” link. The Requirement verification diagram denotes elements of V&V which satisfy the requirements with the “verify” link. Requirements Diagram: Requirement Declinations. Requirements Diagram: Requirement Verification. The Requirement satisfaction diagram indicates the system elements (system or subsytems) that meet the requirements with the “satisfy” link. Blocks Diagram: Test Cases. The Test cases diagram presents the defined V&V elements to verify the requirements. Requirements Diagram: Requirement Verification. (extract) Requirements Diagram: Top-Level Requirements. (Extract)  The complexity of modern systems makes system engineering processes critical.  Requirement engineering processes are important in system design.  The emergence of critical proprieties like safety needs a global approach.  MBSE allows to requirements definition and their traceability towards the solution elements and the V&V (Verification and Validation) elements. Information Model