A data dictionary is a persistent repository of data that are relevant to your model. You can also use the base workspace to store design data that are used by your model during simulation. However, a data dictionary provides more capabilities.
The dictionary stores design data, which define parameters and signals, and include data that define the behavior of the model. The dictionary does not store simulation data, which are inputs or outputs of model simulation.
|Dictionary as data source||All entries in a dictionary are persistent. You do not need to reload data during development.|
|Explicit data-model linkage||You can define a data dictionary as the data source for a model. During model simulation and code generation, the model retrieves design data from the data dictionary.|
|Change tracking||When you modify an entry, its status is updated in the dictionary and stored as metadata that can be tracked. The dictionary also tracks who made the changes and when. You can also view or revert changes.|
|Entry comparison||Compare values of entries in two dictionaries.|
|Data grouping into reference dictionaries||Partition and organize data items into reference dictionaries.|
|Model-data dependency||Discover how entries are used in the model.|
|Store and partition reference data||Store and partition data that are relevant to a model, such as equipment specifications, but not used by the model during simulation.|
|Unified interface for defining data||Use the Model Explorer to work with design data in a dictionary.|
|Incremental update in memory||Improved performance and scalability with minimal footprint on memory.|
|Requirements traceability linking||Navigate from a data dictionary entry to a location in a requirements document.|
A Simulink® data dictionary is made up of three parts called sections.
Design Data: Contains the variables and data types that define parameters, signals, and design data that determine the behavior of the model. Design data created or imported in a dictionary are stored in this section.
This section can store only certain classes and data types. See Valid Design Data Classes for more information.
Configurations: Contains configuration
sets, which are objects of the
that determine how the model is configured during simulation. These
objects control attributes such as sample time and simulation start
When you store configuration sets in a data dictionary, you use configuration references to access the configuration sets. Models that are linked to a dictionary resolve configuration references to configuration sets in the dictionary. For more information about configuration references, see About Configuration References.
This section can also store variant configuration objects, which
belong to the
Simulink.VariantConfigurationData class. These objects store information
about variant configurations, active and default variant settings,
and definitions of the control variable associated with each configuration.
Other Data: Contains information that is relevant to your model but not used by the model during simulation. Use this section to store reference information such as data that describe physical equipment and processes that are represented by your model.
This section can store almost any built-in or custom class or data type. See Invalid Other Data Classes for more information.
|File Format||Import to Dictionary||Export from Dictionary|