{'fraction_non_alphanumeric': 0.012569832402234637, 'fraction_numerical': 0.0, 'mean_word_length': 5.894230769230769, '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}}
Documenting Requirements Traceability Information for Small Projects

Software engineering literature lists many benefits of requirements traceability (RT) and strongly suggests that it should be practiced for software projects. However, available literature concentrates on the development of complex and large systems that have thousands of requirements. Companies that develop small software systems, with only approximately a hundred requirements, have limited budgets and they face the challenge to define what traceability information to document and how. Goals of this paper are to find problems of RT faced in small projects and to offer guidelines for documenting traceability information for such projects.