Press Release Software Testing

Using requirements coverage matrices

Collection and analysis of requirements to a product or to its single feature is an integral stage of any project. This article can be useful for those who repeatedly face the necessity of requirements coverage and preparation of test cases. I will tell you about the usage of Requirements Coverage Matrices and we’ll discuss key advantages of documenting requirements and possible formats of their storage.


It is worth mentioning that the use of Requirements Coverage Matrices and the choice of a storage format depend mainly on the nature of the project and its capacities.

The main conditions, which make usage of a Requirements Coverage Matrix on a project appropriate, are as follows:

  1. The project budget allows time for creating a Requirements Coverage Matrix (or matrices).
  2. Requirements to a product or to a new task are quite substantial and suggest a number of changes.
  3. Requirements provided by the customer are not complete and do not take into account all the nuances of the product implementation or its specifics, thus demanding a detailed analysis and involvement of a team on both the developers’ and the customer’s side.
  4. Initial requirements are not documented and formulated in a clear way, which makes it necessary to collect and document these requirements. 
  5. Mandatory coverage of all requirements with test cases.

  SO WHAT IS A REQUIREMENTS COVERAGE MATRIX AND HOW CAN IT BE USEFUL?

Requirements Coverage Matrix is a table that contains a list of documented requirements to a product/task and links to the corresponding test scenarios. It is used for validation of requirements coverage with test cases.

There may be situations where requirements are not initially documented or where initial requirements are not final and need an additional study together with the story team and agreement with the customer.