{'fraction_non_alphanumeric': 0.015842839036755388, 'fraction_numerical': 0.0, 'mean_word_length': 5.986725663716814, '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}}
Protecting Intellectual Property by Certified Component Quality Descriptions

A major part of Component-Based Software Engineering (CBSE) focuses on composing systems of independent components and the re-use of components. Descriptions of the quality of components allow assuring the quality of the composed system. Certification addresses trust issues regarding the trustworthiness of the descriptions, e.g. in components of the shelf (COTS) scenarios. Selecting components based on quality descriptions allows protecting intellectual property (IP) of the component supplier during selection but the development process must support certification and compositional evaluations. Different certification levels are available which affect the distribution of certification effort across participating roles depending on the need for IP protection and described quality characteristic. Existing CBSE approaches neglect a clear integration of description-based selection in the development process and provide no guidelines on selecting the appropriate certification level for a component. In this paper, we show how certification of quality descriptions can be integrated into a CBSE development process. Additionally, we provide a guideline supporting the selection of a certification level and point out the implications on the effort distribution on the different participating roles. The application of the guideline is demonstrated in three different scenarios and the most suitable certification level is identified, which allows tailoring a CBSE-aware certification process.