Traceability Record

Instructions (each tab of the tables could serve to keep traceability inside the sections. Also, this helps to show the history):
1. Substitute the logotype or name of the Company with the company's information.
2. Fill the information on the right table with the information about the project.
3. The Version History section includes a register of the changes on the template, and every change made to the format must be reviewed, approved, and registered in the table.
4. The traceability record and the research show four elements that must be in the traceability record:
a. Requisites elements.
i. Change request.
ii. Requirement Verification Results.
iii. Requirement Specification (Graphic Specification: Flowcharts, Use Cases Diagrams, Entity-Relationship Diagrams, Wireframes, Mockups, State Diagrams, Data Flow Diagrams, Gantt Charts, Activity Diagrams, Class Diagrams, etc.).
iv. Requirement Specification (Textual Specification: Software Requirement Specification, User Stories, Feature List, Requirements Traceability Matrix, Product Backlog, Vision Document, Functional Specification Document, Technical Specification Document, Interface Control Document, etc.).
b. Design elements.
i. Test Procedures Design.
ii. Test Case Design.
iii. Subsystem Design.
iv. Architectonic Design.
v. Software Components Design.
c. Construction elements.
i. Regression Test.
ii. Software Components.
iii. Unit Test.
iv. Integration Test.
d. Test elements.
i. Procedures.
ii. Test Cases.
iii. Test Result.