| With software systems become more complex, the traceability from requirements to software products such as design models, codes, test cases has become more important. Requirements traceability is an effective way to control software development; it can maintain software development work on consistency. It is the key way to realize the software requirements management and to improve software quality.In the existed traceability technology, static traceability technology is the most widely used. Occasionally some requirements traceability tools have been developed, but these tools are hard to maintain, and when software requirements are changed, the effectiveness of requirements would be undermined. Dynamic requirements traceability is an automated traceability technology to build the relationship between requirements and software products. This paper will introduce ontology to the requirements traceability; propose an automatic matching method from requirements to codes. We build Requirements Ontology and Code Ontology, and then, realize the traceability through the mapping between the two ontologies.The main contents of this paper are:â‘ Build Requirements Ontology and Code Ontology, through analyzing and studying the characteristics of requirements and code. Analyze the decomposition process of requirements and the relationship between requirements and requirements; give the description of the Code Ontology and internal relations of Code Ontology;â‘¡Study the mapping rules between Requirements Ontology and Code Ontology, and propose two mapping methods of Requirements Ontology and Code Ontology based on similarity calculation: the mapping method based on WorldNet English Dictionary;the conceptual similarity calculation based on attribute;â‘¢Design and develop the prototype of the requirements traceability technology based on Ontology, verify the feasibility and effectiveness through experiment. Experimental results show that the proposed method provides an effective method for dynamic traceability technology; it has guiding significance for requirements change impact analysis and has a positive effect for the management of software requirements. |