You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Prerequisites

To work with the Data Markings and Classification Plugin, the following software should be installed:

  • MagicDraw or a similar modeling tool.
  • Variability Core Plugin for the modeling tool.
  • Data Markings and Classification Plugin for the modeling tool.

    If you open a project containing Data Markings without the Data Markings and Classification Plugin installed on the tool, a warning message is displayed informing you to install the plugin first. The plugin must be installed to open the project and see the plugin-specific markings allowing you to differentiate sensitive and non-sensitive data.

Sample

You can also review a project sample provided with the installation, found at:

  • <tool_installation_directory>\samples\Data Markings\secret aircraft model.mdzip
    The sample is a practical example built using the Data Markings Profile, Variability Profile, and the DoD Data Marking Categories.

Library

You can use ready-made DoD Data Marking Categories via the DoD data markings model library. The library is automatically loaded, along with the Data Markings Profile and the Variability Profile, once you use the DoD Data Marking Categories. The library is located at:

  • <tool_installation_directory>\modelLibraries\DoD data markings.mdzip

Profiles

In order to create and use Data Markings, the Data Markings Profile and the Variability Profile must be used. They are imported automatically once you create a new Data Marking Category or use DoD Data Marking Categories. You can also import the profile files manually, which can be found at:

  • <tool_installation_directory>\profiles\Data Markings Profile.mdzip
    The profile file contains both the Data Markings Profile and the Variability Profile needed to create and use Data Markings.

  • <tool_installation_directory>\profiles\Variability Profile.mdzip

API

Data Marking features are also accessible through our standard API. For instance, you can use the enum literal’s sync element (i.e., constraint) to manipulate constraints (Data Markings), retrieve lists of constrained elements (elements with added Data Markings) or lists of constraints added to an element, as well as add new constrained elements. Note that these operations do not consider filters such as Sensitive Element Types or Ignored Data Marking Categories.


Related pages: