For a few weeks there was a survey on SE-Trends: What problem does SysML solve for you? 89 readers took part in the survey, and I will share the results below.<\/p>\n\n\n\n
By the way, another survey on the topic of traceability is currently underway (in the sidebar of SE Trends). Again, I will analyze and publish the results in a few weeks.<\/p>\n\n\n\n\n\n\n\n
Without further ado, here are the raw survey results:<\/p>\n\n\n\n\n\n
More than half of all participants identified mastering the system architecture (30%) and improving communication (26%) as the areas for improvement. <\/p>\n\n\n\n
It is not surprising that architecture is an important topic: after all, as systems become more complex, architecture becomes increasingly important. After all good architecture<\/a> for scalability, maintainability and facilitates the handling of changes and variants. The visual representation in SysML is also ideal for us humans. The nesting that is possible with SysML blocks also makes it easy to break down to any number of levels for different sized (or small) systems. The alternative is \"painted\" diagrams. This may still be sufficient for very small systems, but for modern complex systems, a SysML-based architecture creates enormous added value.<\/p>\n\n\n\n With regard to communication, I would be very interested in readers' opinions (feel free to discuss in the comments): After all, the possibility of using SysML for communication is very diverse. It can form the basis of communication for architects. However, diagrams can also be used selectively, without the model character being perceived to any great extent. The ability to generate documents can also offer added value for certain stakeholder groups.<\/p>\n\n\n\n Three topics received 10-16% of votes - significant minorities. These included:<\/p>\n\n\n\n All three topics have one thing in common: they use the traceability available in SysML to make the connections and interrelationships visible and utilize them. Risks are recognized earlier if, for example, incompatibilities immediately become visible when an interface is changed. This also applies to the avoidance of integration problems. Dealing with changes is made easier by the Black box\/glass box thinking<\/a> simplified.<\/p>\n\n\n\n Only 2 people (2%) saw SysML as relevant for project management. There were also a few free text entries, for example regarding the use of SysML as a DSL. However, no further topic clusters emerged.<\/p>\n\n\n\n And one person saw no added value in the use of SysML.<\/p>\n\n\n\n The results of this survey were not really surprising. However, I see a big difference in the way modern SysML tools support these activities. In my opinion, the development of the architecture is excellently supported by the large SysML tools such as Enterprise Architect, Cameo or Rhapsody.<\/p>\n\n\n\n In the area of communication, on the other hand, we see major weaknesses in traditional tools. Modern web-based tools such as Innoslate<\/a> or SmartFacts<\/a> to gain a foothold. I would be delighted to see even more movement in the market here.<\/p>\n\n\n\n Photo by Lukas Blazek<\/a> on Unsplash<\/a><\/p>","protected":false},"excerpt":{"rendered":" For a few weeks there was a survey on SE-Trends: What problem does SysML solve for you? 89 readers took part in the survey, and I will share the results below. By the way, there is currently another survey on the topic of traceability (in the sidebar of SE-Trends). Again, I will share the results in a few weeks...<\/p>","protected":false},"author":1,"featured_media":3114,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[4,138],"tags":[107,166,58,139],"class_list":["post-3106","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-forschung","category-omg","tag-architektur","tag-kommunikation","tag-sysml","tag-umfrage"],"_links":{"self":[{"href":"https:\/\/www.se-trends.de\/en\/wp-json\/wp\/v2\/posts\/3106","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.se-trends.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.se-trends.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.se-trends.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.se-trends.de\/en\/wp-json\/wp\/v2\/comments?post=3106"}],"version-history":[{"count":0,"href":"https:\/\/www.se-trends.de\/en\/wp-json\/wp\/v2\/posts\/3106\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.se-trends.de\/en\/wp-json\/wp\/v2\/media\/3114"}],"wp:attachment":[{"href":"https:\/\/www.se-trends.de\/en\/wp-json\/wp\/v2\/media?parent=3106"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.se-trends.de\/en\/wp-json\/wp\/v2\/categories?post=3106"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.se-trends.de\/en\/wp-json\/wp\/v2\/tags?post=3106"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Further topics: Development risks, integration, changes<\/h2>\n\n\n\n
Furthermore...<\/h2>\n\n\n\n
Conclusion<\/h2>\n\n\n\n