Your SlideShare is downloading. ×

Features of Requirements Traceability Matrix

412
views

Published on

In today’s software development landscape, there is hardly any shortage of debates concerning the relative merits of practices, methods and certain techniques for design, analysis, and coding …

In today’s software development landscape, there is hardly any shortage of debates concerning the relative merits of practices, methods and certain techniques for design, analysis, and coding activities. One of the most talked about topic in this regard is the requirements traceability and the role is plays in defining and executing systems.


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
412
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Features of Requirements Traceability MatrixIn today’s software development landscape, there is hardly any shortage of debates concerning therelative merits of practices, methods and certain techniques for design, analysis, and coding activities.One of the most talked about topic in this regard is the requirements traceability and the role is plays indefining and executing systems. Though discussions regarding the same might have been going fordecades, and the tools are going to evolve to assist both more and less artifact traceability, there can bevery little doubt about one aspect, i.e. the requirements traceability has been an efficient technique insome development methodologies, especially for those systems where software failure is no option.Experience has made it evident that the capacity to trace requirements artifacts through the stages ofspecification architecture, design, implementation and testing is an essential factor in ensuring a qualitysoftware execution. The ability to track these relationships and assess the influence when change takesplace is common to several modern, high-assurance software processes, especially in the critical missionactivities.Simply put, a traceability relationship is an association between two project elements. More precisely, arequirements traceability matrix is set up by relating the requirements with the work products thatsatisfy the. The tests are related with the requirements on which they are based and the product istested to cater the requirement. In requirements traceability matrix the relationship of driver to satisfiercan be one-to-one, one-to-many, many-to-one, or many-to-many.Today service providers specializing in application lifecycle management and requirements managementsolutions offers help with requirements traceability matrix. It allows you to choose a relation first, anddepending on that, you are able to select personalized filters for every entity that are associated withthe relation that imposes a level of filtration of the linked records. The records of one entity are thenhighlighted in a row while the others are shown in a column.In addition to that, above the filtration imposed you can also select the records that you would like todisplay. The options that are available are includes:  All with the orphans highlighted i.e. having no linked records using this selected relation  Only orphans  Records that have linked records onlyFurthermore, the requirements traceability matrix offers a complete visual representation of the entityitems that are related to one another by the means of the relationships. Utilizing this matrix end usersare able to set up new, edit and delete relationships by double clicking on the cell that appears in theintersection of the two entity items.Related Links - JIRA Integration & Agile Methodology