Systems modeling language: Difference between revisions

Browse history interactively ← Previous edit Next edit →Content deleted Content addedVisual WikitextInline

Revision as of 15:52, 4 December 2014 editWalter Görlitz (talk \| contribs)Extended confirmed users, Pending changes reviewers294,571 edits Filled in 5 bare reference(s) with User:Zhaofeng Li/Reflinks (5ab98b1) + removed inline external links, redlinks and bad ELs (fan/user groups, how-tos, etc. per WP:ELNO).← Previous edit		Revision as of 15:53, 4 December 2014 edit undoWalter Görlitz (talk \| contribs)Extended confirmed users, Pending changes reviewers294,571 edits access dates to ISO 8601 formatNext edit →
Line 14:		Line 14:
	* SysML model management constructs support models, views, and viewpoints. These constructs extend UML's capabilities and are architecturally aligned with ] (IEEE Recommended Practice for Architectural Description of Software Intensive Systems).		* SysML model management constructs support models, views, and viewpoints. These constructs extend UML's capabilities and are architecturally aligned with ] (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=http://www.sysmlforum.com/faq/\|title=SysML Forum: SysML FAQ - What is SysML?, Why use SysML?, Who created SysML?\|work=sysmlforum.com\|accessdate=~~4 December~~ 2014}}</ref>		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>

	The advantages of SysML over UML for systems engineering become obvious if you consider a concrete example, like 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 ] to define high-level functional requirements. Likewise, with SysML you can use Parametric diagrams to precisely define performance and quantitative constraints like maximum ], minimum ], and total ] capacity. UML provides no straightforward mechanism to capture this sort of essential performance and quantitative information.		The advantages of SysML over UML for systems engineering become obvious if you consider a concrete example, like 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 ] to define high-level functional requirements. Likewise, with SysML you can use Parametric diagrams to precisely define performance and quantitative constraints like maximum ], minimum ], and total ] capacity. UML provides no straightforward mechanism to capture this sort of essential performance and quantitative information.
