Content deleted Content added
HeyElliott (talk | contribs) Added info to refs, added archives, ce |
GreenC bot (talk | contribs) Reformat 1 archive link. Wayback Medic 2.5 per Category:All articles with dead external links - pass 3 |
||
| (3 intermediate revisions by 3 users not shown) | |||
Line 13:
* 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 "[[nominative]]" types of [[diagram]]s,<ref>{{cite book
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.▼
|chapter=Annex A: Diagrams (normative)
|title=Unified Modeling Language 2.5.1
|series=[[Object Management Group |OMG]] Document Number formal/2017-12-05
|date=December 2017
|publisher=[[Object Management Group]] Standards Development Organization (OMG SDO)
|page=683
|url=https://www.omg.org/spec/UML/2.5.1/PDF
}}
</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 22 ⟶ 32:
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|website=OMG SE DSIG|title=UML for Systems Engineering RFP|url=http://syseng.omg.org/UML_for_SE_RFP.htm|access-date=2006-06-29 |url-status=dead |archive-url=https://web.archive.org/web/20061012011253/http://syseng.omg.org/UML_for_SE_RFP.htm |archive-date= Oct 12, 2006 }}</ref>
In 2003 David Oliver and Sanford Friedenthal of INCOSE requested that [[Cris Kobryn]], who successfully led the UML 1 and UML 2 language design teams, lead their joint effort to respond to the UML for SE RFP.<ref name=":1">{{Cite web |title=SysML Partners: Creators of the SysML |url=https://sysml.org/sysml-partners/index.html |access-date=2023-03-28 |website=SysML.org |language=en |url-status=live |archive-url=https://web.archive.org/web/20221018204237/https://sysml.org/sysml-partners/index.html |archive-date= Oct 18, 2022 }}</ref> As Chair of the SysML Partners, Kobryn coined the language name "SysML" (short for "Systems Modeling Language"), designed the original SysML logo, and organized the SysML Language Design team as an open source specification project.<ref>{{Cite web |title=SysML FAQ: Who created SysML and how did it get its name? |url=https://sysml.org/sysml-faq//sysml-faq/who-created-sysml.html |access-date=2023-03-28 |website=SysML.org |language=en}}{{dead link|date=April 2024}}</ref> Friedenthal served as Deputy Chair, and helped organize the original SysML Partners team.
In January 2005, the SysML Partners published the SysML v0.9 draft specification. Later, in August 2005, Friedenthal and several other original SysML Partners left to establish a competing SysML Submission Team (SST).<ref name=":1" /> The SysML Partners released the SysML v1.0 Alpha specification in November 2005.
=== OMG SysML ===
After a series of competing SysML specification proposals, a SysML Merge Team was proposed to the OMG in April 2006.<ref>[http://www.omg.org/docs/ad/06-03-01.pdf OMG document ad/06-03-01] {{Webarchive|url=https://web.archive.org/web/20081201130201/http://www.omg.org/docs/ad/06-03-01.pdf |date=2008-12-01
The OMG SysML v. 1.0 specification was issued by the OMG as an Available Specification in September 2007.<ref>{{cite web|url=http://www.omg.org/spec/SysML/1.0/PDF|title=OMG Systems Modeling Language (OMG SysML™), V1.0 |date=September 2007 |work=Object Management Group|access-date=2014-12-04}}</ref> The current version of OMG SysML is v1.6, which was issued by the OMG in December 2019.<ref>{{cite web|url = https://www.omg.org/spec/SysML/1.6/|title = About the OMG Systems Modeling Language Specification Version 1.6 |work =Object Management Group|access-date = 2020-01-14}}</ref> In addition, SysML was published by the [[International Organization for Standardization]] (ISO) in 2017 as a full [[International standard|International Standard]] (IS), ISO/IEC 19514:2017 (Information technology -- Object management group systems modeling language).<ref>{{Cite web|url=https://www.iso.org/standard/65231.html|title=ISO/IEC 19514:2017 - Information technology -- Object management group systems modeling language (OMG SysML)|website=ISO |language=en|access-date=2017-12-29}}</ref>
Line 47 ⟶ 57:
== Tools ==
There are several modeling tool vendors
=== Model exchange ===
| |||