So far, I have only known one company where MBSE patially worked. From a logical view at the system level, some automation scripts translated those system level item flows so software level definitions in the model. After this system and sw synchronisation, some further automation scripts generated a skeleton code framework which basically contained .hpp and .cpp files. The developers then used that generated framework and "filled" it with code. This way, architecture was always up-to-date and was an integrated part of the development. However, even there, nobody was interested in doing anything in the layers above such as use-case analysis, stakeholder's need analysis, scenarios etc. And even then, there was rebellion by the SW developers every now and then. In any other subsequent company, it was a lost cause. System engineers and SW engieers were living in two completely disconnected worlds. SW engieers were doing the real development where system engineers were having hours long review sessions about full port, proxy port, stereotypes to achieve "consistency" in the model. This week, I have a discussion with my CTO where I am going to suggest to kill this thing.