Line 30:		Line 30:
	After a series of competing SysML specification proposals, a SysML Merge Team was proposed to the OMG in April 2006.<ref></ref> 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.		After a series of competing SysML specification proposals, a SysML Merge Team was proposed to the OMG in April 2006.<ref></ref> 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.<ref>{{cite web\|url=http://www.omg.org/spec/SysML/1.0/PDF\|title=SysML 1.0\|work=omg.org\|accessdate=~~4 December~~ 2014}}</ref> The current version of OMG SysML is v. 1.3, which was issued by the OMG in June 2012.<ref>{{cite web\|url=http://www.omg.org/spec/SysML/1.3/PDF\|title=SysML\|work=omg.org\|accessdate=~~4 December~~ 2014}}</ref>		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=SysML 1.0\|work=omg.org\|accessdate=2014-12-04}}</ref> The current version of OMG SysML is v. 1.3, which was issued by the OMG in June 2012.<ref>{{cite web\|url=http://www.omg.org/spec/SysML/1.3/PDF\|title=SysML\|work=omg.org\|accessdate=2014-12-04}}</ref>

	== Tools ==		== Tools ==

	There are several modeling tool vendors already offering SysML support, or are in the process of updating their tools to comply with the OMG SysML specification. Lists of tool vendors who support, or have announced support of, SysML or OMG SysML can be found on the SysML Forum<ref>{{cite web\|url=http://www.SysMLforum.com\|title=SysML Forum: What is SysML? - What You Need to Know\|work=sysmlforum.com\|accessdate=~~4 December~~ 2014}}</ref> or SysML<ref>{{cite web\|url=http://www.omgsysml.org\|title=OMG SysML\|work=omgsysml.org\|accessdate=~~4 December~~ 2014}}</ref> websites, respectively.		There are several modeling tool vendors already offering SysML support, or are in the process of updating their tools to comply with the OMG SysML specification. Lists of tool vendors who support, or have announced support of, SysML or OMG SysML can be found on the SysML Forum<ref>{{cite web\|url=http://www.SysMLforum.com\|title=SysML Forum: What is SysML? - What You Need to Know\|work=sysmlforum.com\|accessdate=2014-12-04}}</ref> or SysML<ref>{{cite web\|url=http://www.omgsysml.org\|title=OMG SysML\|work=omgsysml.org\|accessdate=2014-12-04}}</ref> websites, respectively.

	=== Model Exchange ===		=== Model Exchange ===

Revision as of 15:53, 4 December 2014

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

Overview

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 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 smaller language that is easier to learn and apply. Since SysML removes many of UML's software-centric constructs, the overall language measures 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 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.

The advantages of SysML over UML for systems engineering become obvious if you consider a concrete example, like 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 Diagram to define high-level functional requirements. Likewise, with SysML you 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

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.

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.

OMG SysML

After a series of competing SysML specification proposals, a SysML Merge Team was proposed to the OMG in April 2006. 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. The current version of OMG SysML is v. 1.3, which was issued by the OMG in June 2012.

Tools

There are several modeling tool vendors already offering SysML support, or are in the process of updating their tools to comply with the OMG SysML specification. Lists of tool vendors who support, or have announced support of, SysML or OMG SysML can be found on the SysML Forum or SysML websites, respectively.

Model Exchange

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.

List of SysML Tools

No Magic Cameo Systems Modeler
Artisan Studio
Sparx Systems Enterprise Architect
IBM Rational Rhapsody
Lattix Architect
Modelio
Papyrus
Software Ideas Modeler
SysML Designer
Visual Paradigm
SCADE System
Topcased

References

^ SysML Forum. "SysML FAQ". Retrieved 2009-08-26.
"SysML Forum: SysML FAQ - What is SysML?, Why use SysML?, Who created SysML?". sysmlforum.com. Retrieved 2014-12-04.
OMG SE DSIG. "UML for Systems Engineering RFP". Retrieved 2006-06-29.
"SysML Partners". Retrieved 2006-06-29.
SysML Forum. "SysML FAQ". Archived from the original on 2006-07-16. Retrieved 2006-06-29.
OMG document ad/06-03-01
"SysML 1.0". omg.org. Retrieved 2014-12-04.
"SysML". omg.org. Retrieved 2014-12-04.
"SysML Forum: What is SysML? - What You Need to Know". sysmlforum.com. Retrieved 2014-12-04.
"OMG SysML". omgsysml.org. Retrieved 2014-12-04.

External links

SysML Open Source Specification Project Provides information related to SysML open source specifications, FAQ, mailing lists, and open source licenses.
OMG SysML Website Furnishes information related to the OMG SysML specification, SysML tutorial, papers, and tool vendor information.
Using SoaML services architecture by Jim Amsden, a co-author of the OMG SoaML standard.
Modeling with SoaML, the services-oriented architecture modeling language, a five-part series by Jim Amsden.
Article "EE Times article on SysML (May 8, 2006)"
SE^2 MBSE Challenge team: "Telescope Modeling"
Paper "System Modelling Language explained" (PDF format)

v t e Systems engineering
Subfields	Aerospace engineering Biological systems engineering Cognitive systems engineering Configuration management Earth systems engineering and management Electrical engineering Enterprise systems engineering Health systems engineering Performance engineering Reliability engineering Safety engineering Sociocultural Systems Engineering
Processes	Requirements engineering Functional specification System integration Verification and validation Design review System of systems engineering
Concepts	Business process Fault tolerance System System lifecycle V-Model Systems development life cycle
Tools	Decision-making Function modelling IDEF Optimization Quality function deployment System dynamics Systems Modeling Language Systems analysis Systems modeling Work breakdown structure
People	James S. Albus Ruzena Bajcsy Benjamin S. Blanchard Wernher von Braun Kathleen Carley Harold Chestnut Wolt Fabrycky Barbara Grosz Arthur David Hall III Derek Hitchins Robert E. Machol Radhika Nagpal Simon Ramo Joseph Francis Shea Katia Sycara Manuela M. Veloso John N. Warfield
Related fields	Control engineering Computer engineering Industrial engineering Operations research Project management Quality management Risk management Software engineering
Category

v t e Systems Modeling Language
Actors	International Council on Systems Engineering Object Management Group SysML Partners
Concepts	Activity Actor Association Attribute Block diagram Event Functional flow block diagram Generalization Inheritance Interface Message passing Object composition Object-oriented analysis and design Package Parametric equation Profile State Use case
Other topics	Systems engineering Unified Modeling Language XML Metadata Interchange

Unified Modeling Language

Actors

Organizations
- Object Management Group
- UML Partners
Persons

Concepts

Object oriented	Object-oriented programming Object-oriented analysis and design Object-oriented modeling
Structure	Actor Attribute Artifact Class Component Interface Object Package Profile diagram
Behavior	Activity Event Message Method State Use case
Relationships	Association Composition Dependency Generalization (or Inheritance)
Extensibility	Profile Stereotype
Other	Multiplicity

Diagrams

Structure	Class Component Composite structure Deployment Object Package
Behaviour	Activity State Machine Use case
Interaction	Communications Sequence Interaction overview Timing

Derived languages

Misplaced Pages