Systems modeling language: Difference between revisions

Revision as of 19:37, 2 April 2019

Revision as of 17:34, 11 April 2019

Line 12:

* SysML model management constructs support models, views, and viewpoints. These constructs extend UML's capabilities and are architecturally aligned with [[IEEE-Std-1471-2000]] (IEEE Recommended Practice for Architectural Description of Software Intensive Systems).

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=httphttps://www.sysmlforum.com/sysml-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: with 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.

Line 21:

The SysML initiative originated in a January 2001 decision by the [[INCOSE|International Council on Systems Engineering]] (INCOSE) Model Driven Systems Design workgroup to customize the UML for systems engineering applications. Following this decision, INCOSE and the [[Object Management Group]] (OMG), which maintains the UML specification, jointly chartered the OMG Systems Engineering Domain Special Interest Group (SE DSIG) in July 2001. The SE DSIG, with support from INCOSE and the [[ISO 10303|ISO AP 233]] workgroup, developed the requirements for the modeling language, which were subsequently issued by the OMG parting in the ''UML for Systems Engineering Request for Proposal'' (UML for SE RFP; OMG document ad/03-03-41) in March 2003.<ref name="rfp">{{cite web|author=OMG SE DSIG|title=UML for Systems Engineering RFP|url=http://syseng.omg.org/UML_for_SE_RFP.htm|accessdate=2006-06-29}}</ref>

In 2003 [[Cris Kobryn]] and Sanford Friedenthal organized and co-chaired the [[SysML Partners]], an informal association of industry leaders and tool vendors,<ref>{{cite web|url=http://www.sysml.org/partners.htm|title=SysML Partners|accessdate=2006-06-29}}</ref> which initiated an open source specification project to develop the SysML in response to the UML for Systems Engineering RFP.<ref name="sysml faq">{{cite web|author=SysML Forum|title=SysML FAQ|url=http://www.sysmlforum.com/sysml-faq.htm|accessdate=2006-06-29 |archiveurl = https://web.archive.org/web/20060716231947/http://www.sysmlforum.com/sysml-faq.htm <!-- Bot retrieved archive --> |archivedate = 2006-07-16}}</ref> The original technical contributors and co-authors of the SysML 1.0a specification were Laurent Balmelli, Conrad Bock, Rick Steiner, Alan Moore and Roger Burkhart. The SysML Partners distributed their first open source SysML specification drafts in 2004, and submitted SysML 1.0a to the OMG for technology adoption in November 2005.

=== OMG SysML ===