Requirements Import/Export Mapping (using the example of DOORS NG)
medini allows to exchange requirements with various Requirements Management Systems (RMS). These integrations require a mapping file to be defined for the specific RMS configuration - which can be different even for individual documents/modules/trackers... So the mapping file have an important role to play for the successful connection and should be configured with care, ideally by the company's power user(s). As this is not always trivial, here are some hints how to effectively define the mapping file. We will use DOORS NG as an example, but most steps are very similar for other RMS. Note that some RMS (like DOORS classic) do not support all features (e.g. only import). In addition, please see also the help contents in the Ansys medini™ analyze User Guide (links should work if you have medini running with help opened): Integrations > Exchange of Requirements with RMS > PTC Integrity Integration > Mapping definition To start, it is recommended to correctly configure an import, as it avoids creating wrong data in the RMS. Start medini in DEBUG mode (command line parameter "mediniAnalyze.exe -debug"; dev mode also works, but best stay with debug mode), as this provides a helpful feature for initial set-up described further down Right-click a requirements folder (Properties > Base > Contents is set to "Safety Goals and Requirements") and select Import > Requirements from DOORS NG In the Server Settings window, for URI paste the link to the DOORS NG module. You can get it via the context menu of your module "Share Link to Artifact...", or you just drag&drop the Artifact (in this picture "TestModule1") into the URI field.Fill in Username and Password as if you access DOORS NG and click "Next >". In the mapping selection window you can see that an example mapping file was created. It is saved in the project workspace under config/doorsng/doorsng.mapping. Open it in an external editor (best with XML highlighting, e.g. Notepad++) Still in the same window, click "Details". When in debug mode, you will see "Dump types to clipboard". This function will get in contact with DOORS NG and get all available types information for the module defined on the previous page. Paste the information also in your external editor. It looks similar to this one: Use this information for your mapping: The type labels are the "mappedValue"s to be used in ... (could also be "Information" or "Heading" as per example above). You can also use the name labels as an alternative The field labels are the "mappedAttribute"s to be used for representation of the medini property - i.e. the assigned field name on DOORS NG side The readOnly value indicates if a field cannot be written (if it is true), i.e. it cannot be exported from medini. Adjust the doorsng.mapping file to your DOORS NG configuration. Note that the default mapping will likely not work with your setup, as it is not tailored to your configuration. With the example type information from above it could look like this: <?xml version="1.0" encoding="UTF-8"?>
If you save the mapping and click "Next >" you should hopefully get an error-free import. If not, try to correct the mapping in the external editor and re-do the import in medini with going "< Back" and "Next >" without closing the window. Afterwards, try the export of an existing medini Requirements model similarly. You will not need the debug mode anymore. In case you think that your configuration in DNG is not completely suitable for the exchange with medini, please speak to your requirements management team or directly access the types definition in the admin area of DNG (if you have access), here for each DNG project: There are more features available for mapping files, e.g. Scripting in Requirements Management (RM) Mapping Files Changed direction of relations If you have further suggestions and comments helpful to others, please feel free to post them in this thread. For concrete issues with your RMS configuration, consider opening a support request via "Help > Contact Support" in medini. Happy analyzing!
