REQUIREMENTS TRACEABILITY MATRIX
Printed From: One Stop Testing
Category: Quality Assurance @ OneStopTesting
Forum Name: Requirements and Design Documents @ OneStopTesting
Forum Discription: All those Artifacts generated in Requirement and Design Phases like Use Cases, SRS, Functional & Non-Functional Specefications, Check Lists, Design Documentations etc.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=63
Printed Date: 24Dec2024 at 2:42pm
Topic: REQUIREMENTS TRACEABILITY MATRIX
Posted By: merry
Subject: REQUIREMENTS TRACEABILITY MATRIX
Date Posted: 15Feb2007 at 4:37pm
|
REQUIREMENTS TRACEABILITY MATRIX A traceability matrix is created by associating requirements with the work products that satisfy them. Tests are associated with the requirements on which they are based and the product tested to meet the requirement.
Above is a simple traceability matrix structure. There can be more things included in a traceability matrix than shown. In traceability, the relationship of driver to satisfier can be one-to-one, one-to-many, many-to-one, or many-to-many. Traceability requires unique identifiers for each requirement and product. Numbers for products are established in a configuration management(CM) plan. Traceability ensures completeness, that all lower level requirements come from higher level requirements, and that all higher level requirements are allocated to lower level requirements. Traceability is also used to manage change and provides the basis for test planning. Sample Traceability MatrixA traceability matrix is a report from the requirements database or repository. The examples show tracing between user and system requirements. User requirement identifiers begin with "U" and system requirements with "S." Tracing S12 to its source makes it clear this requirement is erroneous: it must be eliminated, rewritten, or the traceability corrected. 
Traceability is not a panacea. For requirements tracing and resulting reports to work, the requirements must be of good quality. Requirements of poor quality transfer work to subsequent phases of the SDLC, increasing cost and schedule and creating disputes with the customer.
In addition to traceability matrices, other reports are necessary to manage requirements. What goes into each report depends on the information needs of those receiving the report(s). Determine their information needs and document the information that will be associated with the requirements in your requirements management plan for when you set up your requirements database or repository. http://www.jiludwig.com/Configuration_Management.html - |
