Price: $3,999.00
Length: 4 Days
Print Friendly, PDF & Email

SysML Training Crash Course

SysML Training Crash Course Description

SysML Training Crash Course covers the concepts, requirements, tools, and techniques of Systems Modeling Language (SysML). SysML Training Crash Course teaches you how to effectively collect requirements to design the embedded software based on the system specifications using UML 2 and SysML.

SysML Training Crash Course

SysML Training Crash Course helps you to make the appropriate architectural design of the system on the basis of your needs.

Such system architecture demonstrates a high level of agility to the embedded system software against changes as it provides a consistent traceability of the business rules captured in system functions and those of the usage choices (use cases) of the end-users toward the software implementation level.

TONEX SysML Training Crash Course Format

  • The training is delivered in the form of interactive presentation
  • The majority of the class is dedicated to practical activities
  • The training is a combination of lectures, labs, individual/group activities, and hands-on workshops
  • Participants are encouraged to bring in their own sample projects to work on under our instructors’ coaching, or they can use the real-world cases provided by our instructors

Audience

SysML Training Crash Course is a 4-day training course designed for:

  • System analysts
  • System architects
  • Systems engineers
  • Professionals moving into system-level engineering
  • Managers who are responsible for the delivery of software intensive systems

Training Objectives

Upon the completion of SysML Training Crash Course, the attendees are able to:

  • Comprehend a general approach to MBSE
  • Discuss various modeling techniques of the SysML
  • Provide functional requirements
  • Model dependencies between functional and non- functional requirements
  • Model system structure by applying block diagrams with parts and ports
  • Model physical and logical constraints, and studying trade-offs
  • Assign functionality in use cases over the system parts
  • Explain behavior by state machine diagrams
  • Explain behavior by activity diagrams
  • Address allocation of behavior, e.g. to software or hardware parts
  • Apply appropriate heuristics and evaluation techniques to obtain high quality models
  • Discuss the fundamental and the important detail of the Systems Modelling Language SysML
  • Create and sustain a diagram of hierarchical and interdependent written requirements
  • Generate and sustain traceability between requirements and produce reports of requirements and models
  • Generate an overview of the external functional requirements of a system with actors and apply cases on a use case diagram
  • Develop an efficient use case description in a satisfying way that pleases both non-technical and technical stakeholders
  • Model high-level system framework and decomposition using block definition diagrams, blocks, ports and relationships
  • Model the detailed internal framework of blocks on internal block diagrams using parts, ports, connectors and flows
  • Describe structural and functional components and restrictions using constraint blocks, parametric diagrams and constraint properties
  • Model simple, hierarchical and concurrent behavior using activities, actions, control and object flows on activity diagrams
  • Model timing, interaction and messaging between actors, blocks and parts using synchronous and asynchronous messages on sequence diagrams
  • Model state dependent behavior using states, transitions, events and actions on state machine diagrams

Course Outline

Overview

  • Systems engineering definition
  • Components of systems engineering
  • System concepts
  • SE process principles & elements
  • Requirements analysis
  • Development of physical solution description
  • Development of logical solution description MBSE: (model-based architecting/design)
  • System integration
  • Verification and validation
  • The system development life cycle with the harmony process
  • Overview of the UML/SysML diagrams used in requirements gathering, system analysis and design of the System Engineering domain
  • A Method based Framework for requirement gathering, system analysis and design

Language Architecture

  • Design principles
  • Architecture
  • Extension mechanisms
  • SysML diagrams

Compliance

  • Compliance with UML subset (UML4SysML)
  • Compliance level contents
  • Compliance with SysML extensions
  • Meaning of compliance

Language Formalism

  • Levels of Formalism
  • Specification Structure
    • Overview
    • Diagram Elements
    • UML Extensions
    • Usage Examples
  • Conventions and typography

Model Elements

  • Overview
  • Diagram Elements
  • UML Extensions
    • Diagram Extensions
    • Stereotypes
  • Usage examples

Blocks

  • Overview
  • Diagram Elements
    • Block Definition Diagram
    • Internal Block Diagram
  • UML Extensions
    • Diagram Extensions
    • Stereotypes
    • Model libraries
  • Usage examples

