Blog Posts bpmn-1-x Process Analysis Process Modeling

The Link Between Requirements Traceability and Defect Reporting

Blog: Business Analyst Learnings Blog

Software requirements and the decisions made relating to them, carry through from the point of initial conception of the solution till the product is working in the live environment. One of the key decisions that need to made during software projects is the priority of requirements. The priorities of critical requirements can be preserved by ensuring these requirements are linked to their test cases as the project evolves from one phase to another.

The importance of requirements traceability becomes more apparent further down the line when defects are identified during the course of software testing. Resolving all software defects discovered during testing can be quite challenging (almost an ideal) given the limited time, funding and other key factors that affect software implementation. Since it may not be possible or even realistic to fix all software defects, it becomes important to prioritize the defects that are to be fixed based on their severity levels (Their impact on the system and the business as a whole). 

Defect reporting should draw on the priority of individual requirements and not be done in isolation. Testers should also not assign severity levels and priorities to defects until the importance and priorities of underlying requirements are well understood. Requirements Traceability can help to ensure that:

  1. Key requirements are addressed and not left on the table when the product is finally released. 
  2. Severity levels are only assigned after due consideration of the priorities of the requirements to which they are linked and
  3. Software defects that are out of scope of consideration, for example, those that arise based on a user’s unstated expectation of how the system should work and not how it actually works.

Requirements Traceability Matrices (RTMs) are especially useful here and can be used for tracing user requirements and linking them to their test cases. They can be used by testers to ensure that the defects recorded per test case are linked to their originating requirements in order to assess the effects of fixing the defect or postponing the fix till a later release. 

Picture Attribution: “Chain” by Salvatore Vuono/

Leave a Comment

Get the BPI Web Feed

Using the HTML code below, you can display this Business Process Incubator page content with the current filter and sorting inside your web site for FREE.

Copy/Paste this code in your website html code:

<iframe src="" frameborder="0" scrolling="auto" width="100%" height="700">

Customizing your BPI Web Feed

You can click on the Get the BPI Web Feed link on any of our page to create the best possible feed for your site. Here are a few tips to customize your BPI Web Feed.

Customizing the Content Filter
On any page, you can add filter criteria using the MORE FILTERS interface:

Customizing the Content Filter

Customizing the Content Sorting
Clicking on the sorting options will also change the way your BPI Web Feed will be ordered on your site:

Get the BPI Web Feed

Some integration examples