#ocsmp

[mysticmagics]

Guess who spent 7 and a half hours searching and fishing for a singular lily pad for a secret santa gift because I decided to do a really bad play on words and a mod let me do it

[tonextraining]

OMG OCSMP certification, Combo Hands On MBSE SysML

[mint-teabag]

Yes. Another world. Another story. I wish I can create some comics with this one someday... (p.s. blue one is Indigo, black and white is Noah, and white hair is Cloud)

[delligattiassociates]

The Truth about Model-Based Systems Engineering (MBSE)

It’s not a silver bullet.

It’s not an Easy button.

It takes time to learn.

There’s an upfront cost to building a model (rather than just a set of Visio diagrams).

 So why learn MBSE? Two reasons:

 •  Automated consistency among work products when change occurs

•  Rapid, definitive answers to stakeholders' questions

 These are the benefits of adopting and practicing MBSE. And these benefits enable engineering organizations to achieve a key goal: Improved affordability and product quality.

 If your team is currently practicing the traditional, document-based approach to engineering, then you’ve experienced the burden and cost of manually maintaining a disjoint set of work products (i.e., documents, spreadsheets, diagrams, reports, and presentations). MBSE does not eliminate the need for a disciplined engineering process, but it does mitigate the cognitive burden on you—the designer—when requirements change and new design decisions are made.

 Please reply to this post to share your experiences with MBSE—the good and the bad. If you’re considering MBSE adoption, I’ll be presenting some data on the ROI that MBSE offers in a live webinar on Thursday, March 12, 2015.  Please join me:

 https://ei194.infusionsoft.com/app/page/mbse-with-sysml-webinar-registration-12-mar