Skip to main content

ReqIF Export & Import (Advanced)

NirmIQ supports the ReqIF (Requirements Interchange Format) standard for interoperability with enterprise requirements management tools.

Advanced Feature

ReqIF export/import is designed for advanced users who need to integrate with enterprise tools like IBM DOORS, Jama Connect, PTC Integrity, Siemens Polarion, and other requirements management systems.

For simpler imports, see Manual Import (Excel/JSON).

What is ReqIF?​

ReqIF (Requirements Interchange Format) is an international standard for exchanging requirements between different tools and organizations.

Key Facts​

  • Standard Body: Object Management Group (OMG)
  • Current Version: ReqIF 1.2 (2016)
  • Format: XML-based
  • Purpose: Vendor-neutral requirements exchange
  • Industry Adoption: Automotive, Aerospace, Defense, Medical Devices

Why ReqIF Matters​

Problem ReqIF Solves: Different organizations use different requirements tools (IBM DOORS, Jama, Polarion, etc.). When working together, they need a standard way to exchange requirements without losing critical data like hierarchy, attributes, and traceability.

Before ReqIF:

  • Manual copy-paste between tools ❌
  • Loss of hierarchy and metadata ❌
  • Hours of reformatting work ❌
  • High error rates ❌

With ReqIF:

  • Automated import/export ✅
  • Preserves structure and data ✅
  • Industry standard format ✅
  • Tool-agnostic exchange ✅

Official Standards & Resources​

OMG ReqIF Specification​

Official Specification:

Industry Standards​

  • DIN SPEC 99200 - German standard for ReqIF interpretation (2025)
  • ASAM ReqIF - Automotive industry guidelines
  • ProSTEP iViP - Automotive working group recommendations

Tool Support​

ReqIF is supported by major requirements management tools:

ToolVendorReqIF Support
IBM DOORS NextIBMFull support
Jama ConnectJama SoftwareFull support
PTC IntegrityPTCFull support
PolarionSiemensFull support
CodebeamerPTCFull support
DOORS ClassicIBMPlugin available
Visure RequirementsVisureFull support
ReqViewReqViewFull support
NirmIQGannet Solutions✅ Full support

When to Use ReqIF​

✅ Use ReqIF Export/Import When:​

Enterprise Integration:

  • 🏢 Exchanging requirements with customers using different tools
  • 🏢 Migrating from IBM DOORS, Jama, or other enterprise tools
  • 🏢 Supplier collaboration (automotive OEMs → Tier 1 → Tier 2)
  • 🏢 Regulatory submissions requiring tool-neutral formats

Compliance & Standards:

  • 📋 ISO 26262 (Automotive functional safety)
  • 📋 DO-178C (Aviation software)
  • 📋 IEC 62304 (Medical device software)
  • 📋 ASPICE (Automotive SPICE)
  • 📋 Defense contracts requiring DOORS compliance

Complex Projects:

  • 🔧 10,000+ requirements with deep hierarchy
  • 🔧 Multi-vendor development programs
  • 🔧 Long-term archival (20+ year lifecycle)
  • 🔧 Audit trail requirements

❌ Don't Use ReqIF When:​

Simple Use Cases:

  • Small projects (< 100 requirements)
  • Internal-only projects
  • No tool interoperability needed
  • No regulatory requirements

Better Alternatives:

  • Excel - Simple sharing, data analysis
  • JSON - IntelliSE backups, API integration
  • PDF - Read-only documentation
  • AI Import - Converting Word documents

Export to ReqIF​

How to Export​

  1. Open your project in IntelliSE
  2. Click Project → Export → Export to ReqIF (.reqif)
  3. File downloads automatically as {ProjectName}_Requirements_{Date}.reqif

What's Included in Export​

Requirements Data:

  • ✅ Requirement ID (custom_id)
  • ✅ Requirement text
  • ✅ Type classification
  • ✅ Status (Draft, Active, Approved, etc.)
  • ✅ Version number
  • ✅ Jira links (if configured)

Structure:

  • ✅ Complete hierarchy (parent-child relationships)
  • ✅ Specification tree structure
  • ✅ Requirement ordering

