Some Benefits of Model-Based Systems Engineering | Systems Engineering, Part 5

Поделиться
HTML-код
  • Опубликовано: 27 авг 2024

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

  • @larcomj
    @larcomj 3 года назад +42

    after 7 years of working in R&D i can say that this is the best description of how a product is developed, sooooooooooo true.

  • @elexawi
    @elexawi Год назад +6

    What a fantastic short Systems Engineering series! Thanks so much, Brian!

  • @abhishekdeshmukh6778
    @abhishekdeshmukh6778 Месяц назад

    Thank you Brian for the amazing system engineering Series

  • @enes_aero
    @enes_aero 5 месяцев назад +1

    Thanks a lot Brian! You’ve helped me a lot in my undergraduate course with your videos on Control Theory and now that i am working as a systems engineer this video serie was super useful. Never stop making these videos ❤

  • @surajr4757
    @surajr4757 Месяц назад

    Thank you Brian for making these series. I'm feeling sad that this playlist has only 5 videos.🥲Hope you make more videos covering the concepts of Systems Engineering.🙂

  • @mnada72
    @mnada72 3 года назад +10

    As I understood from this series, system engineering is the technical version of project management. I hope I understood ✅

    • @gengistr4566
      @gengistr4566 2 года назад +2

      Is more than that, but it is a good first definition. SE is all around the system, while PM is around the project. Of course SE and PM touch each other and share many things, but both are different. SE is the system (to be created and developed) management!

    • @wyh9021
      @wyh9021 Год назад +2

      @@gengistr4566 majority of the times where we are dealing with "complex" systems. the "Projects" are actually "the systems". Right?

  • @Luke..luke..luke..
    @Luke..luke..luke.. 9 месяцев назад +2

    Just stumbled on these videos. I love this breakdown. Thank you. ❤

    • @BrianBDouglas
      @BrianBDouglas 9 месяцев назад

      Awesome to hear! Thanks for the comment ♥

  • @alimousavi3230
    @alimousavi3230 3 года назад +7

    "NASA systems engineering ENGINE processes" are bidirectional ("top-down" and "bottom-up") and also recursive and iterative processes on "the PBS" and "the WBS" throughout the project life cycle...NASA Systems Engineering Handbook...NASA SP 6105 Rev 01 2007.

    • @chrisstites6260
      @chrisstites6260 2 года назад

      NASA with their ridiculous cost over runs and failure to meet or keep deadlines and/or schedules is a horrific example in any form of use. I know first hand as I worked at the Space Center for over 20 years.

  • @prashkd7684
    @prashkd7684 2 года назад +2

    I wish my company will adapt this systems engineering in our business. The systems we work on are so vast and complex that the only people who full understand it are the ones close to their retirement and we, the mere mortals struggle through our careers.

  • @ace_sunzhe
    @ace_sunzhe 3 месяца назад

    thanks for the great video, it is very helpful,key points clearly explained

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

    Loved this series.

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

    Best tutorial ever! thank you so much!

  • @DDDelgado
    @DDDelgado 6 месяцев назад

    Completed the playlist, Thanks.

  • @erikdornbush4099
    @erikdornbush4099 3 года назад +1

    This is a good explanation of modeling the building of a system, but not all problems are resolved by building something.
    Modeling processes via Monte Carlo simulations for instance is an example of where we might model something that might not require the building of anything, at all.

  • @charlie2960
    @charlie2960 3 года назад +6

    Great video, would be interesting to know how this can aid a more agile approach to traditional systems engineering projects. The software development cycles are so fast - can we emulate this in systems engineering? (Linking MBSE with rapid prototyping)

    • @mostlybasic
      @mostlybasic 2 года назад +1

      For most safety and mission critical systems development, AGILE is not suited. Its more suitable and fruitful for less critical and relatively super less complex SW applications. Why?
      Because for two great reasons:
      1) Agility in AGILE can affect the rigor and time required to strictly adhere to the processes defined as per Guidelines and Certification needs.
      2) Functional complexity is not possible to be broken down to such small pieces where AGILE can be valuable and profitable.

  • @user-eh4ib6gb9l
    @user-eh4ib6gb9l Год назад

    so, top-down approach is first-principles thinking?

  • @mjc6405
    @mjc6405 3 года назад +1

    What's the tool used looks ideal for the job and would be handy.

    • @18_Bruce
      @18_Bruce 3 года назад

      MATLAB/Simulink

  • @j.decastro4742
    @j.decastro4742 2 года назад

    What software is this? the modeling tool

  • @j.decastro4742
    @j.decastro4742 2 года назад

    What software are you using?

  • @srij16
    @srij16 2 года назад +2

    why is the SE not wearing Mask but all the others are ;) . Is he a Superman!?

    • @BrianBDouglas
      @BrianBDouglas 2 года назад +5

      I drew the SE person isolated so no need for a mask, the others were in a group ;)

    • @srij16
      @srij16 2 года назад

      @@BrianBDouglas oh i see :) keep up the good work Brian! :) i look forward to your videos :)

  • @rahulbirari401
    @rahulbirari401 3 года назад +2

    Haha.. I liked how everyone is wearing a mask.

  • @levili5734
    @levili5734 3 года назад +1

    Good video. By the way, I have a problem.
    Hello, Matlab technicals. As a MacbookPro user, apple has introduced ARM MacBook this year. Would you introduce Matlab R2021 for ARM mac (M1 chip)? Since I would like to update my old computer. Thanks!