Embedded SW Development
Hi Bruce, Full disclosure, I am a systems engineer and like the top-down approach to developing systems. Therefore I am intrigued by MBSE using whatever methodology. As you know, I started studying the Harmony/SE process and have also studied the Harmony/ESW process. I thought it would be simple to connect the system world with the software world via SysML/UML models in Rhapsody. However I have seen a pattern with my fellow "embedded software developers". They really don't like Rhapsody and they really don't like UML modeling tools. They think they are clunky, bug-ridden, old and nasty. Many quit their jobs just to avoid it. Software modeling seems to have a bad rep, why is that? They seem to prefer to document their software requirements and software architecture in tools like JIRA and Confluence or using any combination of office tools drawing UML like pictures, but I know that maintaining consistency an traceability using those concepts will be lost. Why don't they want to do proper UML modeling in a tool like Rhapsody? Is it because they are fostered in an "Agile" environment that detests "documentation"? Why is this a struggle? What can be done about it?