Goknil [6] the requirements of a system cannot be static, they are subject to change and new requirements emerge frequently. New and/or modified requirements are integrated with existing ones, and adaptations to the system architecture and source code are made. The process of integrating new/changed requirements and adaptations into the software system is called change management. The size and complexity of software systems make change management expensive and time-consuming. To reduce the cost of changes, it is important to apply change management as early as possible in the software development cycle. Requirements traceability is considered crucial in change management to establish and maintain consistency among software development artifacts. This is the ability to relate requirements to stakeholder justifications and pass them to corresponding design artifacts, code, and test cases. When changes to software system requirements are proposed, the impact of these changes on other requirements, design elements, and source code must be traced to determine which parts of the software system to modify.