Sysml a modeling language for systems of systems
1 / 64

SysML: A Modeling Language for Systems of Systems - PowerPoint PPT Presentation

  • Uploaded on

SysML: A Modeling Language for Systems of Systems. Note to Instructor: The material in this slide set is not contained in the 3 rd edition of the text book It is planned for the 4 th edition. What is SysML?. A graphical modeling language developed by the OMG

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'SysML: A Modeling Language for Systems of Systems' - daire

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Sysml a modeling language for systems of systems

SysML:A Modeling Language for Systems of Systems

Note to Instructor:

The material in this slide set is not contained in the 3rd edition of the text book

It is planned for the 4th edition.

What is sysml
What is SysML?

  • A graphical modeling language developed by the OMG

    • A UML profile that presents a subset of UML 2 with extensions

  • A modeling language for modeling “systems of systems”

    • Supports the development of complex systems consisting of several systems

    • Model exchange via XMI

  • Designed for model-based systems engineering (MBSE)

Relationship between sysml and uml
Relationship between SysML and UML

  • SysML is defined as an extension of a subset of the Unified Modeling Language (UML) using UML's profile mechanism

  • SysML is MOF compliant

All models (MOF)

UML models

CORBA models



.NET models







SysML models



Use Case






Model based systems engineering mbse
Model Based Systems Engineering (MBSE)

  • Model-based systems engineering (MBSE)

    • The formalized application of modeling to support system requirements, design, analysis, verification, validation activities[INCOSE 2004]

  • Advantages

    • Improved communications and knowledge management

    • Impact analysis of requirements and design changes

    • More complete representation

  • A system engineering model contains several models addressing all aspects of the participating systems, hardware as well as software:

    • Functional model

    • Behavoral model (Dynamic model)

    • Structure model (Object model)

    • Cost model

    • Organizational model

    • Development environment, target environment

A sysml model contains several models
A SysML Model contains several Models


Functional Model

Dynamic (Behavior) Model

Object (Structure) Model

Other Models

Sysml diagram frames
SysML Diagram Frames

Activity diagram, block diagram, internal block diagram, sequence diagram

Sysml diagram taxonomy
SysML Diagram Taxonomy





Sysml structural diagrams
SysML Structural Diagrams

Requirements Diagrams

Sysml requirements diagrams
SysML Requirements Diagrams

  • A SysML requirements diagram depicts the requirements in graphical, tabular or tree structure format

  • Example: A Requirements Diagram in Visual Paradigm

Requirement node case tool visual paradigm
Requirement Node (CASE tool:Visual Paradigm)

  • A requirement node is a stereotype of a UML Class

  • It has several attributes

    • Text: the description of the requirement in natural language

    • Id: Allows to number the requirement

    • Source: Location, Stakeholder

    • Kind: to categorize the requirement into Functional, Performance, Interface

    • VerifyMethod: Analysis, Demonstration, Inspection, Test

    • Risk: High, medium, low

    • Status: Proposed, Approved, Rejected, Deferred, Implemented, Mandatory, Obsolete.

Visual paradigm
Visual Paradigm

  • University License for Visual Paradigm Standard Edition

  • Visual Paradigm Tutorials


    • Requirements Modeling with Visual Paradigm


      • On this URL you also find a tutorial movie about managing SysML requirement diagrams.

Dependency relationships linking of requirements
Dependency Relationships: Linking of Requirements

  • Requirements can be linked to other requirements

    • Containment: The requirement contains several sub-requirements

    • Copy: One requirement is a read-only version of another requirement

    • Derive: A requirement is derived from another requirement

  • Requirement elements can also be linked to other model elements (in analysis and design models)

    • Refine: A model element refines a requirement

    • Verify: Another model element validates a requirement

    • Satisfy: Another model element satisfies a requirement

      • Linking to Use Cases

      • Linking to Class diagrams

    • Trace: Any model element that realizes a nonfunctional (performance) requirement.

Requirements diagram elements associations between nodes3
Requirements Diagram Elements: Associations between Nodes

  • Copy Dependency

The text of the Slave requirement is a read-only copy of the text of the Master requirement

  • Derive Dependency

A functional requirement derived from a business need or a test requirement is derived from a functional requirement

  • Satisfy Dependency

Functional Requirement

Business Need

Example: A use case satisfies a functional requirement.

Example of a derive dependency
Example of a Derive Dependency

  • Based on the requirement specifications from the National Highway Traffic Safety Administration (NHTSA.)

  • Excerpt of the original requirement text used to create the model:

Requirements diagram elements associations between nodes4
Requirements Diagram Elements: Associations between Nodes

  • Verify Dependency

