The SysML Modelling Language - Fifth European Systems Engineering Conference - 18-20 September 2006

Oct 25, 2026

Upload by vwvw

Background and rationale for adopting OMG Systems Modeling Language (SysML) as a final specification following the joint OMG and INCOSE Request for Proposal for a UML 2 customization. Explains how SysML extends UML 2 with new diagrams and constructs to support specification, analysis, design, verification, and validation of complex systems spanning hardware, software, data, personnel, procedures, and facilities. Summarizes key specification elements, including modifications to UML 2.0, new requirement modeling, and parametric diagrams, within the context of limitations of UML for systems engineering.

LanguageEnglish

CategoryTechnology

FormatPDF

Pages12

Reading Time30 min

AccessFree to download

Introduction

Shortcomings of UML

Problems with UML 1.x

UML 2.0

The SysML Modelling Language Fifth European Systems Engineering Conference 18-20 September 2006 Matthew Hause Artisan Software Tools, Eagle Tower Suite 701, Cheltenham, Glos. UK, [MatthewH@Artisansw.com](MatthewH@Artisansw.com) Copyright © 2006 by Matthew Hause. Published and used by INCOSE with permission. On July 6th 2006, the Object Management Group™ (OMG™) announced the adoption of the OMG Systems Modeling Language (OMG SysML™) as a final adopted specification. The OMG SysML specification was in response to the joint Request for Proposal issued by the OMG and INCOSE (the International Council on Systems Engineering) for a customized version of UML 2 designed to address the specific needs of system engineers. The OMG SysML specification was developed by a broad-based team including tool vendors, leading industry users, government agencies and professional organizations over a period of 3 years. Creating the SysML specification, for which Artisan was the Specification Architect has been a mammoth task in which over 100 man-years of effort has been invested. OMG SysML is a visual modelling language that extends UML 2 in order to support the specification, analysis, design, verification and validation of complex systems that include components for hardware, software, data, personnel, procedures and facilities. OMG SysML is intended to be used with different methodologies including structured analysis, object orientation and others. OMGSysML reuses a subset of UML 2 concepts and diagrams and augments them with some new diagrams and constructs appropriate for systems modelling. This paper will look at the background of OMG SysML and summarize the OMG SysML specification including the modifications to UML 2.0, along with the new requirement and parametric diagrams. INTRODUCTION The Unified Modelling language (UML) has, since its adoption in 1997, proved immensely popular with software engineers to the point where it is now the only widely used visual modelling language for software engineering. In the past, UML’s software focus has discouraged many system engineers from adopting it in earnest. There were various approaches used to address the shortcomings of UML for Systems Engineers. Some made use of the stereotypes provided in UML to create “libraries” or profiles of entities in their application domain. By applying these, they were able to express non-software concepts (Hause, 2003) . Others used tools such as Microsoft Visio to model their Systems Engineering concepts, in conjunction with their UML model. However, with this approach they were left with two separate models that they were unable to integrate or crossreference. Some simply ignored the problem or used words to fill the gap. Some tool manufacturers such as Artisan Software Tools extended UML, allowing integration of Hardware, Software, and Systems Engineering concepts in a single model (Hause 2001) . This left them open to a charge of being “non-standard”. However, as most Systems Engineers are pragmatists, this argument was not usually effective. In fact, most of the concepts outlined in Hause (2001) have been integrated into UML 2.0 and OMG SysML. Lykins (2000) provides an early paper on trying to adapt UML to SE and some of the issues. Shortcomings of UML. Those who know UML find it to be an effective modelling language. The roots of UML are firmly in software OMG (1997) states that the “Unified Modelling Language (UML) is a generalpurpose visual modelling language that is designed to specify, visualize, construct and document the artefacts of a “software system” [italics mine] . In the UML 2.0 version of the specification, software system has been replaced by system [OMG, 2003a] . This reflects the increased use of UML by systems engineers and users from other domains. The UML is sufficiently flexible and robust to support extensions to address the needs of systems engineering. One of the strengths of UML is its built-in mechanisms for specia

FAQs

Why was OMG SysML developed from UML 2?

OMG SysML responded to an OMG and INCOSE Request for Proposal for a customized UML 2 version aimed at the needs of system engineers.

What does SysML add compared with UML 2?

SysML reuses a subset of UML 2 concepts and diagrams, and augments them with new diagrams and constructs suitable for systems modeling.

What limitations of UML are highlighted for systems engineers?

The document discusses UML’s software-centric focus and specific UML 1.x issues such as limited physical node modeling, awkward use case behavior linking, and insufficient support for requirements and parametric equations.

Oct 25, 2026

Upload by vwvw