Data sources Tab

This tab defines the list of analyzed files.

Overview

It is unnecessary to define which document creates a requirement (statement) or which document covers a requirement (coverage). The same document can contain both statements and coverages.

Commands

File list

  • File list list: Double click on a file opens it with the default editor.
  • Add File button : adds a new file to the list. The supported formats are described in Input formats page.
  • Add Folder button : adds all file of the folder that matches the name pattern. The pattern can use: ? for a single character, * character matches zero or more characters of a name component without crossing directory boundaries, { , , } lists several sequences, [-] matches a character range, \ escapes a special character. For example: source*, s??rce.cpp, *.{h,cpp}, *test*\\*.java, [A-Z,a-z]ource.cpp. The folder can be either static, then the files are immediately found and inserted, or dynamic, then the file are found at runtime.
  • Delete button : removes the selected file from the list
  • Open button : opens the selected file with system editor
  • Path button : opens the file or folder browser to update the path

Data source information

The selected files can be edited.

  • Statement retrieval from list: defines how statement are found in source documents, see Extraction Modes. The file icon is decorated to show the parsing mode.
  • Relative path check box: The value may be the full path or simply the file name. In the latter case, the software searches the file in the same directory that the coverage file. The check-box switches between the relative and the absolute paths.
  • File ID text: identifier that is combined with the heading number to built automatically a REQUIREMENT ID. Only available for Heading mode. The file ID is automatically computed with 3 characters.
  • Edit button: allows to manually update the file ID. This allows to customize how the file is referenced in coverage, for example <RFP§1.1>. The customized file ID can be 8 characters long.

Extraction Modes

Syntax mode

Extraction mode Syntax extracts the requirements using the syntax defined in the Statement tab, see Statement Tab.

Icon: Syntax Icon

Note

The Syntax mode is available for the EXCEL format. In Syntax mode, the EXCEL file is read in the same way as a text file, with each cell being regarded as a paragraph. This combination is rarely used in favor of the Database mode.

Heading mode

Extraction mode Heading extracts the requirements from the heading numbers. ID are automatically generated.

Icon: Heading Icon

Syntax+Full mode

Extraction mode Syntax+Full extracts the requirements using the syntax and all other paragraphs of the document or data source. This mode allows to get the full text for verification and/or coverage.

Icon: Document Icon

Database mode

Extraction mode Database extracts the requirements directly for the table. For an Excel file, the format of [Reqchecker] report is used: a header line with columns names followed by data lines.

Column list is : DOCUMENT, ID, POSITION, TEXT, TITLE, VERSION, COVERAGE DOC, COVERAGE POS, COVERAGE STATUS, COVERAGE VERSION.

Only the column ID is mandatory, other columns are optional. The column order does not matter.

It requires to fill in the columns with the final value of the text, title etc. You must not use read syntax tags such as << in this Excel file.

Other columns can be extracted too if a corresponding custom tag has been created with the same tag as the EXCEL column name, see custom tags definition. They appear in the Matrix tab of the Coverage Matrix (in blue columns) if you check the Extended coverage matrix option .

Icon: Database Icon

This mode can be used if you provide an EXCEL file with the required column names and content provided upstream: * or imported by you; * or exported by Reqchecker via the matrix. The software does not make the difference.

None mode

Extraction mode None extracts no requirement. The document is only used for coverage definitions.