Exporting artifacts from a requirements project into ReqIF files

You can export artifacts, modules, and folders from a requirements project into a ReqIF (Requirements Interchange Format) file by creating a definition and then exporting the artifacts. The artifacts that are exported are determined by the content in the definition.

Before you begin

To export data to a ReqIF file (.reqif or .reqifz), you must have the Export ReqIF permission and you must have a ReqIF definition in the ReqIF editor. To create a ReqIF definition, you must have the Manage ReqIF permission.

About this task

You can export several types of data from a requirements project to a ReqIF file, including these types:
  • Attribute definitions
  • Data types
  • Textual artifacts
  • Graphical artifacts
  • Diagram artifacts
  • Artifact types
  • Modules
  • Collections
  • Links to other artifacts in the RM project
  • Link types
  • Folders
  • Folder hierarchy
  • View column information
The following types of data cannot be exported:
  • Tags
  • Comments
  • View filtering information
  • Reviews
  • Audit History
  • Links to artifacts in applications that are integrated by using OSLC, such as IBM® Engineering Workflow Management (EWM) and IBM Engineering Test Management (ETM)
If you are exporting artifacts to IBM Engineering Requirements Management DOORS® (DOORS), the following data types are not supported. These data types are from the Requirements Management (RM) application for the IBM Engineering Lifecycle Management (ELM).
  • Full rich-text formatting.
  • Graphical artifacts, such as business process diagrams, use case diagrams, and wireframes.
  • Requirements that include embedded collections.

If you use modules to capture information about your project requirements, you can export specific artifacts in the module. Start by creating a view of the module that contains only those artifacts that you want to export; then, during the export process, you can add the new view to the definition. If the view is a non-personal, single-module view (non-module shared), only the artifacts in the view are exported to the ReqIF output package.


  1. On the Administration menu , click Manage Project Properties.
    Note: If configuration management is enabled for your project, on the Administration menu, click Manage Component Properties.
  2. Click the ReqIF tab.
  3. Click New Definition.
  4. Type a name for the definition. If necessary, specify other information, such as a description or whether to include links or folders in the export.
  5. Click Add Artifact or Add Module and follow the prompts to add the artifacts to include in the export. When you add a module, you can optionally choose a shared view to describe which artifacts and attributes are exported from the module, as defined by the view's filter and columns respectively.
    Note: You can add shared views and shared module views to a definition for export, however, doing so exports the view query and not the artifacts in the view.
  6. After you finish adding artifacts, click Save. The definition is displayed in the ReqIF Definitions section.
  7. To start the export, click the pencil icon (Menu icon ) that is next to the ReqIF definition, and then click Export.
  8. When the export is complete, click Download to save the export to a file on your computer. The downloaded ReqIF file has the (.reqifz) extension. To see the data that was exported, click Show Report.

What to do next

You can download packages and view report information in the ReqIF Manager window. Click the action icons in the ReqIF Files section of the editor.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki