• LinkedIn
  • Subcribe to Our RSS Feed
Mar02

Breaking Systems Engineering (and Three Ways to Bind the Fractures)

by dlong

By David Long, Vitech President

“The biggest errors are made on day one.” Sadly, those involved in systems engineering live this every day, but not necessarily in the manner we think. Though we strive to avoid this pitfall and address it in the systems we develop, the very way we approach our practice is often flawed. We break systems engineering from day one by our flawed practices, many times not even recognizing that we have done so.

In talks and tutorials, I frequently ask how many in the audience are applying a waterfall process. The general response is a hand or two timidly raised with the rest of the audience proudly asserting that they execute a spiral, incremental, or agile process – anything but waterfall. I then ask an individual “If I wanted to know about your requirements, who would I talk to?”  More...

Tags: , , , , , ,

Categories: MBSE | Misc

Feb16

Precision and the False Choice

by dlong

By David Long, Vitech President

Just like simplicity, not all precision is helpful. Heresy? Not for engineers. Engineers are taught to use the appropriate degree of precision for the circumstance at hand. Unfortunately, as systems engineers, we too often forget those lessons. The quest for precision can lead us astray, and some of our processes, methods, and tools actually feed this negative tendency. 

At its very foundation, systems engineering is both systems (the big picture, holistic thinking, and emergence) and engineering (rigor and analytics). It is the second aspect – the need and drive for rigor – that can be a source of trouble. Rigor correctly understood leads to the appropriate level of precision given the current level of knowledge and the task at hand. Rigor misunderstood leads us to prematurely delve into detail design while still working at the systems level, to project precision where analytics don’t support it, to overwork a problem when a higher level statement of feasibility is more appropriate.

Too often, we present ourselves with a false choice. The alternative to precision is framed as “ad hoc” or the absence of rigor. That false choice is used both ways – to engage in analyses that are premature or unwarranted and to avoid all rigor because the time is not right or detail is absent. But the choice is not about precision vs. ad hoc. It’s about accuracy and the right degree of accuracy for the circumstances. More...

Tags: , , , , ,

Categories: MBSE

Jan26

The Need to Suboptimize Systems Engineering

by dlong

By David Long, Vitech President

A good systems engineer working on a project should seek to suboptimize systems engineering. A heretical statement? Not really. In fact, the path to optimizing systems engineering lies in suboptimizing systems engineering. It may sound paradoxical, but it’s true.

The purpose of systems engineering is to deliver the desired business value to the customer efficiently and effectively, free from unintended consequences. Systems engineering does not do this in isolation. It does this in concert with project management and countless domain specialties key to the problem at hand and the solutions under consideration. For systems engineers, it’s easy to become obsessed with our processes, methods, tools, and artifacts. However, the purpose of systems engineering is not the execution of an interdisciplinary process. Nor is it generation of a specification. The purpose of systems engineering is not even delivery of the system of interest. The system we engineer is simply a means to the end – delivering the desired business value.  More...

Tags: , , , ,

Categories: MBSE

how to catch a cheater