Reqchecker 1.7 is ready

Automatic impact analysis

The software automatically creates a default version for each requirement. This version is available only if no explicit version is defined. The automatic version is a 6 characters length hash number. The hash is computed from the text and picture read from PDF and MS Word docx documents. The automatic version is not dependant from the following changes: case sensitive change, bullet modification, spaces.

Dynamic folders

The “Add Folder” button in “Data sources” tab now inserts either the files in batch mode, or lists the files at runtime. This works for folder and sub-folders. The advanced patterns allows filters like *.{cpp,h}.

Path update

The path of a file or a folder can be updated without changing other characteristics.

Regular expression conversion

When user switches from standard to advanced regular expression, the existing values are converted. Switch back to standard expression is not possible, then values are reset to default.

Java enum export

New export under Java enum format. This allows to reference requirements directly from Java language, for example as link in JavaDoc source code. (PRO version only)

Read comments for new languages

Read comments for new languages: Python (.py, .pyw), Windows and Linux script files (.bat, .sh), C include files (.inc). (PRO version only)

Bug fixed

Increased maximum length of requirement text. This allows to catch longer text, in particular for heading mode where paragraphs can be long.

(PRO version only) Fixed PDF reader: some cases of landscape page are now correctly read

(PRO version only) Fixed false differences presented in verification report in update mode when the text contains some unprintable characters

(PRO version only) Fixed verification report no more includes deleted requirements.

Reqchecker 1.6.0 is ready

Build 1343 May 2017

  • Leaf requirements : This new tag defines that the requirement is leaf. A leaf requirement is covered by default; it must not be explicitly covered. The default tag value is #Leaf and can be customized. Leaf requirement have a correct status in the reports. The status can be error if it is covered, has several statements etc. Example:

[REQ_02] The red light must be on if the sub-system raises an alert.

<<DSC_0012>> #Partial <<DSC_0013>> #Leaf

  • Statement from heading numbers is available for MS Word 97 documents
  • Management rate : the rate of requirement explicitly managed, excluding requirement with error. The coverage rate is the coverage rate excluding not applicable and not managed requirements. For example let 3 requirements covered, 1 explicitly not covered, 2 not applicable and 4 not yet managed, with a total of 10 requirements. The management rate is 60% (6/10) and the coverage rate is 75% (3/4).
  • Coverage rate can be detailed in percentage. The coverage rate is more accurate, especially if requirements are not unitary.

For example:

<<REQ_0040>> #Partial 13%

<<REQ_0040>> #Partial 30%

<<REQ_0040>> #Partial 40%

<<REQ_0040>> #NA 17%

  • Updated PDF report with new look and rates
  • Performance improvement about 20%
  • Graphical user interface and tooltips are available in German
  • Display §beginning for position found before the first encountered chapter in PDF or WORD documents.
  • (PRO version only) The text of custom tag without end marker stops at the end of line (previous behaviour) or when another tag if read. This allows to write all tags on the same line.
  • (PRO version only) Eclipse content assistance: C++ and Java developers can import the requirement definition and use the Eclipse IDE content assistant (CTRL+SPACE) to select the requirement and insert coverage.

  • (PRO version only) Standalone report : The links to source documents in Verification and Coverage Matrix report are relative if the document are stored in the same folder. In this case the report and the documents can be opened on another computer. New option “EXCEL Hyperlinks” generates EXCEL reports without hyperlinks to source documents.
  • (PRO version only) Verification report update : The verification report can be updated without losing the entered results. The new / updated / deleted requirements are merged, updated cells have yellow background and a comment with a visual comparison between old and new value. The RESULT column is updated too: “(added)” for new requirement, “(updated)” for modified requirements, “(deleted)” for deleted requirements. The merge work with both syntax and heading statement mode. Custom tag are included in comparison. Column can be moved, but column name in header must remain unchanged.


  • (PRO version only) Multiple value for list custom fields : The predefined list type custom tag accepts multiple values ​​separated by punctuation (comma, semi-colon, space, non-breaking space). Each value is checked to verify that it belongs to the value list declared in the .cover file. Example:
<DSL_0123> Title
#Category A, B
  • (PRO version only) Multiple statements are listed in the coverage matrix and highlighted in the verification report. This help to find and fix them.