Example: A test case validates a functional requirement

Example: A use case refines a requirement

  • Refine Dependency

Example: A use case can be traced to a requirement.

  • Trace Dependency

Callouts or how to avoid spaghetti in requirements diagrams
Callouts Or: How to avoid “Spaghetti” in Requirements Diagrams

Is equivalent to:

  • TraceCallout

  • Trace Dependency

Sysml structural diagrams1
SysML Structural Diagrams

Package Diagrams

Organizing a model by use cases
Organizing a Model by Use Cases

Tim Weilkiens, Systems engineering with SysML/UML: modeling, analysis, design‬

Organizing a model by stakeholders
Organizing a Model by Stakeholders

SysML allows provide viewpoints for the stakeholders of a system

Package diagram views and viewpoints
Package Diagram: Views and ViewPoints

  • A model usually focuses on one abstraction of the system (analysis, design, cost)

  • A view provides a perspective that spans multiple abstractions. It includes (subgraphs) of other models

  • The EngrAnalysis view, for example, includes the organization of the enterprise, the system model, logical design and allocated design

  • The viewpoint lists the stakeholders and purpose of the view.

Sysml blocks vs uml classes
SysML Blocks vs UML Classes

  • SysML Blocks are based on UML classes

    • However the do not allow association classes

    • They distinguish between value properties from part properties

    • They allow nested connector ends

  • There are two types of SysML block diagrams

    • Block definition diagrams (bdd) describing the relationship between blocks (composition, association,…)

    • Internal block diagrams (ibd) describing the internal structure of a single block in terms of its properties and connectors

  • Behavior (activity diagrams, use cases) can be allocated to both types of block diagrams.

Sysml block diagrams
SysML Block Diagrams

Internal Block


Block Definition Diagram



Internal block diagram blocks parts ports connectors and flows
Internal Block Diagram: Blocks, Parts, Ports, Connectors and Flows

Sysml ports
SysML Ports

  • 2 Port Types

    • Standard Port (also available in UML)

      • Specifies a set of operations and/or signals

      • Typed by a UML interface

    • Flow Port

      • Specifies what can flow in or out of a block/part

      • Typed by a flow specification.

Sysml activities
SysML Activities

  • SysML activity diagram notation is the same as in UML

  • SysML extensions to support

    • Continous flow modeling

    • Alignment of activities with Enhanced Functional Flow Block Diagrams (EFFBD)

Sysml activity diagrams also support swim lanes
SysML Activity Diagrams also support Swim Lanes



Swimlane BrakeModulator

Sysml activities can consists of subactivities
SysML Activities can consists of Subactivities

Activity Diagram

Block Definition Diagram

Sysml interactions
SysML Interactions

  • SysML sequence diagram notation is also the same as in UML

    • but SysML does not include timing diagrams and communications diagrams

  • SysML focuses on black and white box views of interactions with sequence diagrams.

Sysml state machines
SysML State Machines

  • The same notation as in UML

Sysml use cases
SysML Use Cases

  • SysML use cases: Also no change from UML

Additional information
Additional Information

[INCOSE 2004]

  • Systems Engineering Vision 2020, International Council for Systems Engineering, Technical Report INCOSE-TP-2004-004-02, September 2004


    [SysML Tutorial 2009] Sanford Friedenthal, Alan Moore, Rick Steiner

  • OMG Systems Modeling Language Tutorial,

  • pdf

  • This lecture is based on this tutorial

    SysML Requirements Modeling with Visual Paradigm


  • Here you also find a movie about requirements diagrams

  • Visual Paradigm Standard Edition for UML and SysML

    • Download Link:

    • Unlimited Educational License, Key will be provided in the SE 1 forum

    • Installed on all the computers at the chair for applied software engineering

  • Unicase (Research Tool)


    • Open source. Masterthesis offered: Feature Modeling, a modeling language replacing SysML

  • Sysml block property types
    SysML Block Property Types

    • Part Property

      • A Part is owned by a block (composition)

      • Example: Right-Front Wheel is part of the Vehicle block

      • The part stops existing, when the block stops existing

    • Reference Property

      • A part is not owned by the enclosing block

      • Example: An interface between two parts

    • Value Property

      • Allows to define a value with units, dimensions and even probability distribution

      • Examples:

        • Non-distributed value: tirePressure:psi=30

        • Distributed value: <<uniform>> {min=28, max = 32} tirePressure:psi

    Allocation of hardware to software lecture on system design topic hardware software mapping
    Allocation of Hardware to Software (-> Lecture on System Design, Topic Hardware-Software Mapping)