Unified Modeling Language, UML, and OMG SysML are trademarks of the Object Management Group. All other product and service names mentioned are the trademarks of their respective companies.
Back to Top
A: Although the politically correct response to this question might be that "the answer depends upon whether you are a Systems Engineer or a Software Engineer ...", this response is simplistic and fails to address the growing interest in SysML as an alternative to UML for Real Time Embedded and other software-intensive applications. Consider the recent discussion thread on the SysML Forum discussion group regarding translating a SysML model to Java: http://groups.google.com/group/sysmlforum/browse_thread/thread/17d07673b4f33424>)
Why is SysML an attractive alternative to UML? Consider that SysML is substantially smaller than UML 2.x, so it is easier to learn and apply, yet it is more semantically expressive than UML 2.x, so you can specify visual Requirements and Parametric Constraints as well as Analysis and Design artifacts. Stated otherwise, SysML is more agile and more semantically powerful, while UML is plodding and less semantically powerful. So it shouldn't be surprising that many software engineers and developers are looking at SysML as a "better UML."
Q: SysML vs. UML: Which modeling language is better?
A: Although the politically correct response to this question might be that "the answer depends upon whether you are a Systems Engineer or a Software Engineer ...", this response is simplistic and fails to address the growing interest in SysML as an alternative to UML for Real Time Embedded and other software-intensive applications. Consider the recent discussion thread on the SysML Forum discussion group regarding translating a SysML model to Java: http://groups.google.com/group/sysmlforum/browse_thread/thread/17d07673b4f33424>)
Why is SysML an attractive alternative to UML? Consider that SysML is substantially smaller than UML 2.x, so it is easier to learn and apply, yet it is more semantically expressive than UML 2.x, so you can specify visual Requirements and Parametric Constraints as well as Analysis and Design artifacts. Stated otherwise, SysML is more agile and more semantically powerful, while UML is plodding and less semantically powerful. So it shouldn't be surprising that many software engineers and developers are looking at SysML as a "better UML."
Keep in mind that you can request additional questions to be answered in the SysML FAQ by sending email to FAQ@SysMLforum.com.
Back to Top
Back to Top