SysML for Embedded Systems Modeling

SysML Modeling in Altova UModel

UModel SysML Modeling Features:

  • Supports all nine SysML diagrams
  • Enables hyperlinks between diagrams, supporting documents, or Web pages
  • Shared subprojects for team collaboration or reuse
  • Elements can be assigned to diagram layers and selectively viewed or hidden
  • Unlimited undo/redo encourages exploring new ideas
  • XMI model interchange with other SysML tools
  • SysML diagrams integrated with UML modeling for robust coverage of software project requirements
  • SysML diagrams and elements included in automated project documentation

Download Trial

UModel Supports SysML™ Modeling for Embedded Systems and Other Complex Devices

As an embedded system receives inputs and produces output, its internal operations and states can be opaque. This can make software to control embedded systems difficult to develop, test, and debug. Software modeling with Altova UModel and SysML lets you create a traceable blueprint that is useful for planning, designing, and documenting the system under development.

SysML diagrams can be divided into three types: diagrams that capture system requirements and physical constraints, diagrams that describe the structure of the system, and diagrams that describe the behavior of the system. UModel® 2017 supports all SysML diagrams and extensions.

UModel provides a SysML profile to support SysML stereotypes. You can insert the profile manually through the Project / Include menu option, or you can let UModel add the SysML profile automatically when you create your first SysML diagram in a new project.

A SysML Requirements diagram in Altova UModel
A SysML Use Case diagram in Altova UModel
A SysML Block Definition diagram in Altova UModel

SysML Requirements Diagram

The requirements diagram is a new diagram type in SysML, intended to describe functional, performance, and interface requirements – physical properties or constraints not captured in traditional UML use case diagrams.

SysML Use Case Diagram

SysML use case diagrams support all the features of UML use cases and add an allocation relationship element. UModel allows you to substitute any bitmap (.bmp) image to represent users in SysML use case diagrams.

SysML Block Definition Diagram

SysML employs the concept of blocks to specify hierarchies and interconnection within a system design. A UModel block definition diagram lets you describe relationships between blocks such as composition, association, and specialization.

A SysML Internal Block diagram in Altova UModel
A SysML Parametric diagram in Altova UModel
A SysML Package diagram in Altova UModel

SysML Internal Block Diagram

A SysML internal block diagram describes the internal structure of a block, its properties, and connectors. UModel empowers you to represent these features clearly and quickly.

SysML Parametric Diagram

A SysML parametric diagram illustrates system constraints such as performance, reliability, and physical properties. You can use a UModel parametric diagram to illustrate system weight constraints, for instance.

SysML Package Diagram

A SysML package diagram, like a UML package diagram, allows you to group elements in a hierarchical structure. In UModel, a package diagram can help you organize your SysML model in a way that synchronizes with the organization of the system under design.

A SysML Activity diagram in Altova UModel
A SysML Sequence diagram in Altova UModel
A SysML State Machine diagram in Altova UModel

SysML Activity Diagram

The SysML activity diagram describes the flow of control and data as the system executes. The syntax of SysML activity diagrams is identical to UML activity diagrams, with the extension of support for the allocation element.

SysML Sequence Diagram

The SysML sequence diagram, like the UML sequence diagram, lets you map detailed interactions among system components. UModel supports the SysML allocation extension.

SysML State Machine Diagram

SysML also borrows state machine diagrams from UML and extends them with the allocation element. Draw a UModel state machine diagram to describe your system’s state transitions and actions that it performs in response to events.

Next Steps