Metadata:

  • ✅ Project name and description
  • ✅ Export timestamp
  • ✅ Tool identification (IntelliSE)
  • ✅ ReqIF version (1.2)

ReqIF File Structure​

IntelliSE generates valid ReqIF 1.2 XML:

<?xml version="1.0" encoding="UTF-8"?>
<REQ-IF xmlns="http://www.omg.org/spec/ReqIF/20110401/reqif.xsd">
  <THE-HEADER>
    <REQ-IF-HEADER IDENTIFIER="...">
      <COMMENT>Exported from IntelliSE - Project Name</COMMENT>
      <CREATION-TIME>2025-10-10T12:00:00Z</CREATION-TIME>
      <REPOSITORY-ID>IntelliSE</REPOSITORY-ID>
      <REQ-IF-TOOL-ID>IntelliSE Requirements Management</REQ-IF-TOOL-ID>
      <REQ-IF-VERSION>1.2</REQ-IF-VERSION>
      <TITLE>Project Name</TITLE>
    </REQ-IF-HEADER>
  </THE-HEADER>
  <CORE-CONTENT>
    <REQ-IF-CONTENT>
      <DATATYPES>
        <!-- String type definitions -->
      </DATATYPES>
      <SPEC-TYPES>
        <!-- Requirement type definitions -->
      </SPEC-TYPES>
      <SPEC-OBJECTS>
        <!-- Individual requirements -->
      </SPEC-OBJECTS>
      <SPECIFICATIONS>
        <!-- Hierarchy structure -->
      </SPECIFICATIONS>
    </REQ-IF-CONTENT>
  </CORE-CONTENT>
</REQ-IF>

Compatibility​

Tool Compatibility:

  • ✅ IBM DOORS Next (validated)
  • ✅ Jama Connect (validated)
  • ✅ PTC Integrity (validated)
  • ✅ Polarion (validated)
  • ✅ Any OMG ReqIF 1.2 compliant tool

File Extensions:

  • .reqif - Standard XML file
  • .reqifz - Zipped file (for embedded objects) - future support

Import from ReqIF​

How to Import​

  1. Open your project in IntelliSE
  2. Click Project → Import Requirements...
  3. Select ReqIF (.reqif) format
  4. Choose your .reqif file
  5. Wait for import to complete
  6. Review imported requirements

Supported Import Sources​

Validated Tools:

  • ✅ IBM DOORS Classic (via export)
  • ✅ IBM DOORS Next
  • ✅ Jama Connect
  • ✅ PTC Integrity
  • ✅ Siemens Polarion
  • ✅ IntelliSE (round-trip)

Requirements:

  • Must be valid ReqIF 1.0, 1.1, or 1.2 XML
  • Must include SPEC-OBJECTS section
  • Must include SPECIFICATIONS for hierarchy
  • Attributes must include text content

Import Process​

Step 1: Parsing

  • Validates XML structure
  • Extracts requirements (SPEC-OBJECTS)
  • Parses hierarchy (SPEC-HIERARCHY)
  • Maps attributes to IntelliSE fields

Step 2: Mapping

  • Custom ID: Extracted from attributes or LONG-NAME
  • Text: Longest text attribute or LONG-NAME
  • Type: Mapped from requirement type
  • Status: Detected from status attributes
  • Version: Parsed from version attributes

Step 3: Import

  • Creates requirements in correct order (parents first)
  • Maintains hierarchy relationships
  • Assigns IntelliSE IDs
  • Links to parent requirements

Import Limitations​

Current Limitations:

  • ⚠️ Rich text (XHTML) converted to plain text
  • ⚠️ Custom attributes not in IntelliSE schema are skipped
  • ⚠️ Embedded objects (.reqifz) not yet supported
  • ⚠️ Complex relations simplified to parent-child only

Data Loss Prevention:

  • All critical requirement data preserved
  • Hierarchy fully maintained
  • IDs, text, status, version retained
  • Unknown attributes logged to console

Use Cases & Examples​

Use Case 1: Automotive Supplier​

Scenario: Tier 1 supplier receives requirements from OEM

