In this article

• Identify the Stencil used: Process, External Extractor, Data Store
• Update the "components:" section of the MTMT default mapping file

Permissions required

• N/A

Instructions

For this guide, we will use the following DFD as an example:

1. Identify the Element name and associated Stencil name being used in the DFD

1.1 Element name Mobile Client uses the Stencil Dynamics CRM Mobile:

1.2 Element name Public API v2 uses the Stencil Web API:

1.3 Element name Accounting PostgreSQL uses the Stencil Azure Database for PostgreSQL:

1.4 Element name Azure File Storage uses the Stencil Azure Storage:

2. Download the default mapping file for MTMT (mtmt_default_mapping_example.yaml) from Github

3.  Note the attributes used for mapping the components:

-label:

This is the Stencil name in MTMT and matches the component name in IriusRisk*

type: 

This is the IriusRisk Component found in the Property section when in diagramming view:

4. Identify which Stencils have a matching label

The current default mapping file has a mapping for [1.2], [1.3] and [1.4] but not for [1.1]:

 - label: Web API
   type: web-service

 - label: Azure Database for MySQL
   type: CD-MICROSOFT-AZURE-DB-MYSQL

 - label: Azure Storage
   type: azure-storage

5. Establish the required mapping for those not covered by the default mapping file

Assume the Mobile Client [1.1] is an android based client and this can be mapped to Dynamics CRM Mobile

5.1 Add the following component mapping:

- label: Dynamics CRM Mobile
  type: android-device-client

Note:

* There are some exceptions e.g. Web API stencil which imports the web-service IriusRisk Component (see type in section 3.), however there is currently not a matching component in IriusRisk.