{'fraction_non_alphanumeric': 0.01808785529715762, 'fraction_numerical': 0.0, 'mean_word_length': 5.64, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
The Need for a Unifying Traceability Scheme

The benefits of traceability are widely accepted nowadays, however, several issues still make it difficult a wide-scale adoption of traceability in the software engineering practice. There is a lack of a commonly accepted traceability definition further than the term definition, a standard way of specifying traceability among items, and a traceability type classification; besides, conflicts among a number of approaches exist. As a result traceability-schemes implementation in tools lacks of generality and exchangeability. Round trip engineering therefore cannot be well enough supported. The motivation behind is aligned with that of PIM within the MDA initiative. This paper analyzes several current traceability schemes, in order to obtain relevant features and identify overlaps and inconsistencies among the approaches. Then, and based on the analysis, it provides an initial approach for a Traceability Specification Scheme. This scheme is expected to facilitate traceability specification for a given project, to improve the traceability management, and help to automate some traces management processes.