Traceability Matrix is a set of rules to trace the deliverable to the requirement and vice versa.
Traceability Matrix is used to
verify and validate system specifications,
ensure that all final deliverable documents are included in the system specification, such as process models and data models,
Improve the quality of a system by identifying requirements that are not addressed by configuration items during design and code reviews and by identifying extra configuration items that are not required. Examples of configuration items are software modules and hardware devices,
provide input to change requests and future project plans when missing requirements are identified,
Provide a guide for system and acceptance test plans of what needs to be tested.
Taking the time to cross-reference each requirement to a deliverable ensures that a deliverable is consistent with the customer and system requirements. A requirement that cannot be mapped to a deliverable is an indication that something is missing from the deliverable. Likewise, a deliverable that cannot be traced back to a requirement may mean the system is delivering more than required.
Useful traceability matrices examples:
Functional specification to requirements document: It shows that each requirement (obtained from a preliminary requirements statement provided by the customer or produced in the Concept Definition stage) has been covered in an appropriate section of the functional specification.
Design specification to functional specification verifies that each function has been covered in the design.
System test plan to functional specification ensures you have identified a test case or test scenario for each process and each requirement in the functional specification.
Although the construction and maintenance of traceability matrices may be time-consuming, they are a quick reference during verification and validation tasks.
please give me a clear idea on Treaceability Matrix.
Tracability Matrix is the main document for testing dept. It gives a clear information about testing status like, Howmany senarios we wrote, under one senarion howmany test cases written,how many executed, howmany to be excuted, even no of bugs module wise we can maitain in this.
It's again depends upon the organaisational standard template.
To identify whether all the test cases written and the requirement documents are in synch, the Traceability matrix or coverage matrix is used. Once the tester write the test cases it will entered in the matrix sheet. It will then reviwed either by the Reviewer or Test Lead and validate that all the specification mentioned in the Requirement document are covered and splitted in to all possible scenarios in the format of test case.
In general, the Traceability matrix will have the following fields:
1. Requirement ID
2. Requirement received Date
3. Module Name
4. Responsible Tester Name
5. Reviewer Name
6. Test case name
7. Build / Version number
8. Associated Defects
9. Reviewer Comments.
The traceability matrix can either be maintained in the excel sheet or in any of the specified tools.
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.