You can import tabular data from MS Excel or other spreadsheet using the Comma-separated Values (CSV) file format to:
CSV files store tabular data in plain text format delimited by comma, tab, or semicolon. The first line of the CSV file described mapping of CSV text values to ReqView attributes or traceability links. The conversion of CSV text to attribute values depends on the attribute type as follows:
int
— text is an integer value, e.g., “123”.bool
— text is a boolean value, i.e., “TRUE” / “FALSE”, “YES” / “NO”, or “1” / “0”.string
— text is a string value.date
real
— text is a floating point value, e.g., “3.14”.enum
xhtml
— text is a string value. If the value is wrapped by HTML tag <html>
then rich text formatting is preserved, otherwise it is HTML escaped. For instance, value “Hello” is imported as “<p>Hello</p>” and value “<html><body><p>Hello</p></body></html>” is imported as “<p>Hello</p>”.To import new document objects from a CSV file into the current ReqView document, click File, mouseover Import, mouseover CSV File, and select whether you want to import new objects Add Before, Add After or Add As Children of the selected object.
CSV import will preserve the tree hierarchy of imported document objects, heading of document sections, text description of requirements, attribute values, and outgoing traceability links leading to existing objects. You can import incoming traceability links leading from existing objects to imported objects later, see Update Documents.
Imported CSVs files should contain the following columns:
level
— import hierarchy levels of imported objects (integer). If not provided, then CSV rows are imported as a flat list.heading
— import section headings displayed in the Description column.text
— import text descriptions displayed in the Description column.No CSV column can have name id
as ReqView assigns unique IDs to all imported objects automatically.
Note: If ReqView does not create new document objects or creates empty document objects then double check if the CSV header contains correct IDs of ReqView attributes. For instance, if your CSV file contains column “Description” it is ignored by the importer. You need to split this column to columns “heading” storing section headings and “text” storing requirement description.
Example: Import a CSV file to create new users needs in a specific section of the NEEDS document based on the User Stories Specification Template.
In MS Excel, change column names in the first row to match the IDs of ReqView internal attributes level, heading, text, and custom attributes asAn, iWant, soThat, and status.
In MS Excel, click File, click Save a Copy, and select CSV UTF-8 (Comma delimited) (*.csv) file type (available in the latest Excel versions) or Unicode Text (*.txt) file type (available in Excel 2016 and older versions).
In ReqView, open the NEEDS document and select a section for placing the imported objects. Click File, mouseover Import, mouseover CSV File, and select Add As Children. Finally, choose the CSV (or TXT) file created in the previous step.
To update attributes or outgoing traceability links of existing ReqView document objects from a CSV file, click File, mouseover Import, mouseover CSV File, and select Update Document.
Imported CSV files should contain should contain the first line with the following columns:
id
— match identifier of an existing document object to be updated.heading
— update section headings displayed in the Description column.text
— update text descriptions displayed in the Description column.Only the column id
is mandatory. If it stores an empty value then the row is imported as a new object at the end of the document.
You can import values of custom attributes for selected document objects from a CSV file, which should contain a column storing document object ID and one column per each updated custom attribute.
Example: Import a CSV file to update values of custom attribute status to “PASSED” for document objects TEST-10, TEST-20, and TEST-30, but do not change the status of other document objects.
In a text editor create a CSV file with the following content:
"id";"status""TEST-10";"PASSED""TEST-20";"PASSED""TEST-30";"PASSED"
In ReqView, open the document TESTS, then click File, mouseover Import, mouseover CSV File, and select Update Document. Finally, choose the CSV file.
Note: If ReqView does not update the document objects then double check if the CSV header contains correct IDs of ReqView attributes. For instance, if your CSV file contains column “Description”, which is ignored by the importer, then split this column to columns “heading” storing section headings and “text” storing requirement description.
You can import a batch of traceability links from a CSV file. The CSV file should contain a column storing document object ID and one column per each traceability link type. The values of the traceability link columns should store in each row a list of outgoing links for the given object.
Example: Import a CSV file to update verification links leading from test cases stored in the TESTS document to SW requirements stored in the SRS document.
In MS Excel, change column names in the first row to “id” and “verification”. For each updated test case, create a row, set test case ID in the first column, and list linked SW requirements in the second column:
In MS Excel, click File, click Save a Copy, and select CSV UTF-8 (Comma delimited) (*.csv) file type (available in the latest Excel versions) or Unicode Text (*.txt) file type (available in Excel 2016 and older versions).
In ReqView, open the TESTS document, then click File, mouseover Import, mouseover CSV File, and select Update Document. Finally, choose the CSV (or TXT) file created in the previous step.
Note: The CSV importer will remove for the imported document objects all existing verification links, which are not listed in the CSV file.
To edit attributes or outgoing traceability links for selected document objects in Excel:
Example: Recover verification traceability links from test cases in the TESTS document to SW requirements in the SRS document due to renumbering of SW requirement IDs (using a document template).
Save original IDs of the SRS document:
Duplicate the SRS document:
Export verification links from the TESTS document to CSV file TESTS.csv, see Customize CSV Export.
In Excel, redirect verification links from the TESTS document to point to the SRS-new document instead of the SRS document:
Open CSV files SRS-new.csv and TESTS.csv as separate sheets in one application window.
Select the verification column on the TESTS sheet, click Data, click Text to Columns, select Delimited, check Comma as a delimiter in the Convert Text to Colums Wizard.
For each verification column in the TESTS sheet, insert a new column replacing original SRS IDs by new SRS-new IDs using XLOOKUP Excel function matching the IDs in the id and origId in the SRS-new sheet: =XLOOKUP(TEXT(TESTS!B16,"0"),'SRS-new'!$B2:$B185,'SRS-new'!$A2:$A185,"")
.
Join new columns in the TESTS sheet to one column using TEXTJOIN Excel function: =TEXTJOIN(",",TRUE,L16:T16)
.
Change heading of the joined verification column to “verification” and remove all other columns except the column “id” in the TESTS sheet.
Save TESTS sheet to CSV file TESTS-fixed.csv
In ReqView, update the TESTS document from the CSV file TESTS-fixed.csv.