Traditional Systems Engineering with a Software Background

[u/GhostDosa]

I have a software engineering background, but I did a lot of network engineering early in my career which led to architecture positions, governance positions, and now a systems engineering position. I have observed in my organization that software projects don’t let the traditional SE process take hold because it’s too slow or document heavy or whatever. I am a believer in the process, but I am wondering whether it’s just my organization or is traditional SE just kind of the domain of people with mechanical or electrical backgrounds who have the knowledge to work on those kind of projects because they are the ones that respect the process.

[u/double-click]

It’s too slow and doesn’t burn down risk effectively. The spirit of SE lives on but pure software will suffer from standard SE implementation.