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

Learn how model-based systems engineering (MBSE) can help you cut through the chaos of early systems development and get you from definition to execution more seamlessly.
You’ll hear the transitional phase described in some detail to help you understand what drives the chaos and confusion. You’ll also see how MBSE can make reusing functions and components easier, how to perform interface and constraint verification, and how the model itself can become the implementation through code generation.
See all the videos in this playlist: • Systems Engineering
Check out these other references:
- System Composer (MathWorks): bit.ly/36jKd7q
--------------------------------------------------------------------------------------------------------
Get a free product trial: goo.gl/ZHFb5u
Learn more about MATLAB: goo.gl/8QV7ZZ
Learn more about Simulink: goo.gl/nqnbLe
See what's new in MATLAB and Simulink: goo.gl/pgGtod
© 2020 The MathWorks, Inc. MATLAB and Simulink are registered trademarks of The MathWorks, Inc.
See www.mathworks.com/trademarks for a list of additional trademarks. Other product or brand names may be trademarks or registered trademarks of their respective holders.

[@larcomj]

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.

[@enes_aero]

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 ❤

[@elexawi]

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

[@ace_sunzhe]

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

[@prashkd7684]

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.

[@VichoBandido]

Loved this series.

[@Luke..luke..luke..]

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

[@BrianBDouglas]

Awesome to hear! Thanks for the comment ♥

[@mnada72]

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

[@gengistr4566]

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]

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

[@jangAckman]

Best tutorial ever! thank you so much!

[@alimousavi3230]

"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]

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.

[@DDDelgado]

Completed the playlist, Thanks.

[@BrianBDouglas]

💯

[@erikdornbush4099]

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]

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]

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.

[@mjc6405]

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

[@18_Bruce]

MATLAB/Simulink

[@user-eh4ib6gb9l]

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

[@j.decastro4742]

What software are you using?

[@j.decastro4742]

What software is this? the modeling tool

[@rahulbirari401]

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

[@srij16]

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

[@BrianBDouglas]

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

[@srij16]

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

[@levili5734]

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!