# Requirements Coverage

{include file="nav.tpl"}

## General

This feature allows to map a coverage of user or system requirements by test cases. Navigate via link "Requirement Specification" in main screen.

## Requirements Specification

Requirements are grouped by "Requirements Specification" which is related to Product.
TestLink doesn't support versions for both Requirements Specification and Requirements itself. So, version of document should be added after a Specification Title. An user can add simple description or notes to Scope field.

Total count of all Requirements serves for evaluation Req. coverage in case that not all requirements are added to TestLink. The value n/a means that current count of requirements is used for metrics.

E.g. SRS includes 200 requirements but only 50 are added in TestLink. Test coverage is 25% (if all these added requirements will be tested).

## Requirements

Click on title of a created Requirements Specification. You can create, edit, delete or import requirements for the document. Each requirement has title, scope and status. Status should be "Normal" or "Not testable". Not testable requirements are not counted to metrics. This parameter should be used for both unimplemented features and wrong designed requirements.

You can create new test cases for requirements by using multi action with checked requirements within the specification screen. These Test Cases are created into component and category 'TODO'. Title and Scope are copied to these test cases.