thank you for sharing. it really helps. and I'm wondering if the ppt and model are available? thanks again.

robotic surgery for acute chronic pancreatitis.

MBSE models the requirements, structure, performance, and behavior of systems (or SoS). Mission Analysis is about effectiveness and emergent behavior. SysML is temporally and spatially oblivious. While it can be used to conduct engagement-level analysis (i.e. performance of a SoS) it cannot evaluate effectiveness. The relationship between the MT/MET and the scenario is homeopathic, at best. To evaluate effectiveness you need a mission-level simulation. In the mission-level analysis we compare various architectures to identify the most cost-effective system. The system that contributes to the most cost-effective SoS determines the system level requirements. Mission level and system level are co-dependent. Effectiveness is the measure that matters. Performance is what you pay for. Every requirement needs to earn its way into the system.

Using this software for school and it's so frustrating! I feel very validated seeing the presenter struggle as well 😂

After 3 years, only 16 likes including me, the reason is obvious language and tool gangs :) As an SE with more than 35 years of experience, and now working on "real" MBSE, I cannot understand why a huge part of the SE community still talks about drawing diagrams more than the domain knowledge representation issue. My solution: choose a top-level ontology to express a realistic and scientific worldview (my choice is Basic Formal Ontology); select or create a middle-level core ontology to enable cross-domain (SM, PM, engineering, specialty areas, etc.) interoperability; develop a domain (SE) reference ontology for the multi-program, sub-domain application-level interoperability; depending on these create a graph schema (on a graph db); populate your instances. Then, you may map your solution to any framework and tool to generate fancy diagrams to communicate with stakeholders.

MBSE: Yo dawg, I heard you like systems engineering, so I put some systems engineering in your systems engineering.

Good

In the diagram at 18:54, should the arrow between Verification Activity and Event be reversed to go from Activity to Event?

Very informative - wish the diagrams were available for download.

And better title for this might be nine laws of MBSE. Not all SE practitioners have access to MBSE yet

At 14 minutes or so in this presentation - the speaker has developed what I believe to be a VERY sound definition of Modes. I love it.

Promo*SM

Great information!

Will the models (or presentation of them) be shown later?

'Promo sm' 💖

Good stuff! I like your blogs too!

Thanks a lot. Approved from South Africa

This is excellent. Thanks for sharing!

My question to you is… the transitions, how do you create them in CORE????

I had my SYSTEMS ENGINEERING class back in 1985, ever since I see the WORD major MIS-CONCEPTIONS: Transpórtation Industry is broken into alleways of SUB-COMMODITIES. "carmakers" "airplane makers" "roadmakers" "trainmakers" etc. Another major failure of Man -Kind is the ill conceived Money System.

Nice video c:

Thank you for spending the time to create this content! Easy to follow and insightful

So what if the option for creating this diagram doesn't show up on the top toolbar? Even though you selected it in your diagram to display preferences

I want ask you What are the components of FMEA ??

Can you create a model for me on any system....?

how can i get the tool project explorer (gl concept model) ? is that public application ?

WOW!!! YOU GUYS WENT ALL OUT TODAY!!!!

var.fyi brilliant

7mj1q vyn.fyi

ockpf vyn.fyi

xk5yf vyn.fyi

vaw.fyi cool

P

Have you any books for sale?

Awesome presentation, info, perspective, and approach. Very happy to hear you address the topics soundly. Your talk made my Notable file for doubly documenting what I have been quietly working thru in my personal work with Model-Based Systems Engineering (MBSE) in elevating Humanity. MBSE: Fifty-Five Years Salting Humanity: A Fully-Metered, Bottom-Up, and Inside-Out Approach. Thank you. I shall now go and listen again on 1.75 speed. 😆✌️😁 Another mouthful, like the many names for snow... We learn a lot when opening ourselves to first-hand experience. I am grateful.

Always great content!

Is the RPN supposed to calculate automatically in GENESYS or does it have to be manually input?

Very helpful, many thanks!

Is there guidance available on how to define and decompose items to reduce the clutter on higher-level functional and behavioural diagrams (IDEF0 and EFFBDs). Specifically for items from external components as these tend to be well defined and down to their elemental level (from the concept definition and stakeholder meeting phases) prior to the design of the SoI.

can we download the presentation ??

Interfaces are the most challenging and most neglected aspect of System Engineering.

YEP! Lots of cable rework.

Great content as always!

I am new to Systems Engineering (SE), having started working in an SE role only a couple of months ago. Prior to this I was a quality manager, and certification and compliance engineer, and what I am finding most interesting as I'm learning about SE and watching your presentation is how much SE principles complement the quality management principles of ISO 9001:2015. Both are very much about understanding the 'context', the interested parties and their needs and expectations, and risks and opportunities. A really good presentation which is supplementing my reading of the ICOSE SE handbook.

Hi Ron, thanks for this fantastic explanation on FMEA, one of the best part of this video is the relation which Ron has established between model and the output expected from the model during FMEA.I don't know how these useful videos are lost in to the dark data space of KZbin, thanks again and pardon my English.

Great, presentation, thank you for sharing on KZbin!

42:00 true

great video :)

A good explanation. "Predicting system wrongly leads to wrong result(consequences)!!"

A few additional thoughts - What the customer wants is not always what he needs. And what he wants, needs or asks doesn't necessarily match his expectations or lead to satisfaction. These are all different concepts that may not be confused! - Understanding the problem is not the same as identifying the right problem (the right cause; diagnosis). - ‘Analysis’ is often defined as looking inwards into something, looking at the parts and their relationships. Systems can not be designed without understanding of their supra-system and their environment. We need to do an outward ‘analysis’, an analysis of the environment. Analysis as in Systems Analysis has not the same meaning as 'analysis' in the dictionary.