Fact Sheet: Systems Modeling Language (SysML)

PDF Download


Short description/
Transmitted information
  • Graphical, descriptive, semi-formal, modelling language

  • SysML is extension of UML2

  • Suitable for complex systems

Normative documents
Version / Release state
  • 1.5
Release date
  • May 2017
Application scope
  • Describe system-level use cases, actors and requirements

  • Describe system-level structure and behavior

  • general-purpose graphical modeling language for specifying, analyzing, designing, and verifying complex systems including
    • hardware, software, information, personnel, procedures, and facilities
    • traceability across multiple aspects/views („from requirement to test“)

    • cross-disciplinary communication and collaboration

    • lifecycle-oriented coverage

Promoting bodies
  • OMG

  • INCOSE including GfSE

  • prostep ivip Association
  • OMG Standard
IT Standard classification
  • Modeling Standard

Data format
  • Graphical modelling language

Additional available resources
Relevant prostep ivip project groups SysML Workflow Forum (SysML-WF) (prostep.org)

Positioning of SysML in V-Model


What is the contribution of especially this format/ standard to Systems Engineering and/ or Collaboration:

  • Simplify the model creation with SysML as a basis for visualization, complexity management and better handling of product views due to the product life cycle.
  • One industry-wide SysML profile to address many areas of common interest such as Automotive Regulatory Requirement & Verifications, Automotive Structures, Automotive Feature definitions, Risk Management (-FMEA, Functional Safety, Fault Tree analysis), integrated Dynamical Analysis and Optimization, ALM and PLM Integration
  • The Automotive Domain is witnessing rising SysML and MBSE adoption to cope with the pace of change-especially with Mechatronics seemingly entering every feature of the automobile.
  • An Automotive SysML profile accepted by the industry is not known to exist
  • If collaboration is not enabled, practitioners within the domain will create adhoc profile extensions and fragment the space.
  • Competing profiles that conflict within the same domain are a failure mode that will impede accelerated adoption of SE in general.
  • SE practitioners in a particular domain do become more efficient by extending the base SysML standard to meet their needs

Relevance and Benefit for MBSE

The Systems Modeling Language (SysML) is a general-purpose graphical modeling language for specifying, analyzing, designing, and verifying complex systems that may include hardware, software, information, personnel, procedures, and facilities. In particular, the language provides graphical representations with a semantic foundation for modeling system requirements, behavior, structure, and parametrics, which is used to integrate with other engineering analysis models. It represents a subset of  UML with extensions needed to satisfy the requirements of the UML. 

SysML has emerged as the de facto standard system architecture modeling language for Model-Based Systems Engineering (MBSE) applications.

Risks and Impediments

What happens if we do nothing

  • Software vendor solutions that will lock Auto OEMs into proprietary products not based on standards.
  • Major and lower tier suppliers unable to support diverging OEM proprietary standards without adding significant time and cost which eventually gets shared with the OEMs.
  • Supplier requirements not consideredà no collaboration possible