As individuals and organizations deploy model-based systems engineering, the unwary fall into several traps: starting too big (or too small), chasing standards, focusing purely on the tool (or technical) dimensions, and more. In an earlier blog, I discussed 7 classic errors or anti-patterns to avoid. As we look for positive …

“There is NO SUCH THING as non-model-based engineering” Zane Scott, Vitech Corporation Vice President of Professional Services An interesting quote when you consider systems engineering has spent the last ten years obsessed with the transformation to model-based systems engineering (MBSE). But Zane is exactly right. Engineering has always been, and …

Systems engineering emerged in an era of clean-sheet, top-down, stand-alone design where design began at the system level and proceeded through custom manufactured assemblies and electronics. In today’s age of rapid technology infusion cycles, changing needs, and middle-out or bottom-up design, we strive instead to embrace reuse of existing components …

Influenced by the broad applicability of systems engineering and the fact that it is generally taught top-down, many systems engineers believe that they consistently engage in a variant of clean-sheet design. While systems engineering certainly enables fresh thinking and new looks into a problem space, the reality is that we …