article

The Systems Modeling Language (SysML), is a domain-specific modeling language for systems engineering. 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. SysML is defined as an extension of a subset of the Unified Modeling Language (UML) using UML's profile mechanism.

SysML offers systems engineers several noteworthy improvements over UML, which tends to be software-centric. These improvements include the following:

  • SysML's semantics are more flexible and expressive. SysML reduces UML's software-centric restrictions and adds two new diagram types, Requirement and Parametric diagrams. The former can be used for requirements management; the latter can be used for performance analysis and quantitative analysis. As a result of 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 smaller language that is easier to learn and apply. Since SysML removes many of UML's software-centric and gratuitous constructs, the overall language is smaller as measured 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 will support requirments 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.0's thirteen diagrams, and adds two diagrams (Requirements and Parametric diagrams) and Allocation Tables, which can be dynamically derived from SysML diagrams. A table which compares SysML and UML 2.0 diagrams is available in the SysML FAQ.

The advantages of SysML over UML for systems engineering become obvious if you consider a concrete example, such as modeling an automotive system. With SysML you can use Requirement diagrams to efficiently capture functional, performance and interface requirements, whereas with UML you are subject to the limitations of Use Case diagrams to define high-level functional requirements. Likewise, with SysML you can use Parametric diagrams to precisely define performance and mechanical constraints such as maximum acceleration, curb weight, air conditioning capacity, and interior cabin noise management. UML provides no straightforward mechanism to capture this essential performance and mechanical information.

As for the rest of the automotive system, SysML enhanced Activity and State Machine diagrams can be used to specify the embedded software control logic 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

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 as part of the UML for Systems Engineering Request for Proposal (UML for SE RFP; OMG document ad/03-03-41) in March 2003.

In 2003 Cris Kobryn and Sanford Friedenthal organized and co-chaired the SysML Partners, an informal association of industry leaders and tool vendors, which initiated an open source specification project to develop the SysML in response to the UML for Systems Engineering RFP. 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. After a series of competing SysML specification proposals, a "SysML Merge Team" proposal was proposed to the OMG in April 2006.OMG document ad/06-03-01 This proposal was voted upon and adopted by the OMG as OMG SysML, which the OMG trademarked to differentiate it from the original open source specifications from which it was derived.

OMG SysML

The OMG adopted the OMG SysML specification in July 2006. The current OMG SysML specification is a Final Adopted Specification.OMG document ptc/06-05-04 An OMG Finalization Task Force plans to recommend a final version of OMG SysML in April 2007, which will need to voted upon again before it becomes a public Available Specification.

Since OMG SysML is derived from open source SysML, it also includes an open source license for distribution and use.

Tools

There are several modeling tool vendors who already offer SysML support, and are in the process of updating their tools to comply with the OMG SysML specfication. A list of tool vendors who support, or have announced support of, OMG SysML is available on the Official OMG SysML Website.

References

External links

Unified Modeling Language | Systems engineering

 

This article is licensed under the GNU Free Documentation License. It uses material from the "Systems Modeling Language".

Home Page • arts • business • computers • games • health • hospitals • home • kids & teens • news • physicians • recreation• reference • regional • science • shopping • society • sports • world