Customer (OEM):

  • Uses IBM DOORS Next
  • Exports 2,000 requirements as ReqIF
  • Sends to supplier

Supplier (You):

  • Uses IntelliSE
  • Imports ReqIF file
  • Works on requirements in IntelliSE
  • Exports updated ReqIF back to customer

Benefits:

  • ✅ No tool conversion costs
  • ✅ Maintains OEM's requirement structure
  • ✅ Audit trail preserved
  • ✅ ISO 26262 / ASPICE compliant

Use Case 2: Defense Contractor​

Scenario: Government contract requires DOORS compatibility

Government:

  • Mandates IBM DOORS format
  • Requires ReqIF deliverables
  • Audits traceability

Contractor (You):

  • Uses IntelliSE (lower cost than DOORS)
  • Exports to ReqIF for deliverables
  • Maintains compliance

Benefits:

  • ✅ Meet contract requirements
  • ✅ Save 90% on tool licensing
  • ✅ Standard-compliant format
  • ✅ Audit-ready deliverables

Use Case 3: Medical Device​

Scenario: FDA submission requires tool-neutral format

Requirement:

  • IEC 62304 compliance
  • 21 CFR Part 11 (FDA)
  • Tool-neutral archival
  • 30-year retention

Solution:

  • Export to ReqIF for archival
  • Standard XML format (readable for decades)
  • No vendor lock-in
  • Meets regulatory requirements

Use Case 4: Multi-Tool Environment​

Scenario: Large organization with mixed tools

Organization:

  • Systems engineering: Jama Connect
  • Software: IntelliSE
  • Hardware: Polarion
  • Integration: PTC Integrity

Workflow:

  1. Systems exports from Jama (ReqIF)
  2. Software imports to IntelliSE
  3. Software exports to IntelliSE (ReqIF)
  4. Hardware imports to Polarion
  5. Complete traceability across tools

Best Practices​

For Export​

✅ Do:

  • Export regularly for backup
  • Test imports in target tool before sharing
  • Include descriptive project names
  • Document export date and purpose
  • Validate hierarchy before export

❌ Don't:

  • Export incomplete or draft requirements
  • Use special characters in requirement IDs
  • Export without reviewing data first
  • Forget to communicate with receiving party

For Import​

✅ Do:

  • Backup your project before importing
  • Review ReqIF file in XML editor first
  • Import to test project first
  • Verify hierarchy after import
  • Check for data loss
  • Map custom fields to IntelliSE schema

❌ Don't:

  • Import directly to production project
  • Assume all data will import perfectly
  • Skip validation
  • Import without reviewing source tool's export

Troubleshooting​

Export Issues​

Problem: Export file is very large Solution:

  • Large files are normal for 1000+ requirements
  • Use .reqifz format (future) for compression
  • Consider exporting in batches

Problem: Target tool rejects import Solution:

  • Verify tool supports ReqIF 1.2
  • Check tool-specific import settings
  • Validate XML structure
  • Contact target tool support

Import Issues​

Problem: "Invalid ReqIF file" error Solution:

  • Validate XML structure
  • Check for REQ-IF root element
  • Ensure file is not corrupted
  • Try opening in XML editor

Problem: Hierarchy not preserved Solution:

  • Check source file has SPECIFICATIONS section
  • Verify SPEC-HIERARCHY elements present
  • Some tools export flat structures
  • May need manual re-hierarchization

Problem: Missing requirement text Solution:

  • Check source tool's export settings
  • Ensure text attributes are exported
  • Some tools require explicit attribute selection
  • Re-export with full attributes

Problem: Import very slow Solution:

  • Large files take time (sequential API calls)
  • 1000 requirements ≈ 2-3 minutes
  • Be patient, don't refresh browser
  • Consider splitting into batches

Technical Details​

Attribute Mapping​

IntelliSE maps ReqIF attributes to internal fields:

IntelliSE FieldReqIF Source
custom_idLONG-NAME or ID attribute
textText attribute (longest)
typeSPEC-OBJECT-TYPE or Type attribute
statusStatus attribute or inferred
versionVersion attribute or default 1.0
parent_custom_idSPEC-HIERARCHY structure

Validation​

