Systems modeling language: Difference between revisions

Revision as of 19:37, 2 April 2019

Revision as of 19:37, 2 April 2019

Line 14:

SysML reuses seven of UML 2's fourteen diagrams, and adds two diagrams (requirement and parametric diagrams) for a total of nine diagram types. SysML also supports allocation tables, a tabular format that can be dynamically derived from SysML allocation relationships. A table which compares SysML and UML 2 diagrams is available in the SysML FAQ.<ref>{{cite web|url=http://www.sysmlforum.com/faq/|title=SysML Forum: SysML FAQ - What is SysML?, Why use SysML?, Who created SysML?|work=sysmlforum.com|accessdate=2014-12-04}}</ref>

Consider modeling an automotive system.: Withwith SysML one can use Requirement diagrams to efficiently capture functional, performance, and interface requirements, whereas with UML one is subject to the limitations of [[use case diagram]]s to define high-level functional requirements. Likewise, with SysML one can use Parametric diagrams to precisely define performance and quantitative constraints like maximum [[acceleration]], minimum [[curb weight]], and total [[air conditioning]] capacity. UML provides no straightforward mechanism to capture this sort of essential performance and quantitative information.

Concerning the rest of the automotive system, enhanced [[activity diagram]]s and [[State diagram#UML state diagram|state machine diagrams]] can be used to specify the [[embedded software]] control logic and information flows for the on-board automotive computers. Other SysML structural and behavioral diagrams can be used to model factories that build the automobiles, as well as the interfaces between the organizations that work in the factories.