{'fraction_non_alphanumeric': 0.018234165067178502, 'fraction_numerical': 0.0, 'mean_word_length': 5.8618421052631575, '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': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Entity-Relationship Software Development Environment

We designed and implemented a prototype software development environment based on software component composition. Our software development environment, the Entity-Relationship Software Development Environment (ERSDE), uses extended entity-relationship diagrams (EERDs) as templates of executable programs. An EERD represents the component types and the relationship types among them within an application domain. The graphical editor of the ERSDE uses an EERD as a menu in constructing application software. An EERD used as a menu can enforce legitimate patterns of relationships among software components, in addition to providing an intuitive view of available components and possible relationships among them. Furthermore, as the ERSDE uses structural active objects as the components of a program, we can obtain an executable program if those components are instantiated and interconnected as dictated by an EERD. Two experiments conducted confirmed the effectiveness of our approach.