{'fraction_non_alphanumeric': 0.04353932584269663, 'fraction_numerical': 0.0, 'mean_word_length': 5.0423728813559325, '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}}
Essential properties of IPSEs

The phrase 'Integrated Project (or Programming) Support Environment' and its acronym IPSE are being increasingly used to describe a class of systems consisting of a collection of tools to be used in program development or evolution (maintenance). If the terms 'Integrated', 'Environment' and 'IPSE' are to be meaningful, their use should be restricted to systems that satisfy appropriate criteria. In particular, a clear distinction must be made between IPSE and, to coin a term, ICSE, where 'C' stands for 'coding'. The latter term is seen as applying to, for example, a collection consisting of an appropriate editor, a compiler, a linkage editor, a loader and a run time system.