Product requirements prioritization approaches identify the most valuable requirements according to customer value, requirements risk, volatility, cost or other market parameters. However, it is still a challenge in Value-Based Engineering to manage the requirement values for incrementing the product value. The analysis of the product value requires a better understanding of interdependencies among various artifacts of the software development lifecycle, particularly, requires to get a better understanding of how the value chain is preserved from the problem space to the solution space. In this position paper our aim is to study the feasibility of using traceability as the backbone to preserve the value chain between the prioritized product requirements and the product architecture. We propose traceability semantics to address this aim. Some initial findings from our research are presented.