Several data sources

Requirement information can be extracted from several data sources:
  • Microsoft Office 2007 Word, Excel, Powerpoint
  • Microsoft Office 97 Word, Excel
  • Open Office WRITER
  • PDF
  • Comments in software source files C, C++, C#, Java, JavaScript, XML etc.
  • directly from Microsoft EXCEL worksheet
  • an API is provided to add your own data source

Extract requirements with 3 methods

Three methods are available for requirement extraction. 

  • Syntax: Reqchecker uses simple wildcards or powerful regular expressions to find and extract requirements information. The statement is declared by enclosing markers. For example <REQ_0123> declares the requirement REQ_0123.
  • Heading: the requirements can be automatically created from heading numbers of MS Word or Adobe PDF document. The ID looks like FIL1§1.1.
  • Database: the information are directly read from the table.

Declare coverages everywhere

Coverages can be declared everywhere in documents using a simple syntax with markers, for example <<REQ_0123>>.
A coverage can be partial: it must be covered several time to be fully covered. For example a need like "All reports must display the company logo." shall be covered partially by each test of each report.
If can be also deleted, uncovered, not applicable, or inconsistent (orphans, multiple statements etc).
A requirement coverage can be included in another requirement (node) or everywhere in a document (node leaf). This allows them to be chained on multiple levels.

Interactive matrix

The coverage matrix lists all statements and their coverages, custom attributes. The active links open the source documents at the right position. 

Impact analysis

Check propagation of all requirement changes by using the version management: change the input documents and Reqchecker™ shows where your documents shall be updated.
Every statement and coverage has a version. When the requirement is updated in a newer version, the statement remains inconsistent until it is updated too. The version can be manually changed or automatically computed from text numeric print (hash).

Custom tags

Manage your own attributes (tags) for the requirements as well for the coverage. 3 types are available: yes/no, text on one line or several lines and list of elements. Their values are extracted from statements and coverages and can be reviewed in coverage matrix.
Custom tags register information directly inside de document, e.g. #C for a coverage comment, #TODO for a reminder, #Type for a requirement type, #Status,  etc.

Eclipse Content Assistant

Eclipse content assistance: C++ and Java developers can use the Eclipse IDE content assistant (CTRL+SPACE) to select the requirement and insert coverage.


Graphical user interface and tooltips are available in English, French, German. The detailed online help is available in English.