{'fraction_non_alphanumeric': 0.01924500370096225, 'fraction_numerical': 0.0022205773501110288, 'mean_word_length': 5.035714285714286, '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}}
From Composition to Connectors

Composition is central to Component Based Software Engineering [1]. On one hand, we can express the composition of Whole Part Relationship (WPR) with the help of some properties [2], recognized as WPR properties based on which a UML profile is being devised called WPCP (Whole Part Composition Profile). On the other hand, software composition can be achieved with the help of a connector acting as glue between the communicating components [3]. However, these two approaches consider composition at different levels as WPR properties deal with it as a vertical one with the Whole and the Part components at different granularity levels while Software connector considers it as a horizontal one with the connector in the middle and the communicating components on both sides. In WPR, a precise description of the properties is given which is being undermined by the lack of implementation support. The software connector approach is a promising approach for the implementation of the connectors but it lacks the description of connectors. This paper is a contribution towards bridging the gap between the two approaches. In order for the two approaches to work together, and taking the benefits of the WPCP in code generation of software connectors, as a first step, we match the WPR properties with software connector.