Holarch

SysML v2 Projects

Import and Export ReqIF (SysML v2)

ReqIF files from DOORS, Polarion, Jama, codebeamer and other requirements tools import as SysML v2 requirements on Model → Import and Export, and the requirements export back as ReqIF with their identifiers.

Import

  • Drop a .reqif or .reqifz file on the box, or open it from Import… on the Requirements page or Import ReqIF… in ⌘K / Ctrl+K. One ReqIF file per import.
  • Each requirement becomes a requirement with its text as the doc, its number as the short name and its attributes as attribute values. Requirement types become requirement definitions, enumerations become enumeration definitions, and chapter headings become packages with the chapter number.
  • Relations become derivations (derived from), refinements (refines) or dependencies. Satisfies and verified by between two requirements become dependencies; the table says why.
  • The ReqIF panel shows the counts and whether the SysML v2 text checks without problems. Under Short names from, choose the Foreign ID (the number people see in the source tool) or the ReqIF identifier. Under Relation types, choose what each relation type becomes; the preview is computed again.
  • Tables become text lines, lists become lines starting with a dash, and formatting is dropped; these requirements are listed as Approximated. Images and embedded objects are not imported; the table names each requirement that had one. Download Report saves the list as CSV.
  • Click Import 1 Package. The file becomes one package; a single Undo takes back the whole import.

Import again

  • Import a newer copy of the same file into the same project: requirements keep their element ids, so diagrams, satisfy and verify links and reviews stay attached. The preview row says how many changed, were added or are missing from it.
  • Requirements missing from the new file are kept. Tick Remove the N requirements missing from this file to move them to the Trash.
  • Elements you added in Holarch (parts, verification cases, links) are kept. A requirement changed only in Holarch keeps your change. A requirement changed both here and in the file takes the file's text; the earlier text stays in History.

Export

  • Under Export, choose a package or the whole model and ReqIF (.reqif) or ReqIF archive (.reqifz). Export… → Requirements (ReqIF) on the Database or Requirements page exports the listed requirements.
  • The file holds the requirements with their short name, name, doc, status and attribute values, the package hierarchy as the specification, and derive, refine and dependency relationships. Requirements imported from ReqIF keep their original identifiers and types, so the source tool updates them instead of adding copies.
  • Calculated attribute values are written as text. Satisfy and verify links are not in the file: ReqIF has no parts or verification cases.