Basic systems engineering design in Rhapsody®
This tutorial demonstrates how to apply a SysML profile to project, and how to design a basic structure and behavior.
Learning objectives
The tutorial demonstrates the following key concepts:- Relationships of requirements to use cases
- Methods to define behavior
- Methods to define structure
- Relationships of required behavior to system architecture and validation approaches
- Techniques for handing off the project to software developers
Note: The tutorial begins with a SysML model that contains some artifacts. You can use the
Spa and pool
temperature control architecture model to start working with this
tutorial.
Time required
4 hours- Introduction: Basic systems engineering design in IBM Engineering Systems Design Rhapsody
The systems engineering tutorial starts with a SysML project containing artifacts for an outdoor spa pool temperature controller. Instructions and demonstrations help you to complete the simple architecture and hand it off to software engineers. - Tutorial setup: Downloading the starting point project
In this lesson, you download the starting point project for the tutorial from a wiki and open it. - Lesson 1: Analyzing requirements
In this lesson, you view a short tour of the requirements and requirements table and edit the project. - Lesson 2: Tracing requirements in use cases
In the previous lesson, you reviewed the requirements and learned the difference between functional and nonfunctional requirements. This lesson contains a short video showing the use cases in the starting point project and their relationships. Analysis of the use cases gives you information about both the structure and the behavior of the system. - Lesson 3: Creating standard value types
Most of the attributes have already been added to the SystemUnderControl block. In this lesson, you add the mass of the water to the block. Since the mass of water is expressed in kg, you begin by specifying an applicable valueType, kg. The other attributes already have valueTypes. - Lesson 4: Connecting blocks and analyzing behavior
Additional analysis of the use cases defines the structural and behavioral composition of the control system. The two essential systems are specified as SysML blocks–a ControlSystem block and a SystemUnderControl block. Use an internal block diagram to create the structural design. - Lesson 5: Adding a statechart to the behavioral design
In this lesson, you will learn how to add a statechart to the SystemUnderControl in order to model the essential behavior. - Lesson 6: Defining a constraint and adding a parametric diagram
In this lesson, you examine the block definition diagram that specifies the context of the model in terms of its high level structural elements, the SystemUnderControl and ControlSystem blocks, as well as the constraint that specifies the behavioral dependency between these blocks. - Lesson 7: Simulating the model
This lesson shows how to use model simulation to check the design and guides you to run the same simulation on the tutorial model. - Lesson 8: Building the architecture of the control system
In this lesson, you create a block definition diagram, add block properties, add components, and create an internal block diagram for the ControlSystem. - Lesson 9: Specifying behavior and simulating the model
In this lesson you, specify the high-level behavior of the control system components by using statecharts and simulate the full model. - Lesson 10: Delivering projects to software engineers
This lesson shows you how to deliver specification information to the software engineers.