{'fraction_non_alphanumeric': 0.014767932489451477, 'fraction_numerical': 0.0, 'mean_word_length': 5.5, '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}}
Measuring code inspections and feeding information back to project members

Kemppainen Harri: Measuring code inspections and feeding information back to project members. _ Software inspections have several commonly agreed measures like the number of defects, duration, effort, preparation time etc. These measures are commonly collected and used to analyse the inspection process. These measures are rarely related to individuals who work in the project. To bridge this cap we define five roles and an information need for each role. All roles and information needs are related to code inspection. From an information need we derive measures and indicators to feed some of the collected information back to project members. We use a measurement information model to describe the path from information need to measures and indicators. We use measures, which are commonly collected from code inspections.