Moving from Documents to Models

Поделиться
HTML-код
  • Опубликовано: 24 фев 2016
  • In this webinar, we will suggest an evolutionary process for adopting MBSE, which allows quick wins and minimizes risks. Furthermore, we will share some important lessons learned in supporting organizations on their journey to adopting MBSE, identify common pitfalls to be avoided, and provide recommendations for solving specific challenges such as establishing modeling framework, educating system engineers on modeling languages, methods, and tools, importing data from documents to models, using models to produce document artifacts for specific stakeholders, managing model quality, integrating modeling tool(s) into the overall chain of engineering tools, using models as organizational knowledge base and promoting collaborative approach to model creation, usage, and governance.
    The session demonstrates
    - Typical engineering practices (V models with documents, regulations, standards)
    - MBSE as promoted by INCOSE
    - MBSE infrastructure: language, approach, and tool
    - Common pitfalls to avoid
    - Evolutionary approach to adopting MBSE
    - Solving specific challenges
    - Recommendations for getting started
    The session is hosted by Dr. Darius Silingas, Senior Solution Architect at No Magic, Inc.
    Discuss with us on the CATIA MBSE Cyber Systems Community: go.3ds.com/cyber.systems
  • НаукаНаука

Комментарии • 11

  • @user-qq1sl3xk9k
    @user-qq1sl3xk9k 4 года назад +2

    Hello. Thank you very much for the free publication of your videos.

  • @diigitalname6582
    @diigitalname6582 Год назад

    Dr. Darius Silingas explains complex things in very simple n practical language - in terms of problem definition (now the knowledge is stored in books or documents - away from physical world) and how it is addressed by embedding the knowledge in digital models and simulating the function/ performance/etc. Very cool!

  • @vedarthamgopal19
    @vedarthamgopal19 4 года назад

    Thank you. Good information.

  • @goalisticfaizi
    @goalisticfaizi Год назад

    Can I please get the full file of the example (coffee machine) used in this tutorial?

  • @CameoMagic
    @CameoMagic Год назад

    good overview

  • @CChoo-tk5ji
    @CChoo-tk5ji 5 лет назад +1

    Although presented more than two years ago, this is still valid.

    • @l3adbullet
      @l3adbullet 3 года назад +5

      Although commented more than two years ago, this is still valid.

    • @conrad237
      @conrad237 Год назад

      @@l3adbullet Although replied to more than two years ago, this is still valid.

  • @glennroberts461
    @glennroberts461 11 месяцев назад

    BTW, yes English is a hard language to learn but many, if not most, of us started learning it when we were born. Learning SysML is like trying to learn Russian or Chinese to do systems engineering. SHOW ME HOW TO USE CAMEO.

  • @glennroberts461
    @glennroberts461 11 месяцев назад

    So 30 years ago we introduced to the concept of "Object Oriented Design" - you're Black Box. Now you are telling us to go include "Functions" - you're White Box. THAT'S WHAT REAL SYSTEMS ENGINEERS HAVE BEEN DOING FOR YEARS AND YEARS.

  • @glennroberts461
    @glennroberts461 11 месяцев назад +1

    I've spent 15 minutes on this BS so far and have not seen a good description of the difference between MBSE and the "old method". On slide 6 you tried to pass off the idea that modeling is done on computers and the old method is done on paper. Bullsh-t. If that's the only difference you are wasting my time. Word, DOORS, Visio, Excel, Computer Based Design, Engineering and Manufacturing have been around for over 40 years. Come on, tell me the real difference. AND THE LANGUAGE USED IT NOT IT!