 |
| Requirements Traceability Matrix Template in Excel |
Download Free Requirements Traceability Matrix Template in Excel
Introduction to Requirements Traceability
In software development, a traceability matrix (TM) is a document, usually in the form of a table, used to assist in determining the completeness of a relationship by correlating any two baselined documents using a many-to-many relationship comparison. It is often used with high-level requirements (these often consist of marketing requirements) and detailed requirements of the product to the matching parts of high-level design, detailed design, test plan, and test cases.
A requirements traceability matrix may be used to check if the current project requirements are being met, and to help in the creation of a request for proposal, software requirements specification, various deliverable documents, and project plan tasks.
Common usage is to take the identifier for each of the items of one document and place them in the left column. The identifiers for the other document are placed across the top row. When an item in the left column is related to an item across the top, a mark is placed in the intersecting cell. The number of relationships are added up for each row and each column. This value indicates the mapping of the two items. Zero values indicate that no relationship exists. It must be determined if a relationship must be made. Large values imply that the relationship is too complex and should be simplified.
To ease the creation of traceability matrices, it is advisable to add the relationships to the source documents for both backward traceability and forward traceability. That way, when an item is changed in one baselined document, it is easy to see what needs to be changed in the other.
Instructions For Completing This Document-Requirements Traceability Matrix Template:
1-Complete the Project Name, C/I/O, Project Manager Name, and Project Description fields
2-For each issue identified, complete the following:
- ID: A unique ID number used to identify the traceability item in the requirements traceability matrix.
- Associated ID(s): This column should contain the ID of any associated utilities used for requirements tracking such as a repository, pipeline document, etc.
- Technical Assumption(s) or Customer Need(s): This column should be populated with a description of the technical assumption or customer need linked to the functional requirement.
- Functional Requirement: This column should be populated with a description of the functional requirement.
- Status: This column should be populated with the current status of the functional requirement.
- Architectural/Design Document: This column should be populated with a description of the architectural/design document linked to the functional requirement.
- Technical Specification: This column should be populated with a description of the technical specification linked to the functional requirement.
- System Component(s): This column should be populated with a description of the system component(s) linked to the functional requirement.
- Software Module(s): This column should be populated with a description of the software module(s) linked to the functional requirement.
- Test Case Number: This column should be populated with the test case number linked to the functional requirement.
- Tested In: This column should be populated with the module that the functional requirement has been tested in.
- Implemented In: This column should be populated with the module that the functional requirement has been implemented in.
- Verification: This column should be populated with a description of the verification document linked to the functional requirement.
- Additional Comments: This column should be populated with any additional comments
Download also:
Post a Comment