ReqIF Import

In addition to the JSON import, which is designed for AI-generated requirement catalogs, ETRM also supports ReqIF (Requirements Interchange Format) – the open, XML-based OMG exchange standard. ReqIF is used for data exchange by tools such as IBM DOORS Next Generation, Polarion, Jama Connect, and Codebeamer. If you're migrating from one of these tools, or just want to bring in existing data, export a .reqif file there and import it directly into a new ETRM project.

---

How to import a ReqIF file

1. Go to Projects → New Project.
2. In the "Import Project" card, choose "ReqIF (.reqif)" as the file format.
3. Select the target group and, optionally, a different project name.
4. Choose your .reqif file and start the import.

The newly created project is then available like any other ETRM project – including structure, requirements, and parent-child relationships.

---

What gets imported?

• Structure: Headings/chapters (SPEC-OBJECTs whose type indicates a pure outline level, e.g. "Heading" or "Chapter") become structure elements in ETRM.
• Requirements: All remaining SPEC-OBJECTs become requirements. The title and description text are taken from the standard's reserved ReqIF.Name and ReqIF.Text attributes; if either is missing, the first matching text attribute is used instead.
• Parent-child relationships: SPEC-RELATION entries are interpreted as parent-child links (the relation's source becomes the parent requirement, its target the child requirement).

---

Limitations of this first version

The ReqIF import deliberately doesn't cover the full breadth of the standard, to keep it simple to use:

• Only the first SPECIFICATION in a file is processed. If your file contains multiple specification documents, export them separately from the source system if needed.
• ReqIF export from ETRM is not provided – the import is a one-way street.
• Custom attributes (enumerations, number fields, date fields, etc.) are not imported – only the title, text, and the outline/relationship structure.
• Embedded images/objects within ReqIF requirements are not imported.
• Heading detection is heuristic, based on the type name. If an outline level is mistakenly imported as a requirement (or vice versa), you can correct this directly in the document after import.

Spot-check an imported project against the source file before continuing to work with it.

---

Tip: JSON import remains the recommended path when creating new requirement catalogs with AI assistance. Use the ReqIF import specifically for one-time migration of existing data from another requirements tool.