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

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

First Letter to the Customer

The first time is always the toughest in everything. It’s the time of doubt, incertitude and great challenge. It’s the time when you don’t know when all the handles to operate and just how rigid things are. How should you approach this? I was experiencing the first challenge when entering my very first meeting with the customer, meeting where we were supposed to convince the customer to accept one of our alternative solutions. It was a hell of a challenge. Now, my solutions requires explanation. An explicative letter with a graphic illustration, a presentation, that is. So, 2 days were spent...

read more

How to: 10 Sure Ways to Blow Your Requirements!

What do you achieve when you don’t know what you want? Sometimes the best way to perform is not to know what to do, but what not to do. This is best start not only to new comers, but also to experienced Requirement Engineer who takes over a new challenge. Experience and project specificity will of course add and tailor features and work process, but you already have a pretty solid and complete skeleton of your work product: the requirements document. So, here’s a list with some basics you can start with in order to fail: 1. Start working on phone/email basis: don't ask for a...

read more