On this page:

The CATIA Software Producer allows you to generate and build code from a UML or SysML model. You can generate code, for example, from the UML Class structure,  UML State Machine, or SysML Blocks. The code generation and building are executed via the 3DEXPERIENCE platform. 

Key concepts and capabilities

CATIA Software Producer offers the following generation capabilities:

• Generating C++ classes from UML structured classes
• Generating C and C++ code from UML behaviors
• Generating target dependent middleware code including AUTOSAR classic and adaptive
• Generating and compiling code for FMU
• Generating code from a model persisted as a file, or in TeamWorkCloud or in the 3DEXPERIENCE Platform.
• Generate code containing traceability information establishing the relation from the model items to the code.

CATIA Software Producer uses the concept of target configuration to guide the user in configuring the code generation process.

Prerequisites

• The CATIA Software Producer Client plugin is installed in your modeling tool. Learn more about how to download the installation files.

• The 3DEXPERIENCE platform is on the cloud.

• You have the Software Production Engineer Role. It will give you permission to use the service.

Before starting to work on code generation, first, you have to connect to 3DEXPERIENCE by entering the URL of the Software Producer cloud server. After that, you will be able to log in with your regular identifiers.

Working with the code generator

The principle 

The full set of code you need to generate to cover your target is composed of at least a component and a target-specific part. The component part is relative to the behavior of your application (such as State Machine) whereas the target-specific part is relative to the architecture of your application (such as IBD). In other words, target specific is the binder and the link between the component and the target. As one does not go without the other, this is why at the end of the IBD generation, a dialog will ask you if you want the applicative code to be automatically generated if you have not yet done it (or if it has changed).

To configure the code generation in the SysML diagram

1. Select the element you want to generate:

   • In the open SysML diagram. If you do not select any particular element in the diagram, the entire diagram view is selected as the generation input.

   • In the Containment tree.
2. Do one of the following:
   1. In the diagram toolbar, click the Configure Target button. 
   2. From the selected element's shortcut menu, select Software Code Generation and click Configure Target.
      

3. In the open Generator Details dialog, specify the needed SPO configurations.
   
   

4. (optional) Specify the download location if you want the results saved on your local file system. The generated files will be downloaded to the folder named after the Configuration name.
5. Click the OK button.

If the operation you selected (for example FMU Target Build) requires some other operations to be run beforehand, you will have to configure those operations in the next dialogs that will be opened automatically. The whole will constitute your “Target Configuration”.

Once the end of the configuration process is reached, i.e. you have fully configured your target, under the Configuration package you will find : 

1. The Generator Configurations package: this is where classes are created to save common properties of generators (parameters especially)
   
2. The Target Configurations package: this is where packages are created to store the flow of a target. Within this package,  classes are created to save specific properties for each SPO (download options, input, and generator mapping). 

Executing the code generator

To execute the code generator

1. Select the element you want to generate
   
   • In the open SysML diagram. If you do not select any particular element in the diagram, the entire diagram view is selected as the generation input.
   • In the containment tree.
2. Do one of the following:
   
   • In the diagram toolbar, click the Generate Target button and choose Generate Target.
     
     
   • From the selected element's shortcut menu, select Software Code Generation and click Generate Target.
3. All the operations you configured previously will be launched one after the other.
   
   • If you clicked on Generate Target, the operations will be launched only if it has not yet been launched or if an element has changed.
   • If you clicked on Full Generate Target, all the operations will be launched, regardless of a previous execution.

To edit configuration properties

1. In the Containment tree, right-click a Class element of the needed configuration.
2. In the shortcut menu, click Software Code Generation and select Edit Configuration.
3. In the open Generation Configuration dialog, make your changes.
4. Click OK.

You can deactivate the SPO you do not need.

To deactivate the SPO

1. In the main menu, click Options > Environment. The Environment Options dialog opens.
2. In the dialog, go to CATIA Software Producer Client > Operations.
3. Select the needed operation and click the Change activation status button.

You can switch projects (or even shut down your computer, saving your work first) while waiting for the generation result as it is running on the cloud and as the widget keeps the ids of the cloud assets in the record files located in <local workspace path>\etc\operations\spoRecordFile.json (you have access to it if you need it for the debugging purpose for example). When you come back, another dialog will tell you that operations were running while you were away and will propose you inspect the result and download it.

In the Software Producer Log panel, you can see the messages of the running SPO.

This information is saved in the log file next to your project files. To open the log file location quickly, in the Software Producer Logs window, click the Show Log File button. Each project has its own log file.

A log file for general Software Producer messages not related to a specific project is stored next to the modeling tool log file.

At the bottom right corner of the modeling tool, in the progress bar, you can see whether the SPO is running. After the SPO is completed, the notification is displayed showing the status of the generation.

When an SPO produces a report, the plugin reads it and opens it in a Validation Result window if any element has a diagnostic associated.

A diagnostic is associated with a rule consisting of a severity, message, and source.

You can navigate to the source in the Containment tree.  If you need to show more details concerning the rule or open the full report, right-click the appropriate lines of the table.

You can turn off the Validation Results window's opening after the SPO produces a report.

To turn the validation report off

1. In the modeling tool main menu, click Options and select Project.
2. Set the Show Validation Report property to false.

The full set of code you need to generate to cover your target is composed of at least a component and a target-specific part. Component part is relative to the behavior of your application (such as State Machine) whereas the target-specific part is relative to the architecture of your application (such as IBD). In other words, target specific is the binder and the link between the component and the target. As one does not go without the other, this is why at the end of the IBD generation, a dialog will ask you if you want the applicative code to be automatically generated if you have not yet done it (or if it has changed).

Once the full set of code has been generated, you can launch a build SPO by clicking on the Build button.

When you click a Build button, a dialog opens, wherein you need to specify the target and the available parameters (if there are any).

The code is downloaded to your file system following a specific folder hierarchy:

• esp_workspace¹
  • <componentA_name>[_<targetX_name>]
    • src
    • bin²
  • <componentB_name>[_<targetX_name>]
    • src
    • bin
• etc
  • backup³
  • logs
    • softwareProducer.log⁴

1. You can change the root of the local workspace path in the project options.
2. A bin folder is created only if the related component is the main component for the build.
3. By default, a backup of your downloaded files is saved in this folder so that in case something wrong happens with the download of new files, you can still reach your previous files. You can disable this option in the Project Options dialog.
4. Log files are rotated by size and date so that you might see multiple log files here.

The roundtrip action is a feature available for State Machines and Opaque Behaviors. Using the roundtrip action, you can add the modification you made in the code in between BEG_USER_CODE / END_USER_CODE tags (in files commonly named <ComponentName>_usr.c), back into the model and synchronize the file on the workspace on the cloud.

The following commands are available from the diagrams toolbar or from the shortcut menu of the supported elements in the Containment tree:

Associating Source Code Management repository to model

The following features are related to software governance:

• Source Code Management (SCM) repository association with the model.
• Generation results commit to the SCM.

To associate an SCM repository to the model

1. In the Containment tree, right-click the appropriate package.
2. In the shortcut menu, click Software Code Generation and select Associate SCM Repository.
3. In the open Associate SCM Repository dialog, choose the needed repository.
4. Click OK.

To commit the generation results to the SCM

1. Initiate the code generation.
2. In the open Operation Details dialog, Commit area, select the Commit to branch check-box.
3. Click the ... button.
4. Select the needed branch.
5. Click OK.

Sample project

The sample project Flashlight_SOP.mdzip is located in <modeling_tool_installation_directory>\samples\CATIA Software Producer. You can also open the Flashlight_SOP sample project from the modeling tool's Welcome screen, Samples tab.