I think the problem you mention has to do with the fact that software does not apply to one specific domain. It is easy to formulate a framework of engineering

I think the problem you mention has to do with the fact that software does not apply to one specific domain. It is easy to formulate a framework of engineering rigor for specific domains but this is not easily generalisable to all domains that software is applied to. But thankfully this is where regulators play an important role. Building codes have an explicit statement of how they want a building to work and fail, if you want to build engineering rigor in your team that does civil engineering software, that would be your starting point. For aviation the air authorities do the same. Afaic the us had outsourced that part of regulation to related enterprises for a while and this came up in the 737max aftermath. This is one of the few cases where the US seriously lags behind the rest of the world in my opinion.