{'fraction_non_alphanumeric': 0.016170212765957447, 'fraction_numerical': 0.0, 'mean_word_length': 5.91764705882353, '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}}
Design Knowledge: a Framework for Requirement Traceability

Requirement traceability provides a knowledge base that is yet to be captured systematically in its entirety. Most available tools or frameworks do not define what or how much information should be captured; therefore, these tools are used incorrectly or not at all. It is essential to have documentation of various aspects of tracing such as what changes have been made, the reasoning behind the change and the contributions that have been made. To provide a solution, we have assembled a requirement tracing framework that takes requirement changes, contribution structures, requirement adaptability, design rationale and incremental formalization into account. Our strategy focused on investigating existing framework features to determine which key features should be incorporated. We identified some key features of our framework and these include: requirement traceability, design rationale, contribution structure, incremental formalization and requirement adaptability. With these components we offer a simpler and comprehensive approach for requirement traceability that builds a contextual knowledge base.