Importing a Design from a Systems Modeling Language Project

You can import Systems Modeling Language (SysML) projects from IBM Engineering Systems Design Rhapsody® 9.0.1 and Capital™ Software Developer with IBM Rhapsody® 9.2.0. There are various prerequisites that must be met before the import.

Prerequisites

• This import functionality is an add-on to Capital Systems Modeler and requires a valid license (for Rhapsody Project Import) in order to enable the functionality. Contact Capital Support to obtain a license. Your system administrator enables access to add-on functionality by using license policies and user groups (see “License Policy” in the Capital Access Manager User Guide).

• Your user account must have the Import Design permission enabled.

• When importing, you reference a configuration file that specifies your allow-listing and mapping criteria, and the style set to be applied to the imported design diagrams. You must create and edit this file as required. A template for this configuration file that allow-lists everything in the SysML project is available here: \config\SYSMLImportConfiguration.xml.example. Contact Capital Support to customize the configuration file.

• You must specify the mandatory property on the project into which you have imported the designs: SYSML Application Path. Caution If you switch between different Rhapsody installations for successive imports of SysML projects, Capital Systems Modeler must be restarted between each such import, otherwise an error will be displayed.
  Caution The Capital administrator must ensure that write-permissions are restricted on the rhapsody.jar file found in \Share\JavaAPI before specifying the project property SYSML Application Path. This needs to be done with the help of the system administrator. Your organization is responsible for the security of that location. Access should be restricted to authorized users only. Only authorized users should have permission to update the project property SYSML Application Path.
  There are also optional properties that you can specify.

Table 2: Mandatory and Optional Project Properties Property Name

									Description

								

							

						

							
								
									SYSML Application Path

									Note 
										Mandatory

									

								

								
									The root path of the Rhapsody
										installation.

									For example:

									C:\Siemens\Rhapsody

								

							

							
								
									SYSML Source Project

									Note 
										Optional

									

								

								
									The path to the source Rhapsody project
										for the import. This value populates the Source Project
										field on the Import System Model dialog box when you
										import.

									For example:

									C:\Rhapsody\Projects\RhapsodyProject.rpyx

								

							

							
								
									SYSML Import Configuration

									Note 
										Optional

									

								

								
									The path to the configuration file for
										the import. This value populates the Configuration field
										on the Import System Model dialog box when you
										import.

									For example:

									C:\Config_files\ImportSysMLProject.xml

								

							

						

				See Editing the

Attributes and Properties of a Project for instructions on how to edit project properties.

• The Rhapsody application must be opened when you perform an import from it.

Procedure

1. With the Capital project open, click the SysML Import action on the Workflow ribbon tab at the top of the application.
   
   
   
   The Import System Model Dialog Box displays.

2. Specify the path to the source Rhapsody project and the configuration file that you want to use. Click Import.
   A SysML Import dialog box indicates the progress of the import.
   
   Once the import is complete, the Import Designs to Project dialog box displays.

3. You must specify a revision for each design.

                The Source Design and Name values are automatically
                    completed.
   

4. Click OK to complete the import.

Results

• The SysML project and the objects in it are converted into a Capital XML format and Capital objects. See Table 1 for a list of how various SysML objects are translated into Capital objects.

• When you first import a design, the system creates new functional designs in the currently open project. When you import updates for an already existing functional design, the action creates a new design revision unless you choose to overwrite the existing one.

• The style set defined in the configuration file is applied to the diagrams. Note If the specified style set is not available, an error displays.

• The functional designs, diagrams, and objects in the designs have additional properties populated from the SysML project, such as SYSML Description, SYSML GUID, SYSML Label, and SYSML Stereotypes, or the user-defined properties specified as the in the configuration file selected in step 2. User-defined properties are only on designs.

• A log file is saved in the temp folder for Capital. By default, the file name is SysML_Import followed by a timestamp (date and time). For example, SysML_Import_2022-09-01_15-45-26.log. You can configure whether the file name has a timestamp or not. See Configuring the Log File for Import of Systems Modeling Language Projects.

Note

Flow properties or connectors connected to the Internal Block Diagram (IBD) frames are imported as non-shared signals or messages. You can use batch share functionality to detect these and share them in the functional designs. See Batch Sharing Objects in a Function Build List.

The property SYSML GUID is a special property that exists on all signals and messages that are imported from Rhapsody. This property will have different values on different instances of non-shared, design-wide objects. However, this is a read-only property. Similarly to all read-only properties, the Batch Share action will not report conflicts in the values of the SYSML GUID property. The action will retain the property value from the one selected as ‘Share’, if there is no existing shared object revision matching the criteria. The action will retain the existing value on the shared object if there is an existing shared object revision matching the criteria.

Parent Topic:

Systems Modeling Language Projects

Capital Systems Modeler User Guide, 2512.2606

Unpublished work. © 2026 Siemens