Jump to content

Systems modeling language

From Wikipedia, the free encyclopedia
SysML diagrams collage

The systems modeling language (SysML)[1] is a general-purpose modeling language for systems engineering applications. It supports the specification, analysis, design, verification and validation of a broad range of systems and systems-of-systems.

SysML was originally developed by an open source specification project, and includes an open source license for distribution and use.[2] SysML is defined as an extension of a subset of the Unified Modeling Language (UML) using UML's profile mechanism. The language's extensions were designed to support systems engineering activities.

Contrast with UML

[edit]

SysML offers several systems engineering specific improvements over UML, which has been developed as a software modeling language. These improvements include the following:

  • SysML's diagrams express system engineering concepts better due to the removal of UML's software-centric restrictions and adds two new diagram types, requirement and parametric diagrams. The former can be used for requirements engineering; the latter can be used for performance analysis and quantitative analysis. Consequent to these enhancements, SysML is able to model a wide range of systems, which may include hardware, software, information, processes, personnel, and facilities.
  • SysML is a comparatively small language that is easier to learn and apply.[3] Since SysML removes many of UML's software-centric constructs, the overall language is smaller both in diagram types and total constructs.
  • SysML allocation tables support common kinds of allocations. Whereas UML provides only limited support for tabular notations, SysML furnishes flexible allocation tables that support requirements allocation, functional allocation, and structural allocation. This capability facilitates automated verification and validation (V&V) and gap analysis.
  • 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 diagrams,[4] 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.

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 diagrams 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 diagrams and 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.

History

[edit]

The SysML initiative originated in a January 2001 decision by the 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 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.[5]

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.[6] 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.[7] 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).[6] The SysML Partners released the SysML v1.0 Alpha specification in November 2005.

OMG SysML

[edit]

After a series of competing SysML specification proposals, a SysML Merge Team was proposed to the OMG in April 2006.[8] This proposal was voted upon and adopted by the OMG in July 2006 as OMG SysML, to differentiate it from the original open source specification from which it was derived. Because OMG SysML is derived from open source SysML, it also includes an open source license for distribution and use.

The OMG SysML v. 1.0 specification was issued by the OMG as an Available Specification in September 2007.[9] The current version of OMG SysML is v1.6, which was issued by the OMG in December 2019.[10] In addition, SysML was published by the International Organization for Standardization (ISO) in 2017 as a full International Standard (IS), ISO/IEC 19514:2017 (Information technology -- Object management group systems modeling language).[11]

The OMG has been working on the next generation of SysML and issued a Request for Proposals (RFP) for version 2 on December 8, 2017, following its open standardization process.[12][13] The resulting specification, which will incorporate language enhancements from experience applying the language, will include a UML profile, a metamodel, and a mapping between the profile and metamodel.[12] A second RFP for a SysML v2 Application Programming Interface (API) and Services RFP was issued in June 2018. Its aim is to enhance the interoperability of model-based systems engineering tools.

Diagrams

[edit]

SysML includes 9 types of diagram, some of which are taken from UML.

Tools

[edit]

There are several modeling tool vendors offering SysML support. Lists of tool vendors who support SysML or OMG SysML can be found on the SysML Forum[14] or SysML[15] websites, respectively.

Model exchange

[edit]

As an OMG UML 2.0 profile, SysML models are designed to be exchanged using the XML Metadata Interchange (XMI) standard. In addition, architectural alignment work is underway to support the ISO 10303 (also known as STEP, the Standard for the Exchange of Product model data) AP-233 standard for exchanging and sharing information between systems engineering software applications and tools.

See also

[edit]

References

[edit]
  1. ^ Flexible Views for View-based Model-driven Development By Burger, Erik. KIT Scientific Publishing, Nov 14, 2014. Pg. 250.
  2. ^ "SysML Open Source Project: What is SysML? Who created it?". SysML.org. Retrieved 2023-03-28.
  3. ^ Embedded Systems Security. By David Kleidermacher, Mike Kleidermacher. Elsevier, 2012. Pg 180.
  4. ^ "Annex A: Diagrams (normative)". Unified Modeling Language 2.5.1. OMG Document Number formal/2017-12-05. Object Management Group Standards Development Organization (OMG SDO). December 2017. p. 683.
  5. ^ "UML for Systems Engineering RFP". OMG SE DSIG. Archived from the original on Oct 12, 2006. Retrieved 2006-06-29.
  6. ^ a b "SysML Partners: Creators of the SysML". SysML.org. Archived from the original on Oct 18, 2022. Retrieved 2023-03-28.
  7. ^ "SysML FAQ: Who created SysML and how did it get its name?". SysML.org. Retrieved 2023-03-28.[dead link]
  8. ^ OMG document ad/06-03-01 Archived 2008-12-01 at the Wayback Machine[dead link]
  9. ^ "OMG Systems Modeling Language (OMG SysML™), V1.0". Object Management Group. September 2007. Retrieved 2014-12-04.
  10. ^ "About the OMG Systems Modeling Language Specification Version 1.6". Object Management Group. Retrieved 2020-01-14.
  11. ^ "ISO/IEC 19514:2017 - Information technology -- Object management group systems modeling language (OMG SysML)". ISO. Retrieved 2017-12-29.
  12. ^ a b "sysml-roadmap:sysml_v2_requirements_review_page [OMG SysML Portal]". OMG Wiki. Retrieved 2017-12-29.
  13. ^ "OMG Process Introduction". Object Management Group. Retrieved 2017-12-29.
  14. ^ "Commercial, Free & Open Source SysML Tools for MBSE". sysmlforum.com. Retrieved 2024-05-07.
  15. ^ "OMG SysML". omgsysml.org. Retrieved 2014-12-04.

Further reading

[edit]
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Systems_modeling_language&oldid=1228436534"