1 / 9

AFIS MBSE Working Groups

AFIS MBSE Working Groups. MBSE Initiative Workshop Jacksonville, 2012. Jean-Luc Wippler. Two MBSE tracks. SysML oriented Provide feedback Enhance the “operability” of SysML within organisation “Formal Approach” (or systemic) oriented

bbonnett
Download Presentation

AFIS MBSE Working Groups

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AFIS MBSE Working Groups MBSE Initiative Workshop Jacksonville, 2012 Jean-Luc Wippler

  2. Two MBSE tracks • SysML oriented • Provide feedback • Enhance the “operability” of SysML within organisation • “Formal Approach” (or systemic) oriented • (re)discover and advertise/popularize some “more systemic oriented”, or more formal approaches like System Dynamics of J.Forrester.

  3. Coverage of MBSE “formal approach” oriented (beyond the « strict » understanding) • Models & Technical Processes • Model to solve • « How make my system run? (and know why!) » • Model to decide • « What is the less bad solution ? » • Model to produce (aka MDD or MDE) • « How to make my production repeatable and efficient? » • Models and Agreement Processes • Model to communicate(the goal of architecture frameworks) • « How to crystallise and share a common understanding of various stakeholders? » • Models & Management Process • Configuration management of engineering artefacts • Sharing and Collaborative work (incl. traceability) • Obsolescence management and data perenniality

  4. Engineeri.e. Bring Added Value Assess, MBSE should be a (the?) way to perform SE ! Performing a (SE) Technical Processes can be explained like this: Input Alternatives, conflicts,options, etc OPTIMIZE Choices & impacts VERIFY & VALIDATE DECIDE JUSTIFY V&V facts Output Justifications Adapted from IEEE 1220 Source : “Complex Systems and System of Systems Engineering” Dominique Luzeaux, Jean-René Ruault & Jean-Luc Wippler

  5. Prescriptive Representation Multidisciplinary or domain specific models Decision Model Risk Model Performance Model Cost Model Descriptive Representation Engineeri.e. Bring Added Value Assess, Optimization Model Virtual models, mock-ups, simulations, etc. Thus, useful models are … Input Alternatives, conflicts,options, etc. System of Interest OPTIMISE Choices & impacts VERIFY & VALIDATE DECIDE JUSTIFY V&Vfacts Output Justifications Visible WorldRepresentation Intelligible WorldModel based reasoning Model Based Systems Engineering Source : “Complex Systems and System of Systems Engineering” Dominique Luzeaux, Jean-René Ruault & Jean-Luc Wippler

  6. Need to converge to an optimal solution in term of Performance and Cost MBSE should provide means to explore efficiently the trade space to find where to gain performances wrt affordability (not a means to simply “promote” the supposed solution) Unaffordable Where wewant to be Cost/PerformanceTrade Space Performance UnacceptablePerformance Cost Source : USAF

  7. MBSE “formal approach” foreseen directions (1/2) • Valorisation and dissemination of approaches like: • System Dynamics (J. Forrester) • Multidisciplinary optimisation • MATE (Multi Attribute Tradespace Exploration) • … • Valorisation and dissemination of French R&D work around: • (Formal) Property based engineering • ADL (Architecture Description Languages)

  8. MBSE “formal approach” foreseen directions (2/2) • a minimal, but formal ontology of system (restricted or not ? to architecture) : • graph theory ? (see MIT work about system architecture & design) • (semi)latices (see excellent article of Ch. Alexander “A city is not a tree”) • mereology ? • Formalisation of “ilities” (formal definition of) • formal assessment of “ilities” (modularity, …) • transformations and “operators” (design rules) on models to obtain (enhance) such ilities • Definition of xFFBD : a new step towards eFFBD to provide a yet simple, but formal and complete functional modelling technique of complex systems

  9. Deployment of MBSE:the (real ?) Process model 

More Related