Systems Engineering Using SysML

Course Description

Designed specifically for systems engineers, this training course shows the relevance of SysML modeling techniques for system engineering activities on a variety of project types and sizes. It is suitable for people wishing to know what SysML offers and how to best use it. The course uses a mix of presentations and hands-on practicals.

Course Objectives

• To provide an understanding of the principles and concepts inherent in SysML.
• To describe the structure and content of SysML.
• To enable attendees to apply SysML modeling techniques using Artisan Studio.

Attendees Receive

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

Course Format

Presentations and discussion are used to convey concepts, techniques and notation. Case study exercises allow practical application of the techniques. Attendees work individually or in small groups to complete a number of worked examples, providing hands-on experience of applying the techniques and re-enforcing the concepts. Use is made of Artisan Studio to facilitate an understanding of the relationship between the various diagrams and model items.

Course Outline

Introduction

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

Understanding Artisan's SysML Modeling Environment

• Artisan Studio essentials.
• The Artisan SysML profile.

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.