Skip to content

Prequisites

The following steps must be executed before this exercise: - Install EA 17.1 - Setup the environment according to the General Modeling Tutorial - Run EA and create a new project - Set the perspective (in the right-top corner) to "SysML" alt text

Create Package structure

  • Create a package in the model package called "Steering Wheel Heating System"
  • Click on the "Model" root package, press "CTRL+W", and in the pop-up menu, define the package name and select "Package only" OR
  • Click on the "Model" root package in the "Design" menu tab, press "Add a Package" button alt text
  • Create a package diagram
  • Click on "Steering Wheel Heating System" package and press "CTRL+N" and select "Add Diagram" OR
  • Right-click on the "Steering Wheel Heating System" package and select add diagram alt text
  • In the pop-up window, select Package diagram and select "Create Diagram" alt text
  • Make sure that the diagram toolbox is visible, if not, click on the "Toolbox" button in the "Design" menu tab alt text
  • Use the "Package" creation tool to create two packages: "Use cases" and "Requirements" alt text

Create use case diagram

  • Create a package diagram
    • Click on "Use cases" package and press "CTRL+N" and select "Add Diagram" OR
    • Right-click on the "Use cases" package and select add diagram
    • In the pop-up window, select Package diagram and select "Create Diagram" alt text
  • Create System Boundary using the toolbox alt text
  • Create actors and use cases using the toolbox alt text
  • For the "Vehicle Infotainment System" actor, use "Rectangular notation" by right-clicking on the element, and select "Appearance/Rectangular notation" alt text
  • Add "Extend", "Include", "Generalization", and "Communication" relationships between the actors and the use cases alt text
  • Define usage scenario for the "Heat the steering wheel" use case
    • Double click on the "Heat the steering wheel" use case, and the scenario editor will automatically appear alt text
    • Write down the steps of intended usage alt text
    • Add an exception path by right-clicking on step 3 and selecting "Add Exception Path" alt text
    • In the pop-up window, name the exception path alt text
    • Double-click on the exception path and write down the steps of exception handling alt text
    • Right-click on step 2 and select "Set Step as System" alt text
  • Generate an Activity diagram from the scenario:
    • Double-click on the basic path
    • Click on the generate diagram menu and select "Activity with Action" alt text
    • Open the generated activity diagram alt text

Create requirement diagram

  • Create a package diagram
    • Click on "Requirements" package and press "CTRL+N" and select "Add Diagram" OR
    • Right-click on the "Requirements" package and select add diagram
    • In the pop-up window, select Package diagram and select "Requirement Diagram" alt text
  • Use the "SysML Common" toolbox to create boundaries for FURPS grouping alt text
    • If the "SysML Common" toolbox is not visible, select the "Set Toolbox Visibility" option in the toolbox menu alt text
    • In the pop-up window, make sure that "SysML Common" is selected alt text
  • Create requirements using the toolbox alt text
  • Define the ID and Text of the requirements
    • Click on a requirement
    • Make sure that the "Properties" window is open. If not, select "Windows" in the Design menu tab and click on "Properties" alt text alt text
    • In the Properties window, set the ID and Text of the requirements alt text
  • Click anywhere on the diagram background, and in the "Compartments" tab of the properties window, select the "Tags" option alt text alt text
  • Define the nesting relations between the elements alt text