9 Laws of Systems Engineering

During my last session of YouTube foraging ( oh, you don’t want to see my view history … ) I stumbled upon this gem. Thought it’s a really good webinar, spot-on and directly to the core. I’d say it’s short, even though you wouldn’t say just based on video length. It addresses the basics very briefly and clearly enough, so I’d share with you all. It might come useful to explain that everlasting question on what is Systems Engineering and what is it you’re doing. Then the blank stare and quick subject change when you’re trying to explain....

read more

3D UML Modelling?

Developed on top of Google SketchUp? That’s interesting. I thought it dead since Google sold it to Trimble and it went silent for the least to say, as it got to be a paid tool now. This has been tweeted today, even though the news is from 2009: UML in 3D – #oldiebutgoldie http://t.co/EqgSNudYCA — Jordi Cabot (@softmodeling) September 6, 2014 Would be interested in further development of the concept, in a more professional look & feel for using in practice, provided it was shown effective. Would be interested in seeing some further development of the concept, in a more...

read more

What’s a System Engineer

There is still an active discussion of what System Engineering and the system engineer is all about. I found a very interesting post on the matter here. The historical roots have created some of the differences in these definitions of “systems engineering.” For example, the INCOSE definition comes from its roots in electrical engineering and its early application in places like Bell Labs, the defense industry, and space programs.[1] All systems engineering definitions and all industrial engineering programs share a focus on a set of methods and techniques, although the particular methods and...

read more

About Requirements and Design

Let us be clear from the start what requirements mean. Are they the description of the system to be? At first glance yes, even though that is only half of the truth: they are the description of what the system should be doing, and what is the fashion it should behave or look like. But they are not the description of how that behavior is accomplished. If you are looking at the implementation of a required (in other words requested, desired) behavior, you are looking at design. Because that’s what requirements are all about: the what. Requirements specify WHAT a system (entity) should be...

read more