Comparison of data exchange methods in requirements management

You can exchange or transfer data in or out of the Requirements Management (RM) application in several ways. The methods of data exchange are described in the following table. For more information about a method, click the method name.
Table 1. Comparison of data exchange methods in the RM application
Method Description
CSV, XLS, XLSX import and export You can import and export CSV files or spreadsheets in Microsoft Excel and Office Open XML format. Imports and exports support:
  • Embedded artifacts, including graphical artifacts such as sketches, storyboards, and diagrams.
  • Links, including Open Services for Lifecycle Collaboration (OSLC) links.
  • Round trips, in which you update existing artifacts. When you import CSV files or spreadsheets, you can update existing artifacts that match imported content, or you can create new artifacts.

Before you import data, you can modify a CSV file by using a third-party tool. Imported files must be encoded in UTF-8.

ReqIF import and export You can use ReqIF import and export to exchange requirement artifacts and associated metadata between software tools, including IBM Engineering Requirements Management DOORS (DOORS) products. The ReqIF specification provides a means for tools that implement this specification to exchange requirements information. You can use ReqIF import and export for round trips, in which you update existing exported artifacts.

For a list of supported and restricted data, see Importing artifacts from ReqIF files to a requirements project or component and Exporting artifacts from a requirements project or component into ReqIF files.

Migration package import You can use migration package import to migrate data from DOORS.

For more information, click the link in the left column.

Project templates You can copy project templates to other servers; for example, from a staging server to a production server. Project templates are useful for creating requirements projects. You can create or modify a template by using another template. Project templates are also useful for sharing custom project templates that are applicable to other repositories.

For a list of items that can be included in or excluded from a template, see Creating templates.

  • A project template cannot be used as a project backup because artifact history, comments, reviews, and access controls are not preserved.
  • A project template does not preserve the links that are outside of the artifacts in the template.
Project properties import You can import the project properties from a requirements management project into another requirements management project.
Project baselines You can use project baselines for these purposes:
  • To capture an entire requirement project at a specific moment in time, including artifacts, folder trees, and the public tag list.
  • To define scope and manage change by using collections that are captured in baselines.
  • To track development progress and milestones.
  • To view specific versions of artifacts, with intact links and comments, that were captured at specific point in time.
Restriction: Project baselines cannot be used to transfer data outside of a project.
Database backup and restore Typically, only a product administrator can back up and restore the database.
Backing up and restoring the database is useful for these purposes:
  • To mitigate data loss by backing up the database and indexed files.
  • For serviceability, including these tasks:
Backup is assumed to be at the level of the whole requirements management repository. Restore is assumed to be targeted to the same URI. To change the URI, you must rename the server.