Goknil [6] system requirements cannot be static, they are prone to change and new requirements emerge frequently. New and/or modified requirements are integrated with existing ones and adaptations are made to the system architecture and source code. 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 managing changes 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 across software development artifacts. It is the ability to link requirements back to stakeholder motivations and route them to corresponding design artifacts, code, and test cases. When changes to software system requirements are proposed, the impact of those changes on other requirements, design elements, and source code should be traced in order to determine which parts of the software system need to be changed.