MBSE Success Stories

[Patrick Hagerty]

Greetings all!

I'm trying to sell my employer on the idea of moving over to a model-based systems engineering methodology from our traditionally document-centric processes of old.  I think one of the most influential arguments I could present would include examples of other organizations that have successfully, and profitably, made that transition.

That is, in part, why I purchased Enterprise Architect.  I want to develop SysML diagrams as a way of demonstrating the value of model-based views to the engineering team and managers.  But, I think the success stories will play a crucial part in persuading management.

Does anyone have such a success story to share, or have any ideas about where I might find such information?

Thanks in advance,

~Patrick
[P.S. It occurs to me that this post may be stretching the limits of appropriate posts for this forum.  If I have crossed a boundary, I sincerely apologize.]

[qwerty]

Have you fostered EA's site? Or the Community site?

I once worked for two large transportation company and they successfully introduced EA in some areas. But I have no idea whether they published some success story. At least they are listed amongst those: http://www.sparxsystems.de/referenzen/

q.

[OpenIT Solutions]

Hi,

I believe the community site as some real world models/testimonials etc, see:

http://community.sparxsystems.com/

[KP]

Hi,

I believe the community site as some real world models/testimonials etc, see:

http://community.sparxsystems.com/

Yes, specifically have a look at the case studies page:

http://community.sparxsystems.com/case-studies

[Gary]

Patrick
I have two parts to my job:
1) doing MBSE using SysML
2) making presentaions as to why MBSE is a good idea. What I call winning hearts and minds.
 
The second one is by and far the harder. Everyone wants proof before they will adopt it. Trouble is there are very few documented cases of success stories. Not because there are not any but mainly because people do not gather metrics whilst doing MBSE. Other reasons are  because they are performed by space/military companies and they do not publish what they do. Also success is sometimes because doing MBSE you avoid unplanned spending, it is hard to tell project managers that you will be preventing them spending money on problems that they were not going to spend on because you have avoided them.
System engineers are easier because they are doing the same steps as before but in model based way, with the bonus of less documentation.

The best way I found was costing how much engineering effort it takes to create, manage, track and release a document and then say you will saving that, especially if information is spread across mutiple documents. One change and they all have to updated. One change in a model and done.

Gary

[Dermot]

Rather than arguing your case through specific Case Studies maybe you can present some common benefits of Model Driven Developement from requirements that are traceable to the Class (and code), through to Testpoints defined in the model for testing the code.
There are papers covering these sorts of topics:
http://www.sparxsystems.com/downloads/whitepapers/Requirements_Management_in_Enterprise_Architect.pdf
http://community.sparxsystems.com/white-papers/675-model-driven-development-and-visual-execution-analysis
http://community.sparxsystems.com/whitepapers/systems-engineering/ebook-embedded-systems-development-using-sysml

[J.D. Baker]

In addition to the case studies cited above, there were several relevant presentations at the 2014 session of the INCOSE International Workshop.  The presentations can be found at http://www.omgwiki.org/MBSE/doku.php?id=mbse:incose_mbse_iw_2014.  

The focus of the 2015 IW that just concluded was different so there's not as much to glean from those presentations.  

J.D. Baker
Sparx Systems Ambassador
http://www.linkedin.com/in/jdbaker48
Mobile – 760 315-3636
Skype ID - jdbaker48