Introduction To SysML for Systems Engineers

Course Description

This one-day course for Systems Engineers introduces the Systems Modelling Language (SysML) and how it can address the needs of systems engineers. The course addresses key issues relating to Systems Engineers such as modelling requirements, physical and logical architectures, parametric equations, and behavioural modelling,. It includes all SysML diagrams and cross-cutting notations.

Course Objectives

• To provide an awareness of the principles and concepts inherent in SysML.
• To describe the structure and content of SysML.
• To enable attendees to appreciate SysML modeling techniques.

Attendees Receive

• An annotated copy of all course presentation material.
• All course exercises and solutions.

Course Format

Much of the course involves presentation of key principles and concepts. A real-time case study is introduced which allows illustration of SysML modeling techniques and discussion of their use.

Course Outline

Introduction

• The purpose, structure and benefits of SysML.
• The relationship between SysML and UML.
• Key UML concepts used in SysML.

SysML Model Elements

• Packages and the Package Diagram.
• Note types.
• Views and Viewpoints.

Requirements Modeling

• The rationale for requirement modeling.
• Requirements and the Requirement Diagram.
• Relating requirements – child and derived requirements.
• Capturing requirements and structuring the requirements model.

Structural Modeling

• Blocks and block properties.
• DataTypes and ValueTypes.
• Block Definition Diagrams – usage and notation.
• Internal Block Diagrams – usage and notation.
• Ports, Flows and Interfaces.
• Constraints and Constraint Blocks.
• The Parametric Diagram – usage and notation.

Behavior Modeling

• Use Case Modeling – defining actors and use cases to capture externally-driven system functionality.
• Activity Diagrams – flow-based modeling of activity within the system.
• Sequence Diagrams – defining interaction between system elements.
• State Machine Diagrams – capturing state-based behavior.

Cross-cutting Constructs

• Requirements traceability – relating requirements to other model items.
• Allocations – the concept of allocation, types of allocation and allocation techniques.

Process Issues

• What diagrams in what order?
• Software engineering handover.