Reqtify

General

Name: Reqtify
Tool Provider:

Dassault Systèmes
Supported Standards: DO178C DO330 EN50128 IEC61508 ISO26262
Description:

A requirements tracing tool

Use Cases:

Content

Identifications

Reqtify 2021x

Description:

Release of Reqtify from November 2020
Environment:

Reqtify is supported on Windows 7(SP1)/8/8.1/10.

As Reqtify is a 32-bit software, it is supported for both 32-bit and 64-bit operating systems.

Use Cases

Run all features of the model

Description:

This use case enables to test all the features contained in Reqtify tool.

Alternatively, you could test only selected features of the tool to fit your needs.
Safety-Impact: yes
Inputs:
  • API Exports:

    Output from the API

    The outputs from the API are the artifacts generated by commands using the API, e.g. the generated DOORS artifacts
  • API input:

    Input for the API
  • ASCII input File:

    Textual file as input for the converter
  • ASCII intermediate File:

    Intermediate file from the input converter (textual)
  • Binary input file:

    Binary file as input for converter
  • Filter:

    The filters
  • Inputs:

    The inputs from a tool, e.g. .doc, .xls, .mdl
  • Mark file:

    Additional information for marking elements, stored in a sperate file
  • Model:

    The model of the requirements (in Reqtify Memory) into which the requirements are loaded
  • OTScript source file:

    OTScript source code
  • Presentation Model:

    The computed information for the presentation
  • Project Configurations:

    The Reqtify project configuration
  • Report Model:

    The report models
  • Report Template:

    Template for reports
  • Types:

    The types of analysis
  • User Interface:

    Display Reqtify information to the user interactively
  • XML Document:

    Any XML document to work on
  • XML input File:

    XML file as input for converters
  • XML intermediate File:

    Intermediate file from the input converter (XML)
Outputs:
  • ASCII Export File:

    ASCII export
  • ASCII intermediate File:

    Intermediate file from the input converter (textual)
  • Filter:

    The filters
  • Mark file:

    Additional information for marking elements, stored in a sperate file
  • Model:

    The model of the requirements (in Reqtify Memory) into which the requirements are loaded
  • Project Configurations:

    The Reqtify project configuration
  • Report Model:

    The report models
  • Report Template:

    Template for reports
  • Report output file:

    Report generated from Reqtify

    Reports contain following information

    - Tracability

    - Analysis results

    - Impact analysis

    grouped in customizable blocks of

    - tables

    - nested feature

    - heading

    - text
  • Types:

    The types of analysis
  • User Interface:

    Display Reqtify information to the user interactively
  • XML Export File:

    XML exported file
  • XML intermediate File:

    Intermediate file from the input converter (XML)
Features:
  • Couplings:

    These are some of the different kinds of couplings:

    Code Couplings allow to parse different programming languages.

    Design Couplings allow to connect to different design tools.

    Office Couplings allow to connect to different office tools.

    Requirements Couplings allow to connect to different RM tools.

    Remote Couplings allow to connect to cooperation tools like SVN

    Project Couplings allow to connect to different project management and support tools.

    UML Couplings allow to connect to different modeling tools.
  • Main UI:

    Main user interfaces of Reqtify
  • Main functions:

    Main functions of Reqtify Capture data from different engineering tools
  • Plugins:

    Plugins are additional feature that can be added as plugins to Reqtify
  • Support regular expressions:

    Regular expressions are described in Reqtify customization.
Potential errors:
# Error Safety-Impact Mitigations for detections/avoidance Final detection/avoidance probability
1 [Couplings] Connection Profile Not Defined

The connection profile contains the information to connect to the tool (user name, password,...)

and the user has not defined this profile.

 impact_true HIGH
2 [Couplings] Wrong Coupling behaviour

Error when parsing different progamming languages or when trying to connect to different design/RM/project management/UML/office tools

 impact_true HIGH
3 [Main UI] Wrong output from main user interfaces
impact_true HIGH
4 [Main functions] Wrong output from Main functions

Error when capturing data from different engineering tools

 impact_true HIGH
5 [Plugins] Wrong behaviour from Plugins

Plugins do not behave as expected

 impact_true HIGH
6 [Support regular expressions] Reqtify does not support Regular Expressions correctly

Capture all errors with regular expressions

 impact_true HIGH

Qualifications

QKit for Reqtify

Description:

The QKit is a standard Validas QKit using QST and TAU that automatically executes the qualification tests in the user environment.

The qualification kit for Reqtify has been developed using the model based approach and was validated

One use case is considered:

Run all features of the model - consists of all the features contained in Reqtify tool.

Details on the planning and tests are removed for confidentiality reasons.
Qualfication method:

VALIDAS_QKIT
Identifications:
Use Cases:

Test suites and test cases

Test suite for reqtify

Description:

This testsuite contains tests for use cases described in the model
Flags: Has Requirements Based Tests , Has Negative Tests , Has Boundary Tests , Has Equivalence Tests , Has Error Guessing Tests
Comment:

[details are removed for confidentiality reasons]
# tests: 316
Errors:
  • Reqtify does not support Regular Expressions correctly

Mitigations

# Mitigation Detection/Avoidance probability Detected/Avoided errors
1 [Check] Requirements Coverage By Code

During the development of the product all the developed code has to be traced to requriements (e.g. DO178C). If this is achieved and all requirements are tested, any tracing related error in Reqtify would have been detected.

HIGH
  • Wrong Coupling behaviour
2 [Check] Capture Check

For each type of captured information using regular expressions check in the user interface of Reqtify, if the traceability information is correctly captured.

 HIGH
  • Wrong Coupling behaviour
  • Wrong output from Main functions
3 [Check] Manual Review of Export

Perform a manual review of the artifacts generated by this feature, e.g. the exported QC database

 HIGH
  • Wrong Coupling behaviour
  • Wrong behaviour from Plugins
4 [Check] Interactivly Work with the Connected Tool

Use the navigation for interactive work and verify that it is on the expected place

For example if an artifact is selected (double-click) in Reqtify, the user will determine if it not correctly

navigated in the connected tool.

 HIGH
  • Wrong Coupling behaviour
5 [Check] Other Verification

Verify the generated product of the features using other verification e.g. a test that would detect errors from the corresponding feature of Reqtify

 HIGH
  • Wrong Coupling behaviour
  • Wrong behaviour from Plugins
6 [Check] Control File Integrity

For each file, try to open it using dedicated tool

By trying to open the file using dedicated tool (Word, Excel, Acrobat, ...) the integrity of the file can be controlled.

 HIGH
  • Wrong Coupling behaviour
7 [Check] Check XML file content

For each XML file, check the contents of the file

As most of Reqtify files are XML files, they can be opened in a Text or XML Editor and verified manually.

 HIGH
  • Wrong behaviour from Plugins
  • Wrong output from Main functions
  • Wrong output from main user interfaces
8 [Check] Use the UI to detect the Error

During the use case Tagger plugin in Reqtify inconsitent tags is detected

 HIGH
  • Wrong behaviour from Plugins
  • Wrong output from Main functions
9 [Check] Visible Defect Detection

User Works directly with the tool and will detect obvious errors like damaged text, etc

- disabled button

- disabled menu items

- wrong display


Comment:

The user will easily see the defects since they are on the UI element

HIGH
  • Wrong output from main user interfaces
10 [Restriction] Establish Connection Profile

Define and Test Connection Profile

Before using the connection to the connected tool (DOORS,HTTP,Bugzilla,...) a profile has to be setup and tested.

 HIGH
  • Connection Profile Not Defined