On Export:

  • Validates all requirements have IDs
  • Checks hierarchy integrity
  • Generates unique ReqIF identifiers
  • Creates valid XML structure

On Import:

  • Validates XML against ReqIF schema
  • Checks required elements present
  • Verifies attribute structure
  • Detects circular references

Comparison with Other Formats​

FeatureReqIFExcelJSONAI Import
Hierarchy✅ Perfect⚠️ Manual✅ Perfect✅ AI-detected
Metadata✅ Rich⚠️ Limited✅ Full⚠️ Extracted
Tool Support✅ Enterprise✅ Universal❌ IntelliSE only❌ N/A
Readability❌ XML✅ Easy⚠️ TechnicalN/A
Standards✅ OMG standard❌ No standard❌ No standard❌ Proprietary
Use CaseEnterprise integrationSimple sharingBackupsDocument conversion

Choose ReqIF for: Enterprise tool interoperability Choose Excel for: Simple sharing and analysis Choose JSON for: IntelliSE backups and API Choose AI Import for: Converting Word documents

Regulatory & Compliance​

Standards Supported​

ReqIF is required/recommended by:

  • ISO 26262 - Automotive functional safety
  • ASPICE - Automotive SPICE process improvement
  • DO-178C - Aviation software certification
  • IEC 62304 - Medical device software lifecycle
  • CMMI - Capability Maturity Model Integration
  • FDA 21 CFR Part 11 - Electronic records (via standard format)

Audit Trail​

ReqIF provides:

  • ✅ Tool-neutral evidence
  • ✅ Timestamp of export
  • ✅ Source tool identification
  • ✅ Requirement versioning
  • ✅ Hierarchy documentation
  • ✅ Complete traceability

Long-Term Archival​

Benefits:

  • ✅ XML is human-readable
  • ✅ No proprietary formats
  • ✅ Future-proof (30+ year readability)
  • ✅ Standard won't become obsolete
  • ✅ Can parse without special tools

FAQ​

General Questions​

Q: Is ReqIF support free in NirmIQ? A: Yes! ReqIF export/import is included in all paid tiers (Basic and above). It's an advanced feature but not restricted by tier.

Q: Do I need special training to use ReqIF? A: Not for basic export/import. For advanced mapping and custom attributes, understanding the ReqIF specification helps.

Q: Can I use ReqIF for backup? A: Yes, but JSON is simpler for IntelliSE-to-IntelliSE backups. Use ReqIF when you need tool-neutral archival.

Compatibility Questions​

Q: Will ReqIF work with IBM DOORS Classic? A: Yes, but DOORS Classic requires the ReqIF export plugin. DOORS Next has native support.

Q: Can I round-trip (export → import) without data loss? A: Yes! IntelliSE → ReqIF → IntelliSE preserves all data perfectly.

Q: Does ReqIF work with Excel tools? A: No. Excel is not ReqIF-compatible. Use Excel export/import for Excel workflows.

Technical Questions​

Q: What ReqIF version does IntelliSE support? A: Export: ReqIF 1.2. Import: ReqIF 1.0, 1.1, and 1.2.

Q: Can I customize attribute mapping? A: Currently automatic. Custom mapping planned for future release.

Q: Does IntelliSE support .reqifz (zipped)? A: Not yet. Currently supports .reqif (XML) only. .reqifz support coming soon.

Support & Resources​

Get Help​

Report Issues​

If you encounter ReqIF import/export issues:

  1. Check file is valid XML
  2. Verify ReqIF version compatibility
  3. Test with small sample first
  4. Report issue with sample file

Integration Guides​

Looking to link IntelliSE requirements to MATLAB/Simulink models?

See: MATLAB/Simulink Integration Guide

What you'll learn:

  • Export ReqIF from IntelliSE
  • Import into MATLAB Requirements Toolbox
  • Link requirements to Simulink model elements
  • Create verification test cases
  • Generate traceability matrices for ISO 26262, DO-178C, IEC 62304

Perfect for: Automotive, Aerospace, Medical Device development with model-based design.

Last Updated: October 2025 ReqIF Version: 1.2 NirmIQ Version: 2.0+