Fact Sheet: Systems Modeling Language (SysML)

PDF Download


Short Description/ Transmitted Information - Graphical, descriptive, semi-formal, modelling language
- SysML is extension of UML
- Suitable for mechatronic systems
Application Scope - Describe system-level use cases, actors and requirements
- Describe system-level structure and behavior
Maturity Automotive-specific shaping
Goals - Traceability across multiple aspects/views („from requirement to test“)
- Cross-disciplinary communication and collaboratio
- Lifecycle-oriented
Penetration Individual expert teams
Visibility Approx. 10%
Promoting Bodies - prostep ivip Association
- GfSE
Type OMG Standrad
IT Standard Classification Modeling Standard
Data Format Graphical modelling language
Relations to other standards - extension of UML
- leverages XMI for data exchange of SysML models
Overlap with other standards none


Software Vendors

Industry Users

  • Use Cases
  • Guidelines
  • Best Practice Examples
  • Literature (Books, Scientific Papers)
  • Best Practices

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

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