{'fraction_non_alphanumeric': 0.013539651837524178, 'fraction_numerical': 0.0, 'mean_word_length': 5.959641255605381, '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}}
Modelling and Analysing Provenance Awareness Infrastructure for SOC systems

Provenance awareness adds a new dimension to SOC systems' design allowing them to answer different kinds of questions about the system's history processing by recording information during system execution. Incorporating provenance in SOC systems requires to carefully model and analyse provenance infrastructure requirements at system's design time in order to cope with the inherent complexity encapsulated into the SOC systems' execution cycle, considering the aspects of service discovery, selection and dynamic composition. Formally specifying provenance-infrastructure behavior assists in the design/analysis of the system's accountability by introducing provenance mechanisms to collect the respective provenance where the latter can be verified and revised beforehand the system's actual implementation. We have previously presented a data model to express the graph-based structure of the provenance data collected for composite services. In this paper we focus on a template provenance-infrastructure model specifying the behavior required in order to issue the respective provenance recording calls through the SOC execution cycle. We then bind the infrastructure design to specific SOC models in order to analyze whether this leads to actual recording of the provenance required for answering provenance queries. We accomplish this by proposing a generic algorithm that simulates the provenance-infrastructure behavior and generates sample provenance-data graphs.