Importing and exporting ReqIF files
Requirements Interchange Format (ReqIF) files are XML files that you can use to exchange requirements and associated metadata between requirements tools or requirements repositories. For example, you can exchange data between IBM® Rational® DOORS® and IBM Rational DOORS Next Generation. When the exchange is finished, a report is generated that shows the data that was imported or exported.
About this task
You can import or export data to and from a requirements project by using ReqIF (.reqif or .reqifz) files. Exporting and importing data back into the original requirements project is also supported. You can export data from a requirements project, to another requirements project. On making changes to the data, you can import the data back into the original requirements project. For example, you can export objects to a ReqIF file from Rational DOORS and then import that file into Rational DOORS Next Generation. You can change attribute values, export the artifacts to a ReqIF file, and then import that file back into Rational DOORS. If you import a ReqIF file into Rational DOORS Next Generation after you already imported or exported the data, the data is merged and updated.
If the ReqIF packages contains attributes and types associated with a workflow in Rational DOORS Next Generation, these associated attributes and types are supported during the export process of the package, but are ignored during the import process.
For information about supported and restricted data, see Importing artifacts from ReqIF files to a requirements project and Exporting artifacts from a requirements project into ReqIF files.
- For each module, the report displays attribute definitions, artifact types, and artifacts.
- The summary, data types, artifact types, links, and folder for a specific import or export of a ReqIF package are displayed at the root level.
- Artifact types are displayed at both the root level and the module level. Artifact types for the root level are specific to the ReqIF package and artifact types for the module level are specific to that module.
For information about moving the contents of a server, such as moving a pilot deployment to a production server or moving a production deployment to a different server, see Supported scenarios for using server rename. The server rename operation moves all existing projects and artifacts from one deployment to another. The operation does not support a selected project move function; that is, you cannot move only selected projects when you rename a server.