Modular Development and Code Generation

Incremental Code Generation
Incremental code generation is available for Simulink subsystems which contain a TargetLink Function block. In a team of developers, each member can work on a subsystem individually and just generate code for that. TargetLink^® performs the necessary consistency checks when building the overall application from all the parts.

Benefits
Incremental code generation has several advantages:

• Code for individual subsystems in a model can be tested, reviewed, and frozen, while development in other subsystems continues.
• Team members can work independently on different subsystems.
• Code generation time can be significantly reduced by generating code only for subsystems that have been modified.

Model Referencing Support
TargetLink supports model referencing. Functionalities can be flexibly partitioned into several model files, versioned separately, and developed on a modular basis. Parts of models can be simulated separately and implemented individually by means of incremental code generation.

Simplified Software Integration
TargetLink code from separate (incrementally generated) subsystems and (referenced) models can be easily integrated and tested by means of code generation from the Data Dictionary. Variables with global relevance that are shared by separate models and subsystems are specified and generated from the Data Dictionary.

Code Generation Straight from the Data Dictionary
The Data Dictionary supports the generation of both code and A2L files for Data Dictionary variables independently of their use in TargetLink models. Variables with global relevance that are shared between different models, subsystems and referenced models should be specified in the Data Dictionary and implemented from there. Generating code files with definitions and declarations, and also A2L files for variables from the Data Dictionary, makes software integration and software integration testing easy. Moreover, it is possible to create all the calibration parameters for an entire ECU project in one file, no matter whether they are from legacy code or used in TargetLink models.