When a change is proposed, the traceability infrastructure provides the ability to trace back to the rationale behind impacted requirements so that current decisions can be informed ones, and to trace forward to artifacts such as design documents, code, and test cases in order to more completely understand how to implement the change and to identify and mitigate its possible side effects. Unnecessary traces lead to a maintenance nightmare, while too little traceability provides inadequate support for the change process [41]. Therefore links should be carefully established to provide necessary support for change analysis activities.