Import and export

Import from ReqIF

You bring in data from DOORS Next and other tools via ReqIF. In the directory, choose Import and the format ReqIF / ReqIFz (from DOORS Next or the RMM). Accepted are .reqif, .reqifz and .zip.

1. Choose the file. Mirador first only reads it and shows what it contains.
2. Choose the set under which the elements are created (Import under set) and the Attributes to import.
3. Import. A Dry run exists only for the Excel round-trip; what the file contains, Mirador shows as soon as it has been read.

The id from the source is kept as the external key. Images and embedded files come along, comments from the source become comment threads. Whatever Mirador cannot read in the file, it skips and lists among the notices in the result. How attributes are mapped is defined by a mapping file of your operations team.

A file may be up to 200 MB.

Export

Export in the directory writes the table as

• CSV,
• Excel workbook,
• Excel round-trip – a workbook you can edit and read back in, or
• ReqIF – a .reqifz to pass on, see below.

The traceability board and the hits of a filter can be exported as CSV or Excel.

Export as ReqIF

Export → ReqIF in the directory writes a .reqifz – an archive with the ReqIF document, the images and the attachments. In the Export as ReqIF window you choose:

The export takes the state of the view: from a baseline its frozen state, with a variant selected, only what applies in it. The table filters do not apply to the file; only the checked rows the table currently shows count as selected.

The file carries the outline, types, attributes with formatted text, images, attachments and the relationships whose ends are both in the file (but not those of a module itself). Types and attributes are named as your operations team’s mapping file names them for the import. Before Mirador hands the file out, it validates it against ReqIF; if it fails, no file is produced.

Mirador builds the file in the background and shows the progress; Cancel export stops it. Afterwards the window shows what the file holds and what it lacks, such as relationships that lead out of it. Download saves it. By default it stays available for 30 minutes; closing the window discards it.

Anyone who can read the specification can export it. Each person can run at most two exports at a time.

Mirador’s own import reads a file from this export back in – up to 200 MB, like any import file.

Export profiles

A profile defines per specification what goes out to a recipient. New profile creates one (requires the EDITOR role); Edit and Delete are for its owner while they hold the EDITOR role – for a public one, also the project administrator. Nobody changes a profile in an archived specification.

Editing in Excel and back

The Excel round-trip suits cases where many requirements are to be edited at once – or by someone who does not work in Mirador.

1. Choose Export → Excel round-trip. You decide which rows (the level or your selection) and which columns (those of the view, or all attributes) go into the workbook, and whether rich text appears as plain text or HTML. An empty template is possible too.
2. Edit the workbook. Leave the columns UUID (do not edit) and Revision (do not edit) unchanged – Mirador recognises every row by its UUID.
3. In the directory, choose Import with the format Excel round-trip (workbook from the export). The workbook is always read into the project that is currently open.

When reading it in, you decide:

A workbook may have up to 20,000 rows.

What does not exist

• Comments in the ReqIF export – they stay in Mirador.
• ReqIF from the traceability board; its export offers CSV and Excel.
• An import of an Excel export from DOORS. Use the ReqIF export of DOORS instead.