Ports and Flows

  • Overview
  • Ports
  • Flow properties, provided and required features, and nested ports
  • Proxy ports and full ports
  • Item flows
  • Deprecation of flow ports and flow specifications

Diagram Elements

  • Block Definition Diagram
  • Internal Block Diagrams

UML Extensions

  • Diagram Extensions
    • Directed Feature
    • Flow Property
    • Full Port
    • Invocation On Nested Port Action
    • Item Flow
    • Port
    • Proxy Port
    • Trigger On Nested Port
  • Stereotypes
    • Accept Change Structural Feature Event Action
    • Block
    • Change Structural Feature Event
    • Directed Feature
    • Feature Direction
    • Flow Direction
    • Flow Property
    • Full Port
    • Interface Block
    • Invocation On Nested Port Action
    • Item Flow
    • Proxy Port
    • Trigger On Nested Port
  • Usage Examples
    • Ports with Required and Provided Features
    • Flow Ports and Item Flows
    • Ports with Flow Properties
    • Proxy and Full Ports
    • Association and Port Decomposition
    • Item Flow Decomposition

Constraint Blocks

  • Overview
  • Diagram Elements
    • Block Definition Diagram
    • Parametric Diagram70
  • UML Extensions
    • Diagram Extensions
    • Stereotypes
  • Usage Examples

Activities

  • Overview
    • Control as Data
    • Continuous Systems
    • Probability
    • Activities as Blocks
    • Timelines
  • Diagram Elements
    • Activity Diagram
  • UML Extensions
    • Diagram Extensions
    • Stereotypes
    • Model Libraries
  • Usage Examples

Interactions

  • Overview
  • Diagram Elements
    • Sequence Diagram
  • UML Extensions
    • Diagram Extensions
  • Usage Examples
    • Sequence Diagrams

State Machines

  • Overview
  • Diagram Elements
  • State Machine Diagram
  • UML Extensions
  • Usage Examples
  • State Machine Diagram

Use Cases

  • Overview
  • Diagram Elements
  • Use Case Diagram
  • UML Extensions
  • Usage Examples

Allocations

  • Overview
  • Diagram Elements
    • Representing Allocation on Diagrams
  • UML Extensions
    • Diagram Extensions
    • Stereotypes
  • Usage Examples
    • Behavior Allocation of Actions to Parts and Activities to Blocks
    • Automotive Example
    • Tabular Representation

Requirements

  • Overview
  • Diagram Elements
    • Requirement Diagram
  • UML Extensions
    • Diagram Extensions
    • Stereotypes
  • Usage Examples
    • Requirement Decomposition and Traceability
    • Requirements and Design Elements
    • Requirements Reuse
    • Verification Procedure (Test Case)

Gathering Requirements and Translating Them into System Specifications

  • How to trace business and system requirements using the SysML requirement diagram
  • How to define the scope of the system included functions and use cases that invoke these functions
  • How to model the Life Cycle of the System that organizes transitions between its states where functions are activated
  • Testing cases by scenarios that recognize Use Cases and System Functions

Profiles & Model Libraries

  • Overview
  • Diagram Elements
    • Profile Definition in Package Diagram
    • Stereotypes Used On Diagrams
  • UML Extensions
  • Usage Examples
    • Defining a Profile
    • Adding Stereotypes to a Profile
    • Defining a Model Library that Uses a Profile
    • Guidance on Whether to Use a Stereotype or Class
    • Using a Profile
    • Using a Stereotype
    • Using a Model Library Element

Transforming System Specifications into Design Level Components

  • How to model the Block Diagram of the system and modify it by internal blocks
  • How to develop the Communication Architecture between Sub-System using Parts, Ports and Interfaces
  • How to model the description of white box Interactions in the design stage
  • How to Map Operations on the Components (Parts) of Blocks
  • Developing the Parametric Diagram of the System Functions

SysML Training Crash Course Hands-on Activities

  • In-Class Labs
  • Case Studies
  • Videos

 

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.