Blog

January 9, 2018

The V-model has long provided a metaphor for the classic systems engineering (SE) process, but it is problematic in the Model-Based Engineering (MBE) context: Figure 1 The Systems Engineering V-model It does not reflect much of the work systems engineers actually do. Of the six generic use cases we described in Part 1 of this

January 4, 2018

Most MBSE methodologies place emphasis on organizing the model correctly before actually modeling the system, but this task should not be approached too narrowly.  First, as we discussed in a previous blog, modeling should encompass both the system under development and the project structure, which includes both process and organization. Model organization should facilitate collaboration

December 19, 2017

Introduction Axe in hand, I strode into the misty forest, looking for the perfect Christmas tree. As the slushy snow soaked into my shoes, I thought, “I should have modeled this first!” In any project as critical as decorating the house for Christmas, Model-Based Systems Engineering has a lot to offer the serious practitioner. In

October 17, 2017

Introduction In the first four parts of this series, we have focused on the SysML modeling part of the systems engineering effort. While general-purpose modeling serves many purposes, some parts of design and analysis are best done with more specialized tools. The ability to keep multiple models consistent is the objective of Model-Based Engineering (MBE)

September 29, 2017

Introduction SysML models readily connect structure, behaviors, requirements, and analysis in a single model. We started to show behaviors back in Part 1 with a series of simple state machine behaviors. In this blog post, we show how SysML interaction elements and sequence diagrams can be used to model the message-based